Control settings are FUBAR

[Turok144]

Greetings everyone!  I'm a DCS World newbie.  I recently returned to flight simming from my early days of Falcon 3.0, 4.0  I chose DCS World for the similarities and modernization that this sim offers over Falcon.  I love it! I'm really happy and feel "back in the saddle again" after decades of not simming.  I also scored MSFS 2020 and will purchase X-Plane 12 once it's released for early access.  I'm really stoked about the realism that the modern flight models are offering at the present time.

I'm finding myself in a unique quandary and need help as to how to fix my issue.  I connected my new Warthog Hotas system, installed all the drivers/firmware. For the most part, the default configuration was working fine.  I was in the process of throttling up my F-16 and taking off to the friendly skies.  I even managed some newbie landings.  So no issues there.  The problem began when I purchased and installed my new Thrustmaster TPR pedals yesterday.  All hell broke loose when my F16 shot out like a rocket from the taxiway and crashed into the trees.  Furthermore, my HOTAS  throttle is inverted, max power when it should be off or in the idle position.  My rudder pedals default to the throttle settings and my joystick doesn't do anything.  Even my default keyboard assignments have become unresponsive.

As a last ditch effort, I tooled around with the control settings and was overwhelmed by the extensive list of assignable parameters.

Is there a way to reassign the default settings for the keyboard, Hotas, TPR without having to configure every single parameter manually?

How do I find which version of the F-16 do I have and where do I find the aircraft updates if I need to update to the latest available version?

What totally befuddles me is that this erratic reassignment of my controls only happened after I installed the TPR pedals and is only affecting DCS World.  My HOTAS system and rudder pedals are all working fine right out the box in MSFS 2020 without any of the issues I began encountering in DCS World.

 

Anyway as it is customary to say in the military, when a new member introduces himself at a new permanent duty station, I'm damn glad to be here!

 

 

 

[Frederf]

I don't remember if DCS Viper has a specific default control set or it's the generic. First thing you should do is go to the axis section and clear category for every controller column or in your case your pedals if that's the issue.

Basically DCS assigns roll to the X axis of the controller... every single one of them. This is also true of a bunch of other axes and buttons. This is obviously dumb and causes all sorts of problems. The exception to this generic binding is if there is a specific .diff.lua file for your specific controller, then it's as set in that non-generic file. DCS Viper comes with specific controller settings for 19 devices. This includes the Throttle and Joystick Warthog controllers, but not the pedals. The fix is simply to delete the assignments from your controller that you don't want. E.g. if Pedals "X" is bound to roll, highlight the box at the intersection of the "Roll" row and "Pedals" column and use the Clear button on the bottom.

The "build number" is a unique five digit number on the splash logo, lower left corner or main menu, lower right corner after the version number. Updates are checked for automatically, but there is a way to manually prompt a check although I've rarely seen it needed. You'll know if an update is available. There are two branches, Release (normal install) and Open Beta. The OB branch is updated more frequently and then when the programmers are satisfied that it's good enough the stable branch. You can convert between the branches with a special command line which is a lot better than uninstalling/reinstalling everything. Currently my Open Beta branch is on 2.7.15.26783.

Of course you can assign and adjust one or two things without having to reassign everything. Out of the hundreds of commands I probably only use 20-30. Make good use of the category filters, folded view and the list won't be so scary.

Good luck, have fun, ask questions.

Edited July 15, 2022 by Frederf

[tweet]

