Vyazma Soviet aircraft XP bug

[CoolDTA]

If you destroy enough Soviet aircraft in the Novgorod scen, you fulfil a secondary objective which should lower the experience of the enemy airforce in the following scenario (Vyazma). However, it doesn't seem to work.

This is what you have after mishandling the VVS:




Here you see a MiG-3 at Vyazma. If and when you have achieved the secondary objective at Novgorod, it should have 2.5 stars, but as you can see it has 3.5. This should only happen if you failed the objective, but the trigger doesn't work correctly.




Here is another plane, LaGG-3. It should have two stars, but has three. Other Soviet planes spawned in the first wave also have an incorrect exp value in the same way.




This potential bug doesn't matter much to me (or the vast amount of better players), because it only means it takes a turn or two longer to wipe out the Soviet airforce. But I guess it would be better to root out bugs whenever possible. Maybe someone skilled enough could check this out. My humble wish is that perhaps the dux inquisitor Bru could take a look...

[terminator]

It seems that it is the opposite which occurs: instead of having less experimented units, we have more experimented units :

Screenshot 1073.jpg (239.68 KiB) Viewed 1416 times

[Erik2]

Added to bug database

[bru888]

And to Current Bugs - Version 7.1.4 for the benefit of the general public.

[CoolDTA]

Thanks, terminator and Erik! That is what I thought, but there is another related check in the Setup-section. Maybe this check was supposed to override the one in the terminator's screen capture, but it does just the opposite. No idea actually.

[bebro]

Thanks, terminator and Erik! That is what I thought, but there is another related check in the Setup-section. Maybe this check was supposed to override the one in the terminator's screen capture, but it does just the opposite. No idea actually.

Thx for reporting. I check that.

[GabeKnight]

And there are the map overlays missing in the campaign overview, as seen in the topmost screenshot. I remember someone else mentioning this before, but to be sure, added to the BugDB.