FlyAnyTime Posted March 15, 2019 Posted March 15, 2019 (edited) Just installed F-14 and current open beta in Steam and have lost all ability to setup controls - controls are shown but not recognized when trying to bind axis. I have Saitek X-36 HOSTAS, MFD Cougar V1 panels and CH pedals. I used the Steam File verification and renamed the DCS folder under saved games. While the startup of the application was changed and did go faster however the useability of the F-14 did not change. When trying to configure my controls the application would not recognize the controllers axis while I was trying to bind. For example I was able to bind my Saitek X-56 left throttle lever on the first attempt to the left engine thrust. However when I attempt to bind the right throttle lever to the right engine thrust it fails to recognize the controller. If I go back to the left throttle to confirm the setting it now fails to see it as well. I then attempt to force the binding by manually setting the preferred axis using the dropdown option. When I go to try and fly the F-14 the game again hangs on the startup screen (see attached). I have tried waiting as long as 30 min without any change and ultimately just kill it. I have attached a jpg of the hung screen and latest log file and DiagDX results. Does anyone have a solution for this set of problems? Edited April 1, 2019 by IronMike
sze5003 Posted March 15, 2019 Posted March 15, 2019 This is a common issue for all modules since the previous update. You can only set one axis at a time. Also select axis from the drop down menu when assigning axis rather than clicking the axis button on bottom of the control inputs section. Once you set an axis, hit ok and exit DCS then come back in, set the next one, hit ok, exit DCS, etc. Asus ROG Strix Z790-E | Core i9 13900K-NZXT Kraken X73 AIO | 32GB DDR5 G Skill Neo 6600mhz | 2TB Sk Hynix P41 Platinum nvme |1TB Evo 970 Plus nvme | OCZ Trion 150 960GB | 256GB Samsung 830 | 1TB Samsung 850 EVO | Gigabyte OC 4090 | Phanteks P600S | 1000W MSI MPG A1000G | LG C2 42 Evo 3840x2160 @ 120hz
McNinja Posted March 16, 2019 Posted March 16, 2019 Thanks man, I was trying to wrap my head around this problem for the longest time. Kind of annoying and I hope it gets fixed sometime soon. I was able to repro this issue consistently since the F-14 launch.
Recommended Posts