This fix will appear in the eFalcon v1.09
This is what I just received from Julian Onions a guy that get things done in Falcon engine. He explains what was the problem in code considering the 128 segment campaigns.
Thank you Julian!quote:
There were about 2 parts to the
problem.
1) 2 instances of a hardcoded 1024, that I had been suspicious of for a
while, but they never seeme to affect anything, so I'd left them til
now, but put an assertion next to them so I got notified if it went out
of range. Well it went out of range on that latest campaign you sent
me, so I used the map size instead. I think this only affects unit display on
the planning map though.
2) The big one, was the internal map it keeps of SAM activity. It uses this
to plan the ingress/egress routes for the missions. It works this out by
building a small scale map of the theater with SAM status on it.
It divides the regular map by 6 to get a low res SAM affected status
On regular maps, this is
516/6 * 512/6 = 7235 squares
It holds the sam map size in a short integer, 16 bits, signed.
Range of that is -32768 to 32768
On you map - this is
2048/6 * 2048/6 = 116394
which overflows the size, in fact it wraps around, so if considers the
sam map size to be negative.
Anyway - when planning the ingress route, because this is negative, it
can't access the sam map, and falls out of the sam avoidance routine
with a status, that basically says "Its too dangerous to attempt this
mission".
Therefore, it tries to allocate SEAD strikes against the supposed SAMs
first, before trying to attack the intended targets. Of course the SEAD
strikes that are then planned find their ingress routes are too
dangerous too, so its continually allocating and cancelling packages.
Julian.
PMC TFW
Snake Man
