Jump to content

Recommended Posts

Posted

How about an option whereby the in-game controls do not start moving until the player's controls cross/match their settings? If you've used MIDI controllers you're probably familiar with this idea....it's to prevent sudden, potentially catastrophic, jumps in value (e.g. volume) when using shared knobs, faders etc.

 

Currently in DCS if you spawn in the air at, say, 500kph the in-game controls will be set for 500kph....but the moment you move your physical ones the in-game counterparts 'jump' to match yours. This causes dramatic unwanted effects, particularly with WW2 aircraft.

 

Here's a typical P-51 air start....

 

83sqKP2.gif

 

If the in-game throttle only started moving once the player's throttle crossed or matched its position there would be a smooth transition from AI flight to player control instead of the mad over/under-revving that we have now.

 

(in case you're wondering the 'Synchronize HOTAS at mission start' option is not the same thing)

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...