LoL so much delay and so much bugs :grin:

Oh, well ... it seems that it does work on 4.10 DF servers ... after all limited aircraft have been shot down they won't been shown in the list of available aircraft. I'd wish there was an announcement in the chat window about it though ...

Sorry for bothering you, TD! :oops:

Ju 88 model was changed and mapping with it. Old skins do not work 100% anymore.

Late model 109 compasses don't work.

Two potential bugs:

1) Default fuel mixture or supercharger settings set incorrectly for many player controlled aircraft at high altitudes so the plane emits smoke trails. Switching to autopilot/AI control doesn't fix the problem. AI controlled planes don't have the same problem. Example, a flight of 4 Re.2000 over Smolensk (or any QMB) map at 5000+ meters. I've also seen the same problem in the SM79 and Hs129 series. Haven't had a chance to test them all.

2) At the risk of seeming like I'm whining about FM, the G stress limits on the A20 series might not be correctly implemented. As I understand the films and pilot manuals for the A20, the plane was only stressed to withstand 3 Gs, but the G indicator only starts to go red at 4 Gs. Likewise, I'm still able to do the same sort of BFM with an A20C and A20G as I could before the 4.10 patch, repeatedly pulling 5-6 Gs in turns, loops or dive pull outs without breaking the airplane. The only difference is that the plane doesn't seem quite as powerful or maneuverable.

Bugs are bound to crop up with a patch of this size. No need to be a troll about it. :rolleyes:

Thanks for the quick answer!

It has always been this way: 100% mixture and supercharger to 1st gear.Try spawning at 10000 meters with a La-5 in 4.09 and you will see smoke trails and engine running rough.

Seems I`m the only one who flys sometimes singleplayer missions, I have seen this effect in 4.10 more often than in 4.09 Don`t know what causes this, but the AI can`t fly low without crash the plane within minutes. They outmanouver themself with hitting the ground.

:confused:

It could be... you will not get a 'Rodger' from the tower if you ask for the lights before you pass the last beacon. I will try removing the beacons and see what happens.

UPDATE
I removed the blind landing vehicle and every beacon on the map (had to edit mission file as FMB refused to admit AR was gone) it makes no difference. The tower will not 'rodger' your request until you are within 2km and the lights do not come on until you are within 1km.
2nd Update
I have been making a fairly shallow approach so I tried a higher approach (500m at the 4th waypoint) to see if line-of-sight was the problem but the tower still did not acknowledge my request until within 2km (actually 1.6) and the lights turned on at under 1km.