cannot reproduce Hot start mission issue

[Caldera]

Hey all,

I just installed .49940 and jumped into a hot start mission.  The first thing I noticed was a light green tint to the IHADS, the second thing I noticed was that I became quickly airborne in a right spiraling rotation and immediately crashed.  Both were not the case before.

 

The first thing I can deal with.  The second thing I am looking for a work around.  It would probably be by editing a LUA file?

So is there a way to force the collective value to be at zero when the collective is physically at zero (full down) when the mission starts? 

This is instead of having to quickly raise then lower the collective so that it is so.

I have "Synchronize Cockpit Controls with HOTAS Controls at Mission Start" checked, as it has been since I started playing.  But I  know that doesn't always work (Exp: Throttle on the A-10C)

 

I have no idea why ED decides to change this stuff like this, but they do.  It can be frustrating.

Thanks in advance,

Caldera

Ah Oops...

The first thing, as it turns out was a switch out of position on my HOTAS.

Caldera

[Floyd1212]

I’m not seeing any new behavior with the collective not syncing on startup.

My guess is you have another axis bound to the collective and there is “competition” for what position it should start in, then nudging your physical collective sets it back to zero.

Having controllers get auto-assigned an axis is something we have seen after patching. 

[Caldera]

Floyd,

Thanks that was it.  I also added another trim control axis controller and I forgot to check.

Caldera