I was playing Pac.6 with data base 170909. After getting a couple of hours in to game time I experience game crash to desktop during a save, both manually and autosave, with the save game becoming corrupt and unable to reload. The popup at times would give me

GetMemAnnexA Error: !IS_DISK)65535 [oxffff]) = 65536. I began to repeat the process with a game save about a minute before the crashes would occurred repeatedly and attempted save game would not reload as I believed it was corrupted. I then noticed an event the

proceeded the save crashes. The AI's helicopters would start crashing due to no intervention of my own mainly in task groups. Once this event took place a saved game attempt, manually or auto, would result in the crash to desktop and corrupt save game. I have tried to

recreate it with a smaller scenario but this even seems to take place over time or only when large scenarios are played. I am not sure if this issue has been address before about the save game crashes but know the AI aircraft crashes have in the pass. I have a saved game that

proceeds the event about by a minute and I saved manually every five seconds prior to the AI aircraft crash on their own. Once the aircraft crash any attempted save crashes to desktop and the saved game produce becomes corrupt. As the event happens at the same time every

time I am not sure if the game timer would contribute to it. I am attaching my saved game that is not corrupted and the resulting save game after the event in which I think it was corrupted. My process was to load the good save and immediately save to another save game for

testing to preserve the last good save. The Pac save game is the good save while the autosave was the corrupt save. As by the large change in the save game files a bit seems to be missing in the autosave. One other note is if I turn save to 0 minutes, no autosave, the crash 

happens.

PAC4.hpq autosave.hpq

Thank you Tony, I'll have a look tonight or tomorrow.  Eric has been circling around a similar issue so this could be a big help being able to compare the formation issues popping up for each of you.

No luck as yet.  I've invested about 90 minutes of troubleshooting time so far.  I can fairly regularly get a crash to occur when I start from PAC4.hpq.  However, if I re-load a saved game from either 1 or 2 seconds before the crash, they do not crash when opened and run.  

In short, I haven't found a useful way to isolate the problem yet.

Notes:

Crash at GameTime==112501

Look at group YTC, UnitId==10 in SaveUnitList.  Crash seems to happen on that unit.

At GameTime==112490, YTC UnitId==10 SH-60 SeaHawk has a home-unit (aka base) of YTC UnitId==9, another SH-60.  That is obviously wrong and leads to the crash when UnitId==9 is shot down and the game is saved.

112446 effect4.c:4123 - Group=YRS, UnitId=4, Name=SH-60K Seahawk 06 has an aircraft HomeUnit Group=YRS, UnitId=4, Name=SH-60K Seahawk 06
112446 effect4.c:4123 - Group=YTC, UnitId=10, Name=SH-60K Seahawk 06 has an aircraft HomeUnit Group=YTC, UnitId=9, Name=SH-60K Seahawk 06
112446 effect4.c:4123 - Group=YNS, UnitId=6, Name=S-70C(M) Thunderhawk 94 has an aircraft HomeUnit Group=YNS, UnitId=5, Name=Super Lynx Mk110 05
112446 effect4.c:4123 - Group=YNS, UnitId=7, Name=S-70C(M) Thunderhawk 94 has an aircraft HomeUnit Group=YNS, UnitId=5, Name=Super Lynx Mk110 05

 

Yes I noticed something, by accident,  the other day and was that if you saved after the first three helos crashed you get a good save and all saves after that are also good. So it seems it the problem is it left one helo hanging so to say? I was thinking of trying to see 

if I could recreat the accident and send you that save and some after that for you to look at would that help. 

No need to send anything else at present.  I have fixed the crash (the symptom) but not the root cause (an aircraft being set as the base for another aircraft).  I may need help with that root cause when the time comes.

eeustice is giving the build a bit of a workout.  I also need to see if the fixes break ferrying aircraft groups before posting it up for a larger audience.  In any event, it should be posted in the next 24 hours unless something unforeseen pops up.

Sounds good, let me know if and how I can help.

2019.001 is posted https://harpgamer.com/harpforum/topic/29035-current-files/ 

Let us know how you fare.

Will do. Just to check if I loaded 2018.02 then 2018.11 I can just ahead and loaded 2019.01. Will this version test be able to run from  the save games PAC.4 save game I sent you?

Correct, 2019.001 on top of what you have and you should be able to continue on from your save.

I ran from the save before the crash and experience no more crashing even when I used  save or save as feature. I let it run for awhile with the autosave timer set to 2, 5, and 10 minutes  but the timer would not create  a saved game.   I am pretty sure it was working 

as that is how I noticed the timing of the original crash. I am wondering if I might have disabled it and have contemplated just reloading the whole game again. I thought I would ask if you had any ideas first.

44 minutes ago, Tony said:

I ran from the save before the crash and experience no more crashing even when I used  save or save as feature. I let it run for awhile with the autosave timer set to 2, 5, and 10 minutes  but the timer would not create  a saved game.   I am pretty sure it was working 

as that is how I noticed the timing of the original crash. I am wondering if I might have disabled it and have contemplated just reloading the whole game again. I thought I would ask if you had any ideas first.

You don't need to reload the whole game.  I'll post more later.  

7 hours ago, Tony said:

I ran from the save before the crash and experience no more crashing even when I used  save or save as feature. I let it run for awhile with the autosave timer set to 2, 5, and 10 minutes  but the timer would not create  a saved game.   I am pretty sure it was working 

as that is how I noticed the timing of the original crash. I am wondering if I might have disabled it and have contemplated just reloading the whole game again. I thought I would ask if you had any ideas first.

I took 2019.001 for a spin to look at autosaving and I am not seeing any malfunction when I have the interval set to 2 minutes.

I also fired up the HC Launcher which has the much more useful iterative saving.  When I run the game, I disable the autosave by setting it to 0 minutes and I use the iterative saving instead.  You can find your sweet spot on settings.  I tend towards saving every 10 seconds rotating after 100 saves.  A random note about the launcher, if you find settings you really like, you can copy the listed Command Line into a Windows shortcut to use to run the game in the future with those options.  The limitation (bug?) with iterative saving is that it only activates for the first scenario or save loaded in your game session so if you start a scenario it works, then if you load from the save without closing the game, the iterative saving will stop.

The HC Launcher looks a bit detail for me but would require a bit of study before I tried using it. I have one other request as I have another issue. Could you look at your formation screen from the saved game and 2019.01 and see if it is has been affected. Mine now 

looks like the screen shot below. It allows no interaction.