-
Notifications
You must be signed in to change notification settings - Fork 13
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
Cage/Uncage not working in-game #11
Comments
JoyPro does only change at the current point things for joystick, it is not touching anything keyboard (unless its a modifier) and also just the stuff that is in Saved games. Also im not touching the default luas itself, im reading them, but im not altering them. I mean i don't know exactly how DCS works under the hood, but the creation of joystick keybinds should not interfere with keyboard keybinds. Do you have red exclamanation marks in DCS in the F18? |
Interesting, no. I have no red exclamations. Yeah I am not sure, but seems to be very strange behavior that a simple, default keyboard keybind would not work anymore. It would seem very strange if it was in fact your program that caused this, but it is the only variable I isolated when troubleshooting this problem. |
If so go into you saved games\DCS\Config\Input\FA-18C_hornet\joystick and delete everything in there, does the C button start to work again? |
Yes actually, okay, interesting. I then re-setup controls with JoyPro and everything seems to be working. |
Interesting first time i hear about this, but certainly not the first weird issue im facing :D |
Haha the nature of the beast. I am also a software engineer, so I understand your pain! |
This may not have anything to do with JoyPro.
However, I used JoyPro to setup all my controls. I did not set a bind for CAGE/UNCAGE, since I like it to stay the default "C" keyboard key. I finished by selecting "Clean Existing Binds and Export" with "Keep Defaults" checked.
I then hopped into the F/A-18C to do some maverick practice and realized that CAGE/UNCAGE default Key was not working. It would not actually perform the action. I looked at my controls in-game and the "C" was in-fact still set as the bind.
Is it possible that JoyPro is somehow causing default controls to have issues after setting things up?
The text was updated successfully, but these errors were encountered: