csthopper Posted February 25, 2016 Posted February 25, 2016 (edited) I use a Saitek Aviator as my primary joystick, and a Xbox 360 Gamepad to control my camera skewing. This setup is working well in DCS World 1.2, but in 1.5, the gamepad axis are not responsive. The controller config screen sees the gamepad axis, and let me assign them, but if I go to Axis Tune, I can't get any movement out of the gamepad sticks. The Saitek responds fine in Axis Tune. Confirmed the gamepad is working in Windows settings, and also as mentioned, still works fine in DCS World 1.2. Thanks for the help Edited February 26, 2016 by csthopper
QuiGon Posted February 25, 2016 Posted February 25, 2016 I can't help you with your problem, but I can say the following: I used the Xbox360 pad untill 2 years ago when I switched to the Warthog HOTAS but back then the gamepad and it's axis worked just fine. But just a couple of days ago someone with the same problem as yours came up in the german section of this forum and after two pages of good advices the problem is still there (http://forums.eagle.ru/showthread.php?t=141262&page=6 starting with comment #55). So it seems there is indeed something broken with the xbox360 axis in the current DCS version. Intel i7-12700K @ 8x5GHz+4x3.8GHz + 32 GB DDR5 RAM + Nvidia Geforce RTX 2080 (8 GB VRAM) + M.2 SSD + Windows 10 64Bit DCS Panavia Tornado (IDS) really needs to be a thing!
csthopper Posted February 25, 2016 Author Posted February 25, 2016 (edited) Thanks, and I see that you cross posted on that thread. Looks like this has enough visibility, and should hopefully be fixed. Maybe one day someone will gift me the Warthog HOTAS that I have had on my Amazon wishlist for years :P Edited February 25, 2016 by csthopper
LimpetDrone Posted May 9, 2016 Posted May 9, 2016 (edited) Hi, Any update about this issue? I've just updated DCS to 1.5.3 and Xbox 360 axis control just broke. It worked fine with the previous DCS version (half an hour ago when I tried it). How the hell they still don't fix this issue after 2 month. Edited May 9, 2016 by LimpetDrone
zacklaws Posted May 9, 2016 Posted May 9, 2016 I have just had this problem yesterday with my Logitech Extreme 3D Pro which I use for quick games instead of setting up my Thrustmaster Warthog, HOTAS and pedals. I updated to the latest version of 1.5.3, checked the settings that nothing had changed for the joystick and nothing had, but soon as I went to play a mission with the F-86F, I went into an inverted loop and had no control at all with the stick to pull out of it and eventually crashed. After the first time, I disconnected the stick from the PC and reconnected it, opened up DCS world again, the same happened again. In total it happened three times. After the third time I opened up control panel in Windows and checked to see if my stick was working and it was working perfectly, opened up DCS world again and the problem was solved.
LimpetDrone Posted May 9, 2016 Posted May 9, 2016 Interesting. No luck for me with these steps. It's working in windows control panel but not in the game.
knix15 Posted May 10, 2016 Posted May 10, 2016 Please fix the x360 axis issue ASAP. Win10 + wireless controller.
El Hadji Posted May 11, 2016 Posted May 11, 2016 This seems to be an issue specifically linked to the 360 wireless controller together with Win 10. The wired controller works as intended. It has also been brought up in the Steam DCS forum: http://steamcommunity.com/app/223750/discussions/0/412448792350373660/ [sIGPIC][/sIGPIC] My computer specs below: CPU: Intel Core i5 3570K@4.2GHz | CPU Cooler: Corsair Hydro H100 | GPU: MSI Nvidia GTX 680 2GB Lightning 2GB VRAM @1.3GHz | RAM: 16GB Corsair Vengeance LP DDR3 1600 | SSD 1: Corsair Force 3 120GB (SATA 6) | SSD 2: Samsung 850 EVO 500GB (SATA 6) | Hybrid disc: Seagate Momentus Hybrid 500/4GB (SATA 3) | Keyboard: QPAD MK-85 | Mouse: QPAD 5K LE | TrackIR 5 + Track Clip Pro | Thrustmaster HOTAS Warthog | MFG Crosswind | OS: Win7/64
Snaut Posted June 7, 2016 Posted June 7, 2016 Latest beta reverted to old behavior - gamepad sticks work again but triggers are not properly separated. MSI GTX 770 2GB -> 1920x1200, MSI H97M, Xeon 1231v3, 16GB
swat007 Posted June 30, 2016 Posted June 30, 2016 XBOX360 wireless triggers not work too, hope it will be fix soon. Let the JOY_Z axis working again plz~~~~~~~~~~
Awe Posted November 29, 2016 Posted November 29, 2016 I'm using a PS3-Controller on Win10 with the MotioninJoy Driver. DCS recognizes the trigger-axis correctly when selecting "DX-Default" mode in the Driver Tool. For other games it has to be "Xinput-Default" though... Don't know what it means but it did the trick for me.
Recommended Posts