Can't load savegame in ubuntu gutsy

[kopolov]

dpkg -l | grep physfs
ii  libphysfs-1.0-0                            1.0.0-5                        filesystem abstraction library for game prog

hope this helps

[Buginator]

Well, good news, and bad news.

Good news is you can load those savegames up, If you play with no sound.
warzone2100 --nosound

Bad news is your playing with no sound.

There is a screwy pointer being saved, and this is causing issues on load.
Finding where this happens, and why will take some serious time.

No, I don't know why other systems don't seem to have this issue.  I just know that after spending some time with devil spawn (aka gdb) I do not get crashes if I do the nosound command line option.

So, either start a new game with sound, and don't ever quit   or use the temp fix of playing without sound, or use the level skip cheat to get to the level you want (but that doesn't work on all levels for another strange reason--and has other issues as well, just like you shouldn't use time compression all the time).

[holotz]

--nosound doesn't help.

it kicks me back to desktop and resolution is screwed (becomes something like 640x480).
i need to log out and log in again to restore resolution.

[Buginator]

--nosound doesn't help.

it kicks me back to desktop and resolution is screwed (becomes something like 640x480).
i need to log out and log in again to restore resolution.

Try --window --nosound --debug all
I verified multiple times now that it can load the savegames that way.

Are you using the 64bit version of the OS?  I have only tested on 32bit so far.

[Buginator]

I forgot to mention, those of you that have issues, please upload the savegame directory, and the *.es & *.gam files so I can take a look at them.

If you named the save game  "mission1", then tar/zip up the whole directory  mission1, and everything in it, and then also add mission1.es and mission1.gam.

You can attach it to your message.


Thanks.

[holotz]

--window --nosound --debug all doesn't work either.

This time window is closed.

I'm using 32 bit version.

I attached savegame files.

[Buginator]

--window --nosound --debug all doesn't work either.

This time window is closed.

I'm using 32 bit version.

I attached savegame files.

You got a different problem.  For you, it is trying to load " multiplay/players/Ð.sta"  Which don't exists.
remove your ./warzone* directory (or rename it), and let it create a new one.
Then it should set everything to default.

Unless of course, you have a player name of  "Ð" , which I don't.  So I can't really test it.

So after you wipe/rename that directory, you can then play for a bit, and savegame a few times.  If you crash on loading the savegame, then my patch to fix the issue I was talking about is in the patch tracker #855.

Just upload the file again if you have more issues.

Oh, and if you used the --debug all switch, it should have someplace in your terminal, about the missing file?  (You can capture the output by doing  Warzone2100 --debug all 2>err.txt 1>warns.txt          Or whatever.



Thanks.

[holotz]

I removed the .warzone2100 directory. Still can't load savegames.

I don't understand why it tried to load multiplay/players/Ð.sta. I was playing single player. I didn't have a player name of Ð.

I'm uploading savegame files and --debug all output.

By the way how can I find the patch you mentioned?

[Buginator]

I removed the .warzone2100 directory. Still can't load savegames.

I don't understand why it tried to load multiplay/players/Ð.sta. I was playing single player. I didn't have a player name of Ð.

I'm uploading savegame files and --debug all output.

By the way how can I find the patch you mentioned?

The patch is at the GNA site for this project(https://gna.org/projects/warzone/).  But that won't help your issue.
You got something else going on.  This time around, expectedFileSize = 2,583,691,276.  That is just a tad bit wrong.  The whole header it reads in has the wrong data.
No, I don't know why it is doing that.  I can't get it to do that when I run ubuntu 7.10.  I can't get it to do this when on windows either.  Spent the last 1 hour saving & loading games on u7.10, and can't replicate this. All my games load/save fine. 


Can you give some specifics on what you were doing at the time, and what level you were playing?

Is your system memtest & prime95 stable ?
What is your complete system specs?
Did you compile it yourself from trunk?

[kopolov]

I attached one of my savedgames with the .es .gam files
The mission name was "6" (not to original, but it helps me to keep count).

[holotz]

I have ATI Radeon xpress 200 for graphics and sb450 hda audio. I tried
sudo memtest all 1
but it was taking too much time I killed it with ctrl+c.

I installed ubuntu 7.10 through CD.

I installed and removed warzone several times. First with synaptic then removed it and tried deb file and I think I also tried binary install file. None worked, so I removed and installed again with synaptic.

I was playing at normal level.

Maybe there is some pointer bug somewhere and it causes something different each time? Cause I get the same error message as everyone.

[Buginator]

I attached one of my savedgames with the .es .gam files
The mission name was "6" (not to original, but it helps me to keep count).

You have the same issue as holotz.
The issue is expectedFileSize = 3690987532 which is just not possible to have that kind of file size for this game.
What hardware do you got ?
What game level, and what were you doing at the time?


Holotz, the memtest I was talking about is the memtest option available on the ubuntu boot CD, or you can get it from:
http://www.memtest86.com/

Oh, and yes, it seems it is either a bad pointer, or some corruption going on.  But if I can't replicate it, I can't fix it.

[Buginator]

Slight update, I again played straight through for 6 missions, with no cheats at all, and saved every time I was asked to savegame/continue, so I did.
Then I got a unrelated crash, 'cause I did cheat  [got bored ], and couldn't continue on.
Then I went back and tried to load all those games, and didn't have any issues.


Do a svn update, for the trunk release, [sidenote, I do have all my patches in my version, since I forgot they didn't add them yet]  then ./autogen.sh  then do  ./configure --enable debug and finally do make.

When that is done, and you do your sudo make install, *before* that, go into /usr/local/.../warzone2100 and delete the warzone.wz & mp.wz files there.
Then do the sudo make install.

Now, do:
gdb warzone2100
(in gdb now, type run followed my any command line arguments you want like:)
run --window --debug all 2>err.txt
[game should start]
do whatever you can do to make it crash.
then at the gdb prompt type:
set logging file wzgdbdump.txt
set logging ON
bt full
[hit return until your back at the gdb prompt]
set logging OFF
quit

Then attach the wzgdbdump.txt here, and if you can always replicate this, then include the save game files as I specified before.

It would be much appreciated, since I can't replicate these errors.

TIA!

[kopolov]

Sorry,
can you please write it down in "copy paste" commands (I am not that familiar with linux ... still a newbie ...  :-\ )

[Buginator]

Sorry,
can you please write it down in "copy paste" commands (I am not that familiar with linux ... still a newbie ...  :-\ )

I am a noob to linux as well.
I forget to ask what version of WZ people are running.  I am using the svn trunk version.  That is the version I work on, and which  the patches I did are available for.



To get the trunk version,

Make a directory where you want wz.
cd to that directory
now do:  svn co http://svn.gna.org/svn/warzone/trunk
After it gets everything, then you do the following commands:
./autogen.sh
./configure --enable-debug=yes
make
sudo make install

Note, you might get some errors with either autogen.sh or configure.  Just means you have to download the headers & libs of all the libraries that this project uses.  Things like physfs, quesoGLC, and other ones.


Then once that is done, just follow what I wrote above, and it should be simple enough to do.