Start engine commands no longer works

[dfoxpro]

Tested (/affects) with FC3 su-33 & su-27

How to reproduce:
Go to "Start up" training mission or with mission editor use a cold state plane. Now press any of the key-binds for start engines (RAlt or RCtrl or RShift + Home button).

 

What to expect:

The engine should start (sound, tachometer, throttle and light indication)

 

What really happens:

The engines keep in off state

 

Notes:

· The instructor in the tutorial recognize the start engine commands (left and right engine) and continue with the tutorial.

· It is a soft-lock in many (custom-) missions and tutorials.

· Tested with keyboard and also steam-input controller overlay (steam controller).

 

Video evidence:

 

Mission track (attachment over 5 MB)

https://mega.nz/file/NwV0WJYT#BGoYmBdRsIm8OV-cAz8jt_AC_Dk0dvhO4gtK2RjfWTg

 

Personal note, this month I'm waiting for a virpil hotas, and really really really wanna use my new toys with the Sukhoi planes

 

Edited October 9, 2021 by dfoxpro
bug report guideline changes

[MAXsenna]

Are you using something for a throttle now?
I have this problem once in a while, I only need to advance my throttle then retard it completely, then I can start.

Sent from my MAR-LX1A using Tapatalk

[dfoxpro]

No, only keyboard and steam input (xbox360 controller for DCS) for the joysticks, btw I'm using the stand alone game not the steam game.

 

Any way, yesterday I did more test with(out) vr and got the same results on su 33 (both fails vr and flat-screen) su27(only fails in vr), migs (both fails in vr and flat-screen) and su25 non T(both fails in vr and flat-screen with special note); I double check the key-bind was valid [See attach images].

and a special note on su25: when I press any start engine key-bind, the indicators lights blinks for a jiffy without engine start [See vídeo].

 

 

finally note this is not happen on all airships, for example, the su25T has no problems, the su27 only fails in vr, so it sure wort the analysis and fix.

[dfoxpro]

After more digging I found that the option "set controllers to hotas position" (or something like this) is the trigger to this very bug, disabling this option restore the expected behaviour.

 

Anyway, it's still wrong for some specific ships to be broken with this option, especially when some other ships from the same package and the same quality/type ("ssm"[standard system model?] I believe) work just fine.

 

It's like the other bug-reports, where the su25(T) planes has missing common controls vs the other FC3/SSM planes, like the axis wheel brake and reset trim for example; It should be a more consistent control experience across planes.