Flight controls at mission start

[II.JG1_Vonrd]

Whenever I start a mission (no matter what type... from ME, Quick, single, campaign) with engine running or in flight, when I press fly and spawn in the controls are hard over to the left. Not so big a deal when airspawn but very problematic when starting on ground in a helicopter. I have to be really quick on collective and cyclic to prevent a rotor strike. How can I fix?

[draconus]

Check bindings for axis assignment. Make sure only one device controls one command.

Can be desynch of your HOTAS with game HOTAS - make a controls wipeout before hitting Fly.

[Lange_666]

Do you have under settings/misc this setting activated?

 

 

If yes, try with it turned off.

If i set this to on, i have the same problem as you when i re-enter a mission when the controls where not in there default position when i left a previous mission, like crashing with throttle set to anything then minimum. It seems like DCS keeps the latest used control setting in memory instead of looking at the exact controller setting at mission start.

With this setting turned "off", i don't have that problem.

[II.JG1_Vonrd]

19 hours ago, Lange_666 said:

Do you have under settings/misc this setting activated?

 

 

Yep, that was it... Thanks! 

[Noluck]

On 5/25/2021 at 5:37 AM, Lange_666 said:

Do you have under settings/misc this setting activated?

 

 

If yes, try with it turned off.

If i set this to on, i have the same problem as you when i re-enter a mission when the controls where not in there default position when i left a previous mission, like crashing with throttle set to anything then minimum. It seems like DCS keeps the latest used control setting in memory instead of looking at the exact controller setting at mission start.

With this setting turned "off", i don't have that problem.

 

Same here. I just installed a newer TM driver for adding the Cougar MFD's, I thought that was it. Tore my hair out. Yep, finally disabled the above in settings and all is good. It's definitely a BUG from  the 2.7.x update. I had it turned on in 2.6.x and no issues.

 

---

Edited May 26, 2021 by Noluck
typo

[Lange_666]

No, it's not a bug from 2.7. The same behavior exist already quite a while, even from 1.x.x 

[Munkwolf]

3 minutes ago, Lange_666 said:

No, it's not a bug from 2.7. The same behavior exist already quite a while, even from 1.x.x 

 

Hmm, interesting. I had that option checked for a while, and then the issue started happening after 2.7.

[MAXsenna]

I have this checked and some modules behaves differently in 2.7 for me. I usually do cold starts, so not really a problem.
In the Mirage and C-101 the throttle will be fully forward.
In the C-101 thread Aviodev say they have fixed for the next update.
Cheers!

Sent from my MAR-LX1A using Tapatalk

[-0303-]

15 hours ago, Lange_666 said:

No, it's not a bug from 2.7. The same behavior exist already quite a while, even from 1.x.x 

The "Synchronize HOTAS ..." problem definitely started after 2.7. Had it checked for 2 years before 2.7.

Edited May 27, 2021 by -0303-

[Lange_666]

For you then it is but it's been around longer then 2.7, that's a fact!

There are various post on the topic pre 2.7. One of them is at least one of mine.

Edited May 27, 2021 by Lange_666