MP: Sound and key bind problems

[[DBS]TH0R]

Last night after map rotation, I was flying in A-20. The video below features sound problems that I have encountered, with inability to control the inlet cowl shutters thus rendering A-20 inoperable:

 

 

As I wrote in the video description, I am aware that game restart help in solving the sound issue - but the inlet cowl shutters bug not responding to both keyboard and controller commands is present for a few patches now.

Edited April 6, 2019 by [DBS]TH0R

[airahusky]

В 06.04.2019 в 11:02, [DBS]TH0R сказал:

the inlet cowl shutters bug not responding to both keyboard and controller commands is present for a few patches now.

Are you sure you turned off the automatic radiator control? (LSHift+R)

[[DBS]TH0R]

Never touched it, or ever do. Didn't even know it existed in A-20... This happens rarely, but when it does it is very annoying.

[[DBS]TH0R]

UPDATE: Restarting the game and rejoining the server fixes the issue. Thank you =TBAS= guys for the tip on how to work around this.

[Matt]

Could be that you selected both engines manually (1 and 2 buttons on the keyboard). Atleast i'm assuming you did that, because the throttle shows slightly different % for each engine.

 

If you do that, the inlet cowl shutter command does not work. It's mandatory to use the "select all engines" command (default 0 button on the keyboard). Only then you can control the inlet cowl shutters. Unfortunately it's supposed to work that way.

[[DBS]TH0R]

Throttles are on Warthog throttle - each set for each engine, I just mechanically link them and advance them together. They are about 1% different when moved to desired position. I try correcting it when ever I need them in perfect sync.

 

I did try deselecting both engines, and then selecting them again (known Pe-2 engines bug). The above mentioned bug fix was tested working on KOTA this Saturday. Only restarting the game and rejoining the server solved the issue. Also worth mentioning - don't touch your controls until the engine startup sequence is complete. That borked the controls (i.e. made them non working) again after restart.

 

Second restart and all was working throughout the event.

 

I was told this was a common bug, many experience this. Hoping it gets fixed.

Edited April 14, 2019 by [DBS]TH0R