Warzone crashes on execution

[The Wicked Flea]

Hey all, I'm totally new to Warzone but enjoying it so far. Warzone worked before I had to rebuild my computer. This is an XP Home SP3 system, with nVidia Forceware 178.24 drivers for a Geforce 9800GT.

I'd upload settings or a log, but the game doesn't get far enough to generate either.

I've downloaded and installed the prerequisites (SDL, SDL_net, GLC, etc) into the system32 folder, and tried both version 2.1.1 and 2.1. No change in results even when the libraries are in the executable's folder.

[jaakan]

Hey all, I'm totally new to Warzone but enjoying it so far. Warzone worked before I had to rebuild my computer. This is an XP Home SP3 system, with nVidia Forceware 178.24 drivers for a Radeon 9800GT.

I'd upload settings or a log, but the game doesn't get far enough to generate either.

I've downloaded and installed the prerequisites (SDL, SDL_net, GLC, etc) into the system32 folder, and tried both version 2.1.1 and 2.1. No change in results even when the libraries are in the executable's folder.

why are you using Nvidia drivers for ATI/AMD hardware? wait wait you mean GeForce 9800GT and not Radeon 9800 Pro right?

Get the Windows Installer (Debug version) if you have not already. http://www.wz2100.net/download
start it like this
"C:\Program Files\Warzone 2100\warzone2100.exe" --debug all --debugfile c:\wzdebug.txt
http://wiki.wz2100.net/Command_Line_Options

and have read of this viewtopic.php?f=4&t=691

[The Wicked Flea]

Ack, typo. nVidia Geforce 9800GT. I have no idea why I typed Radeon.

Now that you know I'm not a total idiot, besides possessing rather fumbling fingers, and that I do have the correct drivers... does anyone have a clue why this is failing? I was able to play TA:Spring just fine yesterday.

[Phoenix666]

Which error you have?

[The Wicked Flea]

None that I can find. Once I start the program all I get is the Windows XP "Submit Error" dialog. There is no log, no configuration file, and no notification of an exception. Warzone simply dies immediately. :-S

I'm getting the debug version right now, but I won't have a chance to test it for at least a day.

[The Wicked Flea]

@jaakan: Okay, the debug build actually crashes before the log handle is allocated. Thus somewhere in the extremely early initialization the engine simply crashes. The command I used was: "C:\Program Files\Warzone 2100\warzone2100.exe" --debug all --debugfile c:\wzlog.txt

[Buginator]

@jaakan: Okay, the debug build actually crashes before the log handle is allocated. Thus somewhere in the extremely early initialization the engine simply crashes. The command I used was: "C:\Program Files\Warzone 2100\warzone2100.exe" --debug all --debugfile c:\wzlog.txt

Please get a nightly debug build and enter this on the command line/shorcut:
--flush-debug-stderr --debug all

That should give more info.

[The Wicked Flea]

I can't seem to find where to get a nightly build from. I've looked around, but aside from checking out the source and building it myself (which is a bad idea, since I don't know C/C++ that well) I'm rather lost.

Trying that option with the standard 2.1.1 debug build produces nothing, no log in the console or in the text file.

[Zarel]

I can't seem to find where to get a nightly build from. I've looked around, but aside from checking out the source and building it myself (which is a bad idea, since I don't know C/C++ that well) I'm rather lost.

Trying that option with the standard 2.1.1 debug build produces nothing, no log in the console or in the text file.

http://warzone.mortis.eu/nightly-builds/

Current nightly debug is: http://warzone.mortis.eu/nightly-builds ... -debug.exe

[The Wicked Flea]

Thanks Zarel.

And I'm sorry to sound redundant, but there is still no log file and no settings. Not even output to the console window. This is using that very same nightly build in fact.

[stiv]

Try running the game from the command line, if you are not already.

In your first post, you mentioned installing a number of libraries like SDL and such. This should not be necessary to run the distributed version. Maybe there is an incompatibility there? You might try deleting/renaming them to make sure they are not guilty.

[The Wicked Flea]

Try running the game from the command line, if you are not already.

Done; whenever I mentioned "including the console" this means I did try the command line. Execution runs and the prompt returns, signaling that WZ doesn't allocate the command line, and then WZ crashes.

In your first post, you mentioned installing a number of libraries like SDL and such. This should not be necessary to run the distributed version. Maybe there is an incompatibility there? You might try deleting/renaming them to make sure they are not guilty.

Removed them from System32... and no change. No log and no settings. This is originally why I obtained these dependencies, for self-compilation I know, to see if they would change anything. Neither presence nor absence makes an ounce of difference.

I've tried 2.1.0, 2.1.1 (and debug), and the latest nightly debug, all with debug parameters.

This is the only problem with such old conversions; they tend to be highly buggy for a time. I wish you guys luck though, from what I was able to play it was great fun.

[stiv]

OK, let's try a different tack: graphics problems.

1) got the latest driver for your card? (yeah, I know you mentioned the version - I'm not a windos person and too lazy to check)
2) display settings:
- try turning down hardware acceleration
- reducing display size
- reducing color depth
- any weirness like running dual monitors or running wz at some strange resolution?
3) IIRC, the SubmitError dialog has a link to some more info. anything interesting there?

[The Wicked Flea]

1) I have a GeForce 9800GT without the latest drivers, they're the last stable driver version that I have found (I had previous trouble) though they are somewhat slower than the newest release. I downgraded purposefully, thinking initially that they were the cause of Warzone's trouble.

2) My Desktop resolution is 1280x1024, refresh rate is 75hz, color depth is at 32; dual monitors with the exact same specifications and settings. The last time I had this configuration, right before I had to reformat my system for maintenance, Warzone did run just fine and I turned my other monitor off due to super-saturation that occurred. This is normal in my experience: that the game allocates a handle and it is fit to a screen instead of both screens.

I've tried game-specific settings to turn on various compatibility extensions, turn down the high things that can make some games crash, and even the way the dual monitors are handled by the card. (Performance versus compatibility, etc.) Returning to a single display does nothing.

3) It was actually just hex dumps of the various files that were loaded, no locations of exceptions, etc. Error offset is purportedly 0x0025b0d1, wherever in the app that is. As I said, the rest is just hex dumps of given locations within all libraries and executables allocated by Warzone.


Is there anything the game does prior to allocating the log handle? Is it the absolute first thing done, or is there something else? I'm not even getting a 0-byte file on my harddrive from this, and every time I run the game I tell it to spit out a debug file.

[stiv]

Very thorough! I'm impressed.

The only other thing I can suggest is running wz via the debugger. Maybe a problem initializing the C runtime?

Other than that, I got nothing.