Hi Turok. The issue with new controls is almost always the default settings. Often there is at least one axis double mapped or a button that is mapped to the same function mapped on another controller. Rudder pedals are a common one. (Edit: As just remembered after seeing  Frederf's post, an axis in the defaults will be mapped for almost every controller.)  I'm not familiar with the TPR but I'm willing to bet that more than the rudder axis and two wheel brake axes is mapped on another controller. Your other controls also probably have an axis mapped to either the rudder or brakes. In any event unusual behavior is almost always the result of double (or more) mapping. The only solution is to go through all of your controls and deleting any mapping of the other controls to a function you want on your pedals. I always delete a mapping on a controller I don't want on that controller or for a function I don't want a controller mapping on. For instance, I only fly in VR so I delete all mappings to controllers for the "VIEW" or "VIEW xxxxxx" categories.

I recently converted to Winwing controls from my very old and trusty Warthog. Yeah, it's a PITA to setup and relearn 5-10 airplanes but it was an opportunity to improve my HOTAS workflow and greatly improve control function in general. I had double mappings and axis issues but slowly and methodically going through the process sorted everything out. It isn't a fast process to set up controls but once you do a few and learn some of the handy features you'll come to appreciate the control mapping section. It's quite powerful and flexible which introduces some complexity to get our heads around. The frustration will subside with use.

One feature to get familiar with is "Axis Tuning". That's where reversed controls are fixed. There's a check box to reverse an axis. It also has powerful features to tame overly- or under- sensitive controls. I always map while sitting in an aircraft in a training or self generated mission on active pause. This way I can test as I go along and find problems quicker instead of finding something after spending time doing a cold start and getting half way across the map and having an unrecoverable issue. The other thing I learned the hard way is to ALWAYS remember to hit "Save and Apply" before leaving the control app or even selecting something different like AH-64Pilot" to AH-64CPG". If you don't, you lose all of your work but do get an opportunity to become more familiar with mapping when you redo the work you lost. Isn't pain a great teacher? Just try to temper the frustration by realizing this is essential work and will greatly improve your experience once you find something that works. You'll figure it out with patience. Good luck.

Edited July 15, 2022 by tweet

[Turok144]

On 7/15/2022 at 1:08 PM, Frederf said:

I don't remember if DCS Viper has a specific default control set or it's the generic. First thing you should do is go to the axis section and clear category for every controller column or in your case your pedals if that's the issue.

Basically DCS assigns roll to the X axis of the controller... every single one of them. This is also true of a bunch of other axes and buttons. This is obviously dumb and causes all sorts of problems. The exception to this generic binding is if there is a specific .diff.lua file for your specific controller, then it's as set in that non-generic file. DCS Viper comes with specific controller settings for 19 devices. This includes the Throttle and Joystick Warthog controllers, but not the pedals. The fix is simply to delete the assignments from your controller that you don't want. E.g. if Pedals "X" is bound to roll, highlight the box at the intersection of the "Roll" row and "Pedals" column and use the Clear button on the bottom.

The "build number" is a unique five digit number on the splash logo, lower left corner or main menu, lower right corner after the version number. Updates are checked for automatically, but there is a way to manually prompt a check although I've rarely seen it needed. You'll know if an update is available. There are two branches, Release (normal install) and Open Beta. The OB branch is updated more frequently and then when the programmers are satisfied that it's good enough the stable branch. You can convert between the branches with a special command line which is a lot better than uninstalling/reinstalling everything. Currently my Open Beta branch is on 2.7.15.26783.

Of course you can assign and adjust one or two things without having to reassign everything. Out of the hundreds of commands I probably only use 20-30. Make good use of the category filters, folded view and the list won't be so scary.

Good luck, have fun, ask questions.

 

Thank you.  Good to know about the auto updates.

[Turok144]

On 7/15/2022 at 1:22 PM, tweet said:

Hi Turok. The issue with new controls is almost always the default settings. Often there is at least one axis double mapped or a button that is mapped to the same function mapped on another controller. Rudder pedals are a common one. (Edit: As just remembered after seeing  Frederf's post, an axis in the defaults will be mapped for almost every controller.)  I'm not familiar with the TPR but I'm willing to bet that more than the rudder axis and two wheel brake axes is mapped on another controller. Your other controls also probably have an axis mapped to either the rudder or brakes. In any event unusual behavior is almost always the result of double (or more) mapping. The only solution is to go through all of your controls and deleting any mapping of the other controls to a function you want on your pedals. I always delete a mapping on a controller I don't want on that controller or for a function I don't want a controller mapping on. For instance, I only fly in VR so I delete all mappings to controllers for the "VIEW" or "VIEW xxxxxx" categories.

I recently converted to Winwing controls from my very old and trusty Warthog. Yeah, it's a PITA to setup and relearn 5-10 airplanes but it was an opportunity to improve my HOTAS workflow and greatly improve control function in general. I had double mappings and axis issues but slowly and methodically going through the process sorted everything out. It isn't a fast process to set up controls but once you do a few and learn some of the handy features you'll come to appreciate the control mapping section. It's quite powerful and flexible which introduces some complexity to get our heads around. The frustration will subside with use.

One feature to get familiar with is "Axis Tuning". That's where reversed controls are fixed. There's a check box to reverse an axis. It also has powerful features to tame overly- or under- sensitive controls. I always map while sitting in an aircraft in a training or self generated mission on active pause. This way I can test as I go along and find problems quicker instead of finding something after spending time doing a cold start and getting half way across the map and having an unrecoverable issue. The other thing I learned the hard way is to ALWAYS remember to hit "Save and Apply" before leaving the control app or even selecting something different like AH-64Pilot" to AH-64CPG". If you don't, you lose all of your work but do get an opportunity to become more familiar with mapping when you redo the work you lost. Isn't pain a great teacher? Just try to temper the frustration by realizing this is essential work and will greatly improve your experience once you find something that works. You'll figure it out with patience. Good luck.

 

Much appreciated.  I got it sorted out thanks to your and Frederf's suggestions.  Some axis commands were definitely double mapped while others were incorrect.  It's gonna be painful like you say to map each parameter manually, but in the end it's probably the best thing.  At least this drill will broaden my knowledge of the commands.  I'll make sure that I save often as well.

Cheers!

[arb65912]

5 minutes ago, Turok144 said:

Much appreciated.  I got it sorted out thanks to your and Frederf's suggestions.  Some axis commands were definitely double mapped while others were incorrect.  It's gonna be painful like you say to map each parameter manually, but in the end it's probably the best thing.  At least this drill will broaden my knowledge of the commands.  I'll make sure that I save often as well.

Cheers!

Hi Turok, I am totally new here and I did have to go through setup, but it is not so bad.

Just start with axes and then whatever you think it is the most needed. It is going to be saved automatically but if you want you can save as some profile.

I also had double assignments and it was driving me nuts, I advanced throttle and some other parameter was changing.

Take it easy and enjoy!!!

[Turok144]

21 hours ago, arb65912 said:

Hi Turok, I am totally new here and I did have to go through setup, but it is not so bad.

Just start with axes and then whatever you think it is the most needed. It is going to be saved automatically but if you want you can save as some profile.

I also had double assignments and it was driving me nuts, I advanced throttle and some other parameter was changing.

Take it easy and enjoy!!!

Thanks arb65912.  I'm slowly making progress through trial and error but it's been really rewarding figuring it out.  I wrongly assumed that everything would already be mapped to the joystick etc. Yesterday, I figured out how to map the brakes to the rudder pedals.  Everything when it comes to flight simming is all about the realization that one cannot rush and expect instant results.  It's all about patience, the desire to learn, and apply your knowledge layer by layer.

 

Cheers! 

[arb65912]

52 minutes ago, Turok144 said:

Thanks arb65912.  I'm slowly making progress through trial and error but it's been really rewarding figuring it out.  I wrongly assumed that everything would already be mapped to the joystick etc. Yesterday, I figured out how to map the brakes to the rudder pedals.  Everything when it comes to flight simming is all about the realization that one cannot rush and expect instant results.  It's all about patience, the desire to learn, and apply your knowledge layer by layer.

 

Cheers! 

Yes, could not agree more. I had a rough time with setup until I found out the way around it and so far, so good. 

Enjoy everything!!!!

[Turok144]

50 minutes ago, arb65912 said:

Yes, could not agree more. I had a rough time with setup until I found out the way around it and so far, so good. 

Enjoy everything!!!!

Thanks mate. To you as well.