hard2earn@... uploaded file savegame.7z (84.9 KiB)

savegame alpha9

hard2earn@... commented

forgot to mention i was using Stable / 2.2.4 / windows installer.
got em from the dl section of this site.

Buginator changed priority from critical to blocker

Buginator changed operating_system which not transferred by tractive

Buginator changed milestone from unspecified to 2.2.5

Buginator commented

In the same directory where warzone2100.exe is, you will see a file called 'stderr.txt' and in it, it will tell you why it crashed.

error   |11:06:22: [scrv_error] VLO parse error: Template Cyborg Flamer not found at line 255, text: 'Cyb-Flamer-GROUND'
fatal   |11:06:22: [dataScriptLoadVals] Script cam1-5.vlo did not compile
error   |11:06:24: [resLoadFile] resLoadFile: The load function for resource type "SCRIPTVAL" failed for file "cam1-5.vlo"
fatal   |11:06:24: [resLoad] Failed to parse wrf/cam1/sub1-5.wrf
fatal   |11:06:27: [startGameLoop] Shutting down after failure
net     |11:06:30: [NETshutdown] NETshutdown

Script bug--ack!

anonymous commented

apparently it just crashes one me without creating the .txt file u mentioned. at least u seemed to be able to reproduce the error with my savegame, right?
i searched the install folder (where teh wz.exe is) and the local user folder as well.

there was no such 'stderr.txt' as you mentioned b4.

p.s.: what do you mean by "ack!" - acknowledged maybe?

Buginator commented

Replying to Warzone2100/old-trac-import#1027 (comment:3):

apparently it just crashes one me without creating the .txt file u mentioned. at least u seemed to be able to reproduce the error with my savegame, right?
i searched the install folder (where teh wz.exe is) and the local user folder as well.

there was no such 'stderr.txt' as you mentioned b4.

p.s.: what do you mean by "ack!" - acknowledged maybe?

I should have said D'oh! Anyway, these things are hard to track down, so it will take some time.

Thanks for the report!

Buginator commented

For reference, #973 is a duplicate of this, but you have the newer build, so sticking with this ticket.

Buginator commented

Another duplicate is #1028

(sorry about the spam)

hard2earn@... commented

no problem. is there anything i can do to help with this problem?

if so just tell me. i can add more files if u need logs or stuff like it.

regards

Buginator changed priority from blocker to critical

Buginator commented

Well, I did some more tracking, and it looks like it is not a script error per se, yes, it errors out with a script error, but the cause is unknown.

I quick played the game to that level, and I do not get the same error, it just moves on to the next mission.

This leaves me to think it is corruption someplace, but finding the cause of that is even harder than debugging script errors. :(

Did you do anything special, like using any of the cheats or anything?

Would you happen to have the missions before this level that you can upload, so I can check from a earlier point of the game with those?

I'll attach a savegame so you can verify this savegame works... (I don't recommend you use this same savegame to continue your campaign though, since it will spoil some stuff for you.

Buginator uploaded file Sub1-5S-savegame.7z (48.8 KiB)

Sub_1_5S test savegame

Buginator commented

I also noticed that the savegame build date is off...

savegame Oct 11 2009

build Oct 31 2009

Did you use a old savegame from 2.2.3 or earlier version of the game?

rondan69@... commented

I am still starting out with this test

hard2earn@... uploaded file allsavegame.7z (319.6 KiB)

savegames

anonymous commented

Hi.

tx for takin ur time and looking into it again.

1. i did not use any cheats nor mods that came with the installer. 2. as i said i was using the most up to date installer which i DL'ed at the mainsite

your savegame works indeed. to your convinience i uploaded all my savegames.

what came to my mind:

when i started playing the 1st time i had xp64 running. i then made a backup b4 migrating to win7. then dl'ed the client again reinstalled and overwrote all the data with my backups. do you think it is possible that this is where the problems come from?

I don't understand why it makes weird savegames. i did not import any old games cept from what i wrote above. should be the most recent version i have running. the installer was both times the same version.

What i could do is uninstall WZ using REVOuninstaller deleting all data i got and reinstall. then i would have to play again til i reach that level. that can take some time. if that would help i would try it.

Buginator commented

Ok, thanks for the upload, I will check the stuff as soon as I can, my next free day will be the end of the week.

You don't need to use REVOuninstaller, the game does a CRC check when it copies the data, so it should be OK just installing over the previous version.

As for playing the game again from the start, if you wish, you can do that, but I need to find out why the savegames get corrupted for some people, and not others...

anonymous commented

Sorry, I started another ticket about the same problem: http://developer.wz2100.net/ticket/1044
I see one commont thing: we both used a lot of vehicles in previous mission, and when they returned, they were "compressed" on a little landing zone.

Also, I'll attach my full savegames directory. My savegame names are like 4a, 5b, etc, that usually means that 5c was made after 5b and 4a etc. The ones related to crash are those 8, 8b, 8c, 8d, 8e, 8start savegames, all of them should crash just after transport leaves the map.
Despite this, its a great game :)

anonymous uploaded file savcamp.zip (3977.3 KiB)

anonymous commented

Oh, and I also thought about the "bad" savegames. Maybe they're made when you overwrite an existing savegame?

I'm in a mood to replay the game to find out :)

anonymous commented

Ok, I did it :)

I replayed the game, each time I saved I used a new saveslot. And I had no problems and no crashes when transport was leaving the map. Alfa9 mission also works perfectly. Now I've run out of free saveslots, so I guess I'll delete the old ones, and see if I can play without bugs.

Probably something gets messed up when overwriting a savegame. Also, just before Alfa9 mission on the "bugged" save, I was able to resarch Python vehicle body. On "normal" save that's not possible.

anonymous commented

Oh, I didn't replay the whole game, just to Alfa9 mission :) - I'm not that sick... ^^

Buginator commented

Thanks for the savegames, highly appreciated! :)

As for the overwriting, we delete the old files first, then create new ones...so I am not sure how it can screw up there.

Still trying to find out what causes this, but due to lack of time, not getting anywhere fast. :(

anonymous commented

I can only say that I didn't do any save overwriting and had no crashes after transport left the map. And previously, (when I did overwriting) I had a few crashes and couldn't progress to Alfa9 mission. So, I can say that creating a new savegame each time 'fixes' the bug.
Its similar to: http://developer.wz2100.net/ticket/768

However, I still have crashes in Intelligence Display, same as: http://developer.wz2100.net/ticket/1025 so they should be unrelated to savegame files.
And I'll probably try to find out why their occur - they're much more annoying.

Buginator commented

Replying to Warzone2100/old-trac-import#1027 (comment:18):

However, I still have crashes in Intelligence Display, same as: http://developer.wz2100.net/ticket/1025 so they should be unrelated to savegame files.
And I'll probably try to find out why their occur - they're much more annoying.

Almost all the times I have looked, the crashes in the Intel Display are the fault of bad video drivers.

Buginator changed status from new to closed

Buginator set resolution to needinfo

Buginator commented

For the crashes in intelligence Display, that is almost certainly a video driver bug.

For the other issues, I can't replicate it, and if we can't replicate it, then we can't fix the issue.

I am out of ideas.

If you have any more thoughts on how we can replicate this issue, then respond back to this ticket.

Thanks for the report.

Buginator changed milestone from 2.2.5 to 2.3

Buginator commented

Milestone 2.2.5 deleted