Shaking in the backseat of a multicrew aircraft while on the carrier

When occupying the RIO seat in the Tomcat being on Multiplayer, cold & dark on the carrier, everything is fine.

As soon as the turbines are started, the view in the backseat starts to shake.

This shakeing is so disturbing that you start to get sick in VR and you are also nearly unable to flip a switch cause you just can't click it.

When you are airbourne, everything is fine again and the shaking is gone.

This problem existet when the Tomcat was released. A few weeks later it was gone. Since a few patches, it is here again.

Please prioritize to fix that issue, as it is a big problem when operating this aircraft as it is intend to be.

Thank you very much in the name of everyone flying as a RIO.

I can confirm the issue. As soon as the engines start it starts to shake violently for the RIO. Luckily I'm not playing in VR :puke:

The shaking stopps as soon as the aircraft hooks into the catapult, which makes me think that this issue (which probably is an ED issue at its core) could be worked around if wheel chocks would be made available to tie the aircraft down on the deck, just like when hooked into the catapult, although I'm not sure if wheel chocks will have the same effect.

For now I have to tell my pilots to wait with engine startup untill I'm done with my startup process when starting on the carrier.

No one else sees a problem in that disturbing issue?

Yes its been reported and reported again like many other carrier issues. They seemingly never get attention...

Any news on that issue? Its impossible to click on a button being RIO...

Really a disturbing bug :-(

Any news on that issue?

It is so unbelieveable disturbing!

The Tomcat is a multicrew carrier aircraft, and it is impossible to hit a single button in the backseat as soon as the engines start!

PLEASE fix that, or even aknowledge it!

i can't believe that not more people are bringing up that issue...

It's probably not something that is easy to fix (and maybe requires ED to do something) and as it is not a gamebreaking bug either it's probably low priority.

Side question: Does the same issue persist with the L-39 on a carrier?

Need to try it one day with the L-39, but as the whole sync is really messed up, I'd guess it will be the same.

Caught it on tape yesterday:

I-LV6A3ManE

I would not see that as a low priority bug...