(***) Preventing and fixing the infamous save game bug Options

[Aztek985]

Originally posted by SMIFFGIG:

--------------------------------------------------------------------------------------------------------------

Here is how to prevent the incredibly annoying and frustrating save game bug from ever occuring or how to fix it in a mod that already has the bug

Firstly the save game bug appears in many TS and FS mods (deezire u reading) it allows you to save your game, but if you try to load up that save again you get the dreaded "Internal Error" message and shuts down TS.

I never used to know what caused this bug and had no chance of curing it, however many thanks to Banshee for telling me what the cause was.

This allowed me to work from there. The cause is the [Animations] section in the Rules.ini if you add any animations to this section the save game bug appears

however in any decent mod you got to add animations and you got to keep the save game feature.. well heres how to do it


You will see the last animation in the list is

CODE

707=INVISO

This is the max, and anything past this =Save game bug
so how do u add animations, quite simple
you dont even have to replace any that are already in the list

You will notice the numbers of the animation down the side of the list, these generally go up in order. However there are many! unused slots and you get jumps like this

CODE

54=FIREPOWR
63=MGUN-N

Well we know we cannot go over the 707 mark, but we can however use up all these slots in between, so from the above u will get the following free slots for your own animations

CODE

54=FIREPOWR
55=
56=
57=
58=
59=
60=
61=
62=
63=MGUN-N

now thats quite a few free slots, check the list and enable all these free slots and u will find u got more than enough room for more slots

I was going to make a template opening all free slots, but im sure u can manage it

My testing was done with both TS and FS and save game worked in both
however in TS: Retro (my mod i tested this with) all animations from the firstrm.ini have been put into the rules.ini

this means that there is possibly many many more slots that can be used for firestorm alone. But i dont know what the max is in firestorm and you would of course only see these anims if u had the addon

anyway thats all

-SMIFFGIG

[Chriz]

:blink:

He sayed the game would reserve 38 after INVISIO... but thats kinda wrong, because it seems to have unlimited numbers... and I doubt it has something to do with FS/ 1.02 Patch

So... When you put any new anim on a spot of an anim that's reserved for Firestorm, you get the savegame bug.

Thats also wrong, it looks like you can change the order and numbers as you like without getting SaveGamebug, but you will ruin some Map scripts

This post has been edited by Chriz: Feb 13 2007, 06:00 PM

[Bittah Commander]

That's probably because the anims from Firestrm.ini are already added to Rules.ini (and possibly removed from Firestrm.ini) and thus those those 38 numbers after 707 are no longer reserved for the numbers from Firestrm.ini (seeming they're already present in Rules.ini).

He sayed the game would reserve 38 after INVISIO... but thats kinda wrong, because it seems to have unlimited numbers... and I doubt it has something to do with FS/ 1.02 Patch

...*sigh*

Anyway, if someone has time, try this...
First simply remove all anims from Firestrm.ini and add a couple new (non-firestorm) anims after 707=Inviso. If the savegame bug doesn't occur now, we know enough.
If the savegame bug still does occur, try adding the anims from Firestrm.ini to Rules.ini before 707=Inviso and add some new animations after 707=Inviso (or simply leave those anims from the previous method if you didn't remove them). Try this with both with and without removing the Firestorm anims from Firestrm.ini.

IF it savegame bug still keeps occuring, try adding all of the anims from Firestrm.ini after right 707=Inviso in Rules.ini (try it with and without removing those anims from Firestrm.ini again) and adding a couple new anims after those.

If what some others posted above is right, the last method should definitely work.