OK, here is your bizarre AI behavior of the day:
In this mission file, the JU-87s will immediately drop their bombs upon spawning in:
In this very similar example, they will function as expected--no immediate bomb drop:Code:[PARTS] core.100 bob.100 tobruk.100 [MAIN] MAP Land$Online_Volcanic_Island DespawnAfterLandingTimeout 600 BattleArea 0 0 32768 40960 10000 TIME 10.0000002421439 WeatherIndex 0 CloudsHeight 1000 BreezeActivity 10 ThermalActivity 10 [GlobalWind_0] Power 3.000 0.000 0.000 BottomBound 0.00 TopBound 1500.00 GustPower 0 GustAngle 45 [splines] [AirGroups] tobruk:Tobruk_LW_KG77_III.11 [tobruk:Tobruk_LW_KG77_III.11] Flight0 1 2 Class Aircraft.Ju-87B-2 Formation LINEABREAST CallSign 11 Fuel 37 Weapons 1 1 2 1 Detonator Bomb.SC-500_GradeIII_J 0 -1 0.08 Detonator Bomb.SC-50_GradeII_J_DivePreferred 0 -1 0.08 Detonator Bomb.SD-250_JB 0 -1 0.08 Detonator Bomb.SD-500_E 0 -1 0.08 Detonator Bomb.SC-250_Type2_J 0 -1 0.08 SetOnPark 1 Skill 0.32 0.32 0.32 0.95 0.32 0.32 0.32 0.32 Aging 65 [tobruk:Tobruk_LW_KG77_III.11_Way] NORMFLY 13675.02 25513.72 100.00 300.00 NORMFLY 6864.82 7906.08 100.00 240.00 NORMFLY 769.28 848.42 100.00 240.00 NORMFLY 3524.80 406.95 690.00 240.00 NORMFLY 5308.09 4894.76 690.00 240.00 LANDING 5919.10 8855.90 264.00 240.00 LANDING 5100.72 3512.42 264.00 300.00 [CustomChiefs] [Chiefs] [0_Chief_Road] [Stationary] [Buildings] [BuildingsLinks]
The difference, as you may have seen, is that the first example has two LANDING waypoints in a row. You can't do this from FMB but if you are generating waypoints programmatically or by hand it is easy to do.Code:[PARTS] core.100 bob.100 tobruk.100 [MAIN] MAP Land$Online_Volcanic_Island DespawnAfterLandingTimeout 600 BattleArea 0 0 32768 40960 10000 TIME 10.0000002421439 WeatherIndex 0 CloudsHeight 1000 BreezeActivity 10 ThermalActivity 10 [GlobalWind_0] Power 3.000 0.000 0.000 BottomBound 0.00 TopBound 1500.00 GustPower 0 GustAngle 45 [splines] [AirGroups] tobruk:Tobruk_LW_KG77_III.11 [tobruk:Tobruk_LW_KG77_III.11] Flight0 1 2 Class Aircraft.Ju-87B-2 Formation LINEABREAST CallSign 11 Fuel 37 Weapons 1 1 2 1 Detonator Bomb.SC-500_GradeIII_J 0 -1 0.08 Detonator Bomb.SC-50_GradeII_J_DivePreferred 0 -1 0.08 Detonator Bomb.SD-250_JB 0 -1 0.08 Detonator Bomb.SD-500_E 0 -1 0.08 Detonator Bomb.SC-250_Type2_J 0 -1 0.08 SetOnPark 1 Skill 0.32 0.32 0.32 0.95 0.32 0.32 0.32 0.32 Aging 65 [tobruk:Tobruk_LW_KG77_III.11_Way] NORMFLY 13675.02 25513.72 100.00 300.00 NORMFLY 6864.82 7906.08 100.00 240.00 NORMFLY 769.28 848.42 100.00 240.00 NORMFLY 3524.80 406.95 690.00 240.00 NORMFLY 5308.09 4894.76 690.00 240.00 LANDING 5919.10 8855.90 264.00 240.00 [CustomChiefs] [Chiefs] [0_Chief_Road] [Stationary] [Buildings] [BuildingsLinks]
(In fact in CloD 4.5 where AI didn't land reliably something like this was our normal practice - we had another routine that would come along and take care of "LANDING" aircraft that hadn't actually landed, after a while. You didn't want AI aircraft circling commonly-used airports endlessly, so you would send them to the first airport to attempt landing, which sometimes they did successfully, then after a while send them elsewhere to "land" which actually meant be despawned periodically. Anyway, a long story but one that is pretty unnecessary in 5.0 now that AI actually land correctly!)
If ALL aircraft behaved like this it would be one thing, but as near as I can tell, only the JU-87 jettisons all bombs in this scenario. Perhaps some others do it as well--I didn't test each and every possible bomb-carrying aircraft systematically. But I tested quite a large number and of the ones I tested, only the JU-87 acts this way.
Just something to be aware of, if your AI aircraft are jettisoning their bomb load at the very start of their flight, for no particular reason that you can see.
Bookmarks