Raids being cancelled - Allied 1943 Campaign

[simovitch]

I'm getting reports from a dev team tester about raids being cancelled for no reason. Seems to start happening around the end of 1943.

These incidents are usually associated with large raids with lots of bombers and escorts. Some raids will still go out, but others are cancelled for no reason.

If you have experienced this, please post a report here so that we can look into it. If you have recently made it through 1943 into 1943 without this happening, please also report here.

[Pete McCullagh]

Guilty....l broke it again. Problem appears when allied air force starts getting significant reinforcement. Getting progressively worse with larger amounts of units.

[JeffroK]

Still in Aug 43, are they reported as cancelled or just not flying??
I'll keep my eyes open.

[simovitch]

I found the problem.
In Pete's saved game there were several missions where the base altitude of the raid (27K-28K) were pushing some of the bombers and high escorts above their allowable ceiling. That's a pretty high raid in my book and once I lowered the raids to the 24K range they all flew without a hitch. I think there may be a % of the max ceiling that prohibits flying but I have to check this.

In the meantime, this is not a gamebreaker enough to code in some error trapping and release a new patch. Just be mindful of your max altitudes and setting those high escorts too high above the main raid. Especially the night bombers of BC.

This ticket is closed.

[simovitch]

Update on this issue:
The game will reset raid altitude automatically if the player sets the raid at an altitude higher than the lead group type max alt, and all other groups will be adjusted to their own service ceiling as well. So the coding is not an issue.

What is happening in this particular instance appears to be related to how the game allocates to system memory when the game pushes itself to the limit as it were. For some reason I can run the savegame fine on my laptop, or in windowed mode, but on my desktop computer it is hit or miss: sometimes all the raids fly and sometimes only some of them fly.

Right clicking the desktop shortcut and selecting "run as administrator" is a confirmed fix for this issue.

You should notice this during the action phase but you can also spot the failed raid by reviewing the action report at the end of the turn. The failed raid will be listed but no results shown, just like if it was cancelled due to bad weather.

I have never seen this before so I'm classifying it as a very rare occurrence but if you see something amiss please report it here.

[Philshaw]

Finding these posts has helped a lot, repeatedly had raids cancel with no reason given on what appear to be decent days.

Am running .83 version, dropped some Liberators from 28k foot down to 24k and they finally launched, but I have had raids go out at this altitude and 30k for fortresses in the past without a problem (they did bomb fromthis altitudesometimes I had believed), I checked the escorts for ceiling, all could make the38k escort alt.

Now the game started under a patch from 2022 iirc, but have patched it. Current game date is 3rd of December 44, (43 Campaign). I do not know if start from fresh the campaign would help?

Edit:

Sorry, just digested the part on memory allocation, might well restart game but as administrator.

Edit 2:

Thank you, run as admin and the raid launches backat 28k altitude.

[Philshaw]

Well, after my spam in the previous message,*I think* it still happens, have sometimes wondered if the Axis oil shortage is affecting the larger allied bombers (as axis do not take off for the RCM planes and intruders that take of).

No message saying cancelled and comparatively clear skies.

[simovitch]

I also found that running the game as administrator is not the panacea I thought it was. This is an issue with the game's memory caused by, as far as I can tell, launching large 400-500+ aircraft raids all at or near the same time.

Fixing this issue, if and when I find a solution, could result in all current saves to be unusable.

So, try launching no more than 300 planes (bombers + escorts) per raid. If you want to go larger, set at least 5 minutes delay between the raids and see if that helps.

[Philshaw]

Thank you for your patience, I spent a lot of my life bug hunting in code, I can imagine it can be frustrating with what must be old code

[Philshaw]

I also found that running the game as administrator is not the panacea I thought it was. This is an issue with the game's memory caused by, as far as I can tell, launching large 400-500+ aircraft raids all at or near the same time.

Fixing this issue, if and when I find a solution, could result in all current saves to be unusable.

So, try launching no more than 300 planes (bombers + escorts) per raid. If you want to go larger, set at least 5 minutes delay between the raids and see if that helps.

I think I have an example of a 192 bomber raid not being canceled, but seemingly never forming. There are no fighters so compared to other to other raids that have run,it is pretty small, any purpose in me sending support the game file?

I think this may be the most raw version of a raid not starting. I think there are a total of 5 mission in the game, this bomber raid and 4 recon.

[simovitch]

go ahead and attach it to a post on this thread. It may need to be zipped, or rename the extension to ".txt" for matrix to allow it to upload here.