ZXMaster Posted May 24, 2023 Posted May 24, 2023 (edited) Loaded into DCS today to fly the F1EE for the first time post-update, and none of my axis commands are working in the jet on my T16000 joystick or throttle. DCS is seeing the controllers correctly, and if I load into the AV-8B both work as normal. Have tried deleting bindings, resetting bindings, clean and repair of the game, and re-install the module, to no avail. Any assistance would be appreciated. Edited May 24, 2023 by ZXMaster
Sheepy Posted May 24, 2023 Posted May 24, 2023 I have been assisting ZXMaster. The buttons do however work but not the Axis, you can actually see the animations on the stick if you press weapon release for example. We have also cleared the category of the axis commands well as re-installing the module itself. i7-9700K || GTX 1080 Ti || 32Gig 3200 RAM || 1TB NVME & 1TB SSD || X56, Track IR, CH Pro Rudder Pedals
ZXMaster Posted May 24, 2023 Author Posted May 24, 2023 dcs.log Attached my latest log file in case it will be of use.
fausete Posted May 25, 2023 Posted May 25, 2023 Hello, we can't see anything out of the ordinary in the log but we are investigating. I imagine you have already done it, but please, make sure no other device that might be interfering is connected. I don't think this is the source of the problem, but just to try, please in the Miscellaneous options menu, try unchecking the FFB option. Finally, if you attach a track, we can take a better look to see if the issue is in our code. 1
Solution Sheepy Posted May 25, 2023 Solution Posted May 25, 2023 9 hours ago, fausete said: Hello, we can't see anything out of the ordinary in the log but we are investigating. I imagine you have already done it, but please, make sure no other device that might be interfering is connected. I don't think this is the source of the problem, but just to try, please in the Miscellaneous options menu, try unchecking the FFB option. Finally, if you attach a track, we can take a better look to see if the issue is in our code. So we found the problem... it's us xD. We Didn't realise the plane needed to be started to move the stick, so all is good. It's something I never bother checking before starting up. I start and afterward check controls. Apologies about that. Thanks for the help and interest. 1 i7-9700K || GTX 1080 Ti || 32Gig 3200 RAM || 1TB NVME & 1TB SSD || X56, Track IR, CH Pro Rudder Pedals
ZXMaster Posted May 25, 2023 Author Posted May 25, 2023 9 hours ago, fausete said: Hello, we can't see anything out of the ordinary in the log but we are investigating. I imagine you have already done it, but please, make sure no other device that might be interfering is connected. I don't think this is the source of the problem, but just to try, please in the Miscellaneous options menu, try unchecking the FFB option. Finally, if you attach a track, we can take a better look to see if the issue is in our code. As Sheepy has mentioned, once the motor was started, all was well. Something that never crossed my mind last night (been a good 9 months since I last flew the F1). Thank you for taking the time to assist. 1
fausete Posted May 25, 2023 Posted May 25, 2023 (edited) No problem. I didn't even think that might be why you were seeing what you were seeing. Glad you found out! Edited May 25, 2023 by fausete 2
Recommended Posts