Kirill/Anton - Have you noticed the glitch with the map in single missions?

[Araqiel]

Originally Posted by Ancient Seraph

The reason it feels like the plane is trying to fly itself is because it is. In some single missions you have the possiblity to fly all planes in your flight. You can switch between these flights by going to the map and using the up and down arrows to select different pilots/aircraft. As soon as you enter the map menu, the plane will try to fly itself. I have no idea however where they're designed to go, so can't help you with that.

Ah, I see, so it's an issue with the tactical control? The issue presumably being that while in map view the player aircraft is now considered another AI-controlled wingman, whether you actually move the stick to select a different aircraft or not. So perhaps all that would need to be changed is for being in map view while on tac. control missions to still give you control over the aircraft, albeit control you couldn't actually make use of in map view as the stick selects wingmen instead. This would leave your aircraft on the heading you left it on, as if you were just not touching the controls.

[InfiniteStates]

Yeah I've mentioned this problem before too, but I'm sure you can still fly your plane while the map is up, and the d-pad selects wingmen. So there's no need for AI control until you do actually choose someone else.

I'm also noticing the lost engine noise of the LA-5FN as well. In CTA games (any difficulty, virtual cockpit) the engine noise goes after landing.

Hadn't noticed the flaps one - that one sounds like the worst of the 3 issues..!

[ontheborderland]

On the inspect the airfields mission, I made the mistake of pulling up the map while landed, and the freakin' AI drove the plane into the side of a building!

[Araqiel]

Originally Posted by ontheborderland

On the inspect the airfields mission, I made the mistake of pulling up the map while landed, and the freakin' AI drove the plane into the side of a building!

Hah, I did this too. Hopefully there's something in the patch to address this issue, but having heard very little I can't say it seems too likely.