Is "synchronize cockpit controls with HOTAS controls at Mission start" broken? Not P-51 specific. Also Spitfire, probably all.

[-0303-]

So I noticed multiple times when spawning P-51 start on runway engine spins up. When I touch the HOTAS throttle lever (Warthog) it goes to idle. Same thing Spitfire. HOTAS throttle idle but engine roars away until lever touched on mission start.

 

Began with first 2.7 release I think.

Yes, I checked the checkmark, I've relied on it for years.

[rick66]

I'm seeing this also.

Edited April 28, 2021 by rick66

[=475FG= Dawger]

Me too. I turned it off. Got tired of going off the side of the carrier in the Hornet with a hot start. Same thing happens in every module.

 

[-0303-]

Took a turn for the worse. For some reason, maybe just me, I always had infrequent occasional, "stick disconnected" or whatever the exact message.

 

It reconnects immediately and nothing usually happens. Except now it goes full throttle and I have to "retouch" throttle.

<sad upside down Spitfire>

<and sad upside down P-51>

...

Now it happened when Alt-Tabbing away from DCS. Coincidence?

---

Happened again, immediately on Alt tabbing away.

Even an Alt+Enter shift from full screen triggers it.

Edited May 1, 2021 by -0303-

[Art-J]

Never had controls de-sync on mission spawn in 2.7 so far, in any of the planes I flew, or when Alt-Entering. The sync option seems to be working well, as always. TH Warthog hotas here, used without TARGET software.

 

It's in single player, though, I don't know how things are in multi. Haven't Alt-Tabbed either, so can't comment on this one.

 

 

[Captain Orso]

Controls with desync if you make any adjustments to any controls while in-mission. It has been this way for as long as I fly DCS.

 

EG: You are flying straight and level. <Esc> and go into control settings, change anything, even if you immediately change it back, save.

Now try to lower your gear through flipping the switch on your HOTAS configured for gear-up/gear-down to the gear-down position. Nothing happens. Flip back to the up position, and nothing happens, which is expected, because the gear are already up. Flip the switch to the gear-down position again and the gear go down. After that it works normally.

 

Works the same with every switch on the HOTAS.

[Bastlwastl]

Hello there,

 

i am experiencing this as well but only in the F-18, dann anyone confirm that he has the same problem?

 

Thanks a lot!

 

regards

Sebastian

[-0303-]

On 4/28/2021 at 11:46 PM, pmiceli said:

Me too. I turned it off.

Turning it off prevents "full throttle spawn" offline. Just now MP online I alt tabbed out of DCS and came back to find brakes-locked-idling plane upside down. Getting old.

Edited May 26, 2021 by -0303-

[LeCuvier]

It has always been "surprising". The problem is mostly with maintained ON/OFF switches. The issue Captain Orso describes also happens quite often when your mission has started airborne. Your Gear UP/DOWN switch is in the UP position and the physical switch on your controller is ON. The software has not registered a OFF --> ON transition and therefore doesn't "notice" the transition OFF --> ON when you set the switch to "Gear Down", and so the gear stays up. I have done a few belly landings this way. Nowadays I check that the gear is really extending.

The cause of the issue seems to be that the software does not scan all bound switches at mission start. That's not a problem with pushbutton commands, because every command will generate a OFF --> ON transition (followed by a ON --> OFF transition). Sometimes you can "wake it up". When you cycle one of the maintained ON/OFF switches it will recognize the ON status of the others. I have often seen that in the hog.

ED could reliably fix the problem by scanning the status of all bound switch commands that have a "up" and "value_up" statement in the "default.lua".

[scoobie]

We may be talking about the same, but I'm not sure, so...

While up/down Lua commands do normally react to a "slope", i.e. off/on and on/off transitions, when you have "sync. controls" option on, at the mission start DCS reads your latching switches, but only those in the physical "on" position. It seems to be ignoring switches in the "off" position - instead they are (in the cockpit) set to their "default" state for a specific aircraft configuration ("on" or "off"), for example, in a cold & dark state.
A kind of assymetry, that's how it looks to me - "ON" will be sync'ed, "OFF" won't.

Is that what you're talking about? (I feel I may be mistaken).

 

With axes it seems to be the same thing - axes aren't "read" on mission load, but set to the "default" state proper for a specific configuration of the aircraft (different for cold & dark and for "start in the air" missions), so you need to move them up or down to make DCS read their physical position and only then the plane gets synchronized to your throttle etc. For joystick (stick), I believe we don't see this effect only because the "default" aircraft's state at the mission load is stick centered - and yours is centered too. So at the mission load it's good (but incidentally!), and when you only touch it, its value (X or Y) is immediately read and it's still good.
The question is... is this effect more bad or more good? It does, in a way, ensure your mission starts properly, i.e. even if your controls are in bad positions, nothing bad is going to happen immediately upon the mission load. Maybe this way of thinking stands behind this feature?

 

What troubles me more, however... maybe it's just something messed up on my end, I don't know... It seems that this effect happens also when you switch to external view (F2) and then jump back to F1, the latching switches kind of forget where they were, you need to "wake them up" as LeCuvier calls it. I'm not sure if it's always the case, but I'm seeing this at least often. I like F2 (and F3) to watch my shiny pretty plane
Anybody else having this, by any chance? I'm hoping that I have just messed up my options or something and it's repairable.

 

Edited June 18, 2021 by scoobie