Hunting the big savegame bug progress

**bn880** · Feb 1 2004, 01:17

Okay, I think everyone now knows how missions with a large Gamestate Variable space can cause a savegame to fail with a message like "error no entry at 'continue.bin/GameState/Variables/Item11/data.value'"

Along with Dinger I think I have isolated one of the issues with the save/load game Variable state:

Attempting to load this GameState from a continue.fps will cause the error <table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">savepath Error no entry at 'continue.bin/GameState/Variables/Item11/data.value'.[/QUOTE]
or
<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">savepath Error no entry at 'continue.bin/GameState/Variables/Item12/data.value'.[/QUOTE]
depending on the names of the Variables

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">class GameState
{
class Variables
{
items=30;
class Item0
{

name="a";
class data
{
type=2;
class value
{
items=1;
class Item0
{
class data
{
type=1;
value=1.0;
};

};

};

};
readOnly=0;
};

class Item1
{
name="b";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item2
{
name="c";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item3
{
name="d";
class data
{
type=1;
value=30.0;
};

readOnly=0;
};

class Item4
{
name="e";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item5
{
name="f";
class data
{
type=1;
value=42.0;
};

readOnly=0;
};

class Item6
{
name="g";
class data
{
type=1;
value=-1.0;
};

readOnly=0;
};

class Item7
{
name="h";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item8
{
name="i";
class data
{
type=1;
value=0.0;
};

readOnly=0;
};

class Item9
{
name="j";
class data
{
type=1;
value=945.247131;
};

readOnly=0;
};

class Item10
{
name="k";
class data
{
type=1;
value=-1.0;
};

readOnly=0;
};

class Item11
{

name="l";
class data
{
type=1;
value=36.0;
};

readOnly=0;
};

class Item12
{
name="m";
class data
{
type=1;
value=3.0;
};

readOnly=0;
};

class Item13
{
name="n";
class data
{
type=1;
value=0.0;
};

readOnly=0;
};

class Item14
{
name="o";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item15
{
name="p";
class data
{
type=1;
value=0.3;
};

readOnly=0;
};

class Item16
{
name="q";
class data
{
type=1;
value=0.0;
};

readOnly=0;
};

class Item17
{
name="r";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item18
{
name="s";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item19
{
name="t";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item20
{
name="u";
class data
{
type=1;
value=0.0;
};

readOnly=0;
};

class Item21
{
name="v";
class data
{
type=1;
value=-1.0;
};

readOnly=0;
};

class Item22
{
name="w";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item23
{
name="x";
class data
{
type=1;
value=-1.0;
};

readOnly=0;
};

class Item24
{
name="this";
class data
{
type=256;
class value
{
id=0;
};

};

readOnly=1;
};

class Item25
{
name="y";
class data
{
type=4;
value=1;
};

readOnly=0;
};

class Item26
{
name="z";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item27
{
name="aa";
class data
{
type=1;
value=-1.0;
};

readOnly=0;
};

class Item28
{
name="bb";
class data
{
type=1;
value=0.0;
};

readOnly=0;
};

class Item29
{
name="cc";
class data
{
type=1;
value=30.0;
};

readOnly=0;
};

};

};[/QUOTE]

However, renaming the array at entry Item0 to 'za' makes the problem go away. Similarly swaping the array at Item0 with Item11 or Item12 fixes the problem. It depends on the naming of the variables.

<table border="0" align="center" width="95%" cellpadding="0" cellspacing="0"><tr><td>Code Sample </td></tr><tr><td id="CODE">class GameState
{
class Variables
{
items=30;
class Item0
{

name="za";
class data
{
type=2;
class value
{
items=1;
class Item0
{
class data
{
type=1;
value=1.0;
};

};

};

};
readOnly=0;
};

class Item1
{
name="b";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item2
{
name="c";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item3
{
name="d";
class data
{
type=1;
value=30.0;
};

readOnly=0;
};

class Item4
{
name="e";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item5
{
name="f";
class data
{
type=1;
value=42.0;
};

readOnly=0;
};

class Item6
{
name="g";
class data
{
type=1;
value=-1.0;
};

readOnly=0;
};

class Item7
{
name="h";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item8
{
name="i";
class data
{
type=1;
value=0.0;
};

readOnly=0;
};

class Item9
{
name="j";
class data
{
type=1;
value=945.247131;
};

readOnly=0;
};

class Item10
{
name="k";
class data
{
type=1;
value=-1.0;
};

readOnly=0;
};

class Item11
{

name="l";
class data
{
type=1;
value=36.0;
};

readOnly=0;
};

class Item12
{
name="m";
class data
{
type=1;
value=3.0;
};

readOnly=0;
};

class Item13
{
name="n";
class data
{
type=1;
value=0.0;
};

readOnly=0;
};

class Item14
{
name="o";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item15
{
name="p";
class data
{
type=1;
value=0.3;
};

readOnly=0;
};

class Item16
{
name="q";
class data
{
type=1;
value=0.0;
};

readOnly=0;
};

class Item17
{
name="r";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item18
{
name="s";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item19
{
name="t";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item20
{
name="u";
class data
{
type=1;
value=0.0;
};

readOnly=0;
};

class Item21
{
name="v";
class data
{
type=1;
value=-1.0;
};

readOnly=0;
};

class Item22
{
name="w";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item23
{
name="x";
class data
{
type=1;
value=-1.0;
};

readOnly=0;
};

class Item24
{
name="this";
class data
{
type=256;
class value
{
id=0;
};

};

readOnly=1;
};

class Item25
{
name="y";
class data
{
type=4;
value=1;
};

readOnly=0;
};

class Item26
{
name="z";
class data
{
type=1;
value=1.0;
};

readOnly=0;
};

class Item27
{
name="aa";
class data
{
type=1;
value=-1.0;
};

readOnly=0;
};

class Item28
{
name="bb";
class data
{
type=1;
value=0.0;
};

readOnly=0;
};

class Item29
{
name="cc";
class data
{
type=1;
value=30.0;
};

readOnly=0;
};

};

};[/QUOTE]

Obviously in a small mission such as this you will not get this improper GameState ordering, but I extracted the first 30 entries from a huge savegame what was failing. And this is one of the causes, it appears that saving and loading must have a specific order of arrays or variable names which is not adhered to during save of huge missions GameState.

**Dinger** · Feb 1 2004, 04:06

What does this mean/why is it important?

First, Bn880 did the work. I just sat there chasing my own problems (speaking of which, don't _EVER_ name a magazine with a class that begins wtih a CfgModels entry class name).

Second, yes, this continues the "Chasing the big CTD" problem, by a different approach. Bn880 spent a lot of time with huge (3 meg) savegame files, monkeying with parameters until he isolated the problem to variables and 6 k.

Third, yeah, bn880 think's he's isolated this bug. The isolation isn't good enough yet to prepare a "Savegame corrector", but hopefully BIS will take notice, it will now be a minor matter and they'll be able to slip this one in. That's the most optimistic reading possible; frankly I'm amazed they continue to support this product so far after release. So we hope bn880's work here gives them at least goods to prevent this in future products.

Okay, fourth, for those of you wondering: this is from a "CoC internal" program written by Confucius. No we're not trying to hide anything; We at CoC don't believe in secrecy. Confucius went "off the reservation", and as soon as we can get ahold of him, we'll release the product.

**toadlife** · Feb 1 2004, 04:57

Good job guys!

I really hope BIS can slip this one in. The savegame bug is a real modkiller.

**bn880** · Feb 3 2004, 13:28

Small bump in case BIS has not spotted this...

EDIT: stupid spelling mistake

**bn880** · Feb 3 2004, 14:24

Originally Posted by (toadlife @ Feb. 01 2004,00:57)

Good job guys!

I really hope BIS can slip this one in. The savegame bug is a real modkiller.

Yes and it is a real CE+UA killer as well, it also pretty much killed my personal enhusiasm in The Working Mission.

I consider a bug like this kind of a core problem, when a savegame can not be loaded...

**m21man** · Feb 3 2004, 14:32

Hopefully they can fix this soon (I'm ready for another beta patch

).

**void_false** · Feb 3 2004, 17:15

no offensive, but i would like to say some1 "go to hell!!"

I have never expirenced this problem. But after i read this topic - it follows me everywhere. Now i cant save nor load!

now i must play missions without loading at all. even loading autosaves cause CTD. I don't know what to do. and even worst thing that i dont know the reason what caused this?

**DayGlow** · Feb 10 2004, 00:22

this bug has stopped me from playing OFP. Hope it gets fixed.

**Dwarden** · Feb 17 2004, 03:54

bn880 You reported this to BIS directly too?

**Javito1986** · Feb 17 2004, 20:59

So, is there a way for us to fix it and play our missions normally?

Thread: Hunting the big savegame bug progress

Thread Tools

Display

Posting Permissions