A few A20 bugs

[TheWarsimmer]

Haven't played the A20 for a while, but noticed a few things, at least on my end in VR. 

 

1) Once you start the engines, you can no longer work the inlet cowl flap. You have to close it before starting the engine. Oddly, this only happens to me in multiplayer

2) This probably applies to all bombers, but the sight does not work properly in VR unless you have technochat on. For instance, there is no visual change if you set the interval time or how much of your payload you are dropping.

3) Not really a bomber bug, but the new distant buildings option is AMAZING. You can altitude bomb and see your target from forever away, but there's just one problem... you can't tell if the building has been destroyed until you're nearly ontop of it. All the buildings will look fine from a distance, when suddenly you're at that point where you're about to drop only to find that half of the targets have switched from unscathed to rubble.

[LukeFF]

3 hours ago, TheWarsimmer said:

Once you start the engines, you can no longer work the inlet cowl flap. You have to close it before starting the engine. Oddly, this only happens to me in multiplayer

 

Not a bug - you have to have both engines selected, since it's one lever that controls both flaps.

[TheWarsimmer]

Both engines are selected. Tested a few times with the full hud on to confirm, because I had the same suspicions as you.  Both engines are selected by default to begin with. It only occurs on my end when on a mp sever.

 

Tbh that one has the least impact. The requirement for technochat to be on for a fully functioning bomb sight and the distant building rendering not showing if buildings are destroyed is the most practical problem when you bomb from altitude. Perhaps this will be fixed soon. Because the engine can now draw distant buildings, it may not be too much of a stretch to do a quick check if they are destroyed or not and run the appropriate texture. This would allow true high altitude bombing and push those engagements up even higher, being more representative of western front air combat.

Edited November 18, 2019 by TheWarsimmer

[[DBS]TH0R]

8 hours ago, LukeFF said:

 

Not a bug - you have to have both engines selected, since it's one lever that controls both flaps.

 

I've had this happening for several patches now. It manifests itself in MP, and there is only one solution to the problem: game restart.

 

The only workaround that I've found is not touching any of the controls before the engines are up and running, i.e. the engine startup procedure has finished.