UN9249 Posted May 28, 2022 Posted May 28, 2022 (edited) Hello, friends everytime i restart DCS happens this. pretty annoyng. Edited May 28, 2022 by UN9249 [sIGPIC][/sIGPIC]
draconus Posted May 29, 2022 Posted May 29, 2022 Hover the mouse over the exclamation mark and read what is causing the controls conflict. Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
UN9249 Posted May 29, 2022 Author Posted May 29, 2022 (edited) hi, it says "no awailable comands for your device". but its my hotas warthog pitch channel. so i have everytime i start dcs to put it to default, and than it works. Edited May 29, 2022 by UN9249 [sIGPIC][/sIGPIC]
draconus Posted May 29, 2022 Posted May 29, 2022 Yeah, there's some bug in the Warthog F-14 default profile people already reported. What I suggest to try is to backup and then remove that profile from main DCS folder /mods/f-14/config/input/joystick (did not check exactly, real folder may differ). 1 Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
UN9249 Posted June 1, 2022 Author Posted June 1, 2022 (edited) On 5/29/2022 at 6:02 PM, draconus said: Yeah, there's some bug in the Warthog F-14 default profile people already reported. What I suggest to try is to backup and then remove that profile from main DCS folder /mods/f-14/config/input/joystick (did not check exactly, real folder may differ). that helped, thank you! i had to reassign all controlls again, but nothing jams my controll now. thank you!! Edited June 1, 2022 by UN9249 1 [sIGPIC][/sIGPIC]
draconus Posted June 1, 2022 Posted June 1, 2022 (edited) 5 hours ago, UN9249 said: that helped, thank you! i had to reassign all controlls again, but nothing jams my controll now. thank you!! Cool, now backup your controls from \saved games\dcs\config\input\ and remember the problem (bad file) can come back after the update or DCS repair, until it's fixed. Edited June 1, 2022 by draconus 1 Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
IronMike Posted June 1, 2022 Posted June 1, 2022 Thank you for the reports, we'll investigate further what we can do to squash this bug, we're currently not sure what is causing it. 1 Heatblur Simulations Please feel free to contact me anytime, either via PM here, on the forums, or via email through the contact form on our homepage. http://www.heatblur.com/ https://www.facebook.com/heatblur/
Heizer-41- Posted July 9, 2022 Posted July 9, 2022 Got the same problem with F-14 Throttle-Axis: red dot marked and not applicable if rudder-pedals pluged in.
Devil 505 Posted August 24, 2023 Posted August 24, 2023 On 6/1/2022 at 7:33 AM, IronMike said: Thank you for the reports, we'll investigate further what we can do to squash this bug, we're currently not sure what is causing it. Was there any progress made on this? Been flying the F-14 since release with my Thrustmaster rudder pedals and HOTAS Warthog. Got a new computer recently and loaded the Tomcat back up along with every single module in DCS. I have had no issues binding axis or using my rudder pedals or throttle with any other aircraft. For some reason the F-14 allows me to bind the Stick and left/right toe brakes, but not the rudder pedals itself or the throttle. There is a red exclamation mark next to both rudder pedals and throttle before I even try binding them. Then when I bind them, there is a red exclamation mark next to the assigned axis for both. I hover the cursor over the red marks and all it does is tell me the axis I just bound; it does not provide the error/conflict. I have gone into the UI layer options and General options and have nothing bound to the axis. I have gone inside the RIO axis and have nothing bound there. I cannot figure out where the problem lies and I know it is not with my equipment. Any help would be greatly appreciated. The F-14 is the only module giving me this problem and I want to get back to flying her with my new PC.
draconus Posted August 24, 2023 Posted August 24, 2023 @Devil 505 Let's diagnose the problem: 1. Have you tried earlier solution from this thread? Backup and remove TM rudder's default profile file from the game files /mods/aircraft/f-14/config/input/joystick - the exact folder may be different - I'm pulling it out of my head. 2. Remove DCS mods. 3. Disable any external software or additional drivers for control devices. 4. Try clean profile - rename temporarily /saved games/dcs world folder. Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Willie Nelson Posted November 7, 2023 Posted November 7, 2023 On 8/24/2023 at 5:06 PM, draconus said: @Devil 505 Let's diagnose the problem: 1. Have you tried earlier solution from this thread? Backup and remove TM rudder's default profile file from the game files /mods/aircraft/f-14/config/input/joystick - the exact folder may be different - I'm pulling it out of my head. 2. Remove DCS mods. 3. Disable any external software or additional drivers for control devices. 4. Try clean profile - rename temporarily /saved games/dcs world folder. Just had this problem too, I cheated on the steps though, not sure if I really want to uninstall all mods, I simply deleted the in game default warthog thrust lever profiles on the Hornet (my problem was on the speed brake extension) and then repaired DCS. So far so good. i7700k OC to 4.8GHz with Noctua NH-U14S (fan) with AORUS RTX2080ti 11GB Waterforce. 32GDDR, Warthog HOTAS and Saitek rudders. HP Reverb.
Recommended Posts