Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question - How go get axis change working #117

Open
Meekstaaa opened this issue Jun 4, 2018 · 4 comments
Open

Question - How go get axis change working #117

Meekstaaa opened this issue Jun 4, 2018 · 4 comments
Labels

Comments

@Meekstaaa
Copy link

Hi again,

Sorry for the bombardment of questions!

A bit of a background, not sure if you play it but in project cars 2 the lmp hybrid system is useless and activates on full throttle but at 90% it doesn't activate. Having a manual activation would be a great advantage to have so you can deploy it whenever you want.

I was thinking about this and how joystick gremlin could be used to facilitate this. I set it up but it didn't seem to work, I'm not sure if it's me doing something wrong or not.

Here's what I did:

  • Have my throttle set to a vjoy axis.

  • Have two profiles under my parent profile which has the throttle linked to the Vjoy axis.

  • Have game calibrated for 100% travel = 100% in game throttle.

  • Profile 1 set to 100% throttle.

  • Profile 2 have the Vjoy curve set so that only 90% of throttle is applied when at 100% pedal travel is applied.
    image

  • Have a temporary switch on wheel between profiles 1 & 2.

Am I doing it right or is there something else?

Oh I also noticed when going between scrolling through the profiles setting it up in the Vjoy device part it phantom adds other axis to the list and moves things around in the UI even though there are no other axis setup in Vjoy.

When you close and reopen the program it also can show that the curve is there next to the axis
image
But not on showing the actual curve next to it.

@WhiteMagic
Copy link
Owner

Just to make sure I understand correctly what the goal is. You want to have two modes, one that is a standard 1:1 mapping and the second one which reaches 90% virtual (as seen by the game) when the physical throttle is at 100%.

I just quickly tried doing it the way you did, with the response curve on the vJoy axis, and you seem to have found a bug. The vJoy response curve is set when entering the temporary mode but not unset when it is left. This would obviously break your setup. The other way is to simply have the response curve and remap action on the actual axis itself rather then the vJoy axis, i.e. something like this:

bandicam 2018-06-04 22-44-58-133
bandicam 2018-06-04 22-45-16-863

That should set the vJoy axis to 90% when the physical axis reaches 100%. One possible drawback of this in general (irrespective of where the response curve is applied) when you leave the temporary mode the axis value will not automatically updated, i.e. there has to be a slight motion of the axis to change the value again.

Yeah the input selection thing is a bit whacky at times depending on the action sequence and changes between tabs etc.

@Meekstaaa
Copy link
Author

Aha! I shall give that a go! Thank you.

@Meekstaaa
Copy link
Author

That works! Thanks!

Is there any way or work around to make the axis change without moving the physical axis?

@WhiteMagic
Copy link
Owner

Not at the moment but it's one of those things I'm planning for the next version. Essentially allowing arbitrary actions to be run when leaving / entering modes. In this case that could be used to set an axis value when entering a mode to trigger updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants