You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the code a specific joystick is hard-coded to map (for instance) yaw to the 3rd axis and POV to Gaz. I think this should be done for any joystick that supports POV or 3rd axis (wich is testable using the DirectInput class) and not only for the T.Flight Stick X.
I don't know if the following is a problem only for my two joysticks, but the center (zero) point should be 32511 (maybe I need to calibrate them?), not (short.MaxValue - short.MinValue)/2.
The text was updated successfully, but these errors were encountered:
I tried with two different joysticks - a sidewinder and a Predator. Both have a center value of 32511 for the roll and pitch axis. However, the predator does have a slightly different value for the yaw axis (the sidewinder doesn't have a yaw axis). Possibly this is just poor calibration on my side...
If you need some kind of test with joysticks feel free to tell me.
The JoystickInput.cs file is the place where axis values are determined ... if you want to do a test, just connect the joystick and debug the method GetAxisValues(). For my Flight Stick, all the values are equal as long as I don't move the axes.
In the code a specific joystick is hard-coded to map (for instance) yaw to the 3rd axis and POV to Gaz. I think this should be done for any joystick that supports POV or 3rd axis (wich is testable using the DirectInput class) and not only for the T.Flight Stick X.
I don't know if the following is a problem only for my two joysticks, but the center (zero) point should be 32511 (maybe I need to calibrate them?), not (short.MaxValue - short.MinValue)/2.
The text was updated successfully, but these errors were encountered: