Warzone 2100 Forums

V. 2.2 Beta 2
When I complete the objective in a camping, WZ crash with this message:
"Assertion failed" (details are in the atachment - savegame and error message)

Can it be fixed?

Have you tried pressing Ignore?

Also, send the crashdump (warzone2100.rpt in Program Files/Warzone 2100/)

If I press IGNORE it show me this message again.

My OS is Windows XP, hardware: Celeron 1.3, GeForce 4, 512 Mb RAM.

(Warzone2100.rpt in the attachment)

This seems to be common...

What is an Assertion failure anyway? I'm under the impression that it is when the game fails to read code.

Raem_Lylar wrote:What is an Assertion failure anyway? I'm under the impression that it is when the game fails to read code.

No, it is a program statement that declares a certain precondition must be true for the program to proceed. For example, the value of a certain variable must be between 1 and 5.

Assertions are useful for developing and debugging a program. They have the useful property that they can be turned on and off at compile time. Usually, they are turned off once a program is ready to be released.

stiv wrote:No, it is a program statement that declares a certain precondition must be true for the program to proceed. For example, the value of a certain variable must be between 1 and 5.

Assertions are useful for developing and debugging a program. They have the useful property that they can be turned on and off at compile time. Usually, they are turned off once a program is ready to be released.

To be exact, it declares ("asserts") that something should be true. Half the time, nothing bad really happens if it isn't true, but sometimes it could be indicative of deeper problems. That's why you should usually hit "ignore".

Warzone ALWAYS terminates when ignore is hit. No matter how severe the assert is.

So it is game breaking because i can not continue playing.

I get this too...

I press retry, it crashes...
I press ignore, same thing pops up... (or it aborts it automaticly...)
i press abort... it keeps popping up....

exactly - same thing here.

lav_coyote25 wrote:exactly - same thing here.

Not surprising. When the assert fails, it means something has gone wrong. You can quibble over the semantics of must/should/ought to/hopefully/maybe, but it is a sign that something bad has happened.

It may be a coding error, it may be something in the program's environment like bad data, but it is not good AND it is important enough that the programmer used an assert statement rather than trying to dance around the problem.

Think of it as a bug. Report them if you can.

did done do. still waiting for an answer. xD

lav_coyote25 wrote:did done do. still waiting for an answer. xD

The answer is 42.


Anyway, besides what has been said, it depends on what the Assert was. Some asserts, you can ignore, and they may go away. Others, when you hit ignore, the issue was too severe, and it crashes warzone, and if you keep hitting ignore, and it seems to be the same assert over and over, well, that means, you are in a loop, and who knows how many times you will see the same assert...

And just a FYI, it is better to post/attach stderr.txt, instead of screenshots of the assert, and of course, if you crash, the stderr.txt & the crash dump file.

so posting the damn things on the trac lister isnt going to work then... ok.

lav_coyote25 wrote:so posting the damn things on the trac lister isnt going to work then... ok.

Oh, that is the *best* place for those. I just meant, instead of people posting pics in the forums of the assert.

Votan wrote:V. 2.2 Beta 2
When I complete the objective in a camping, WZ crash with this message:
"Assertion failed" (details are in the atachment - savegame and error message)

Can it be fixed?

Sorry, had it fixed, but I forgot to commit it.

To make it up to you, I will upload a fixed .exe. You can either backup the old one (recommended), and use this one, or overwrite the old one.

This is windows *only*.

BTW, it is easier if you make bug reports via trac, like you just did. That way, I can remind myself easier...

Oh, and if you use this version, and you get errors/bugs that you don't get with the original release, then please mention the build # that you see of the right side of the screen in the main menu.

Thanks!

As always, a savegame with the issue is the *best* way for us to track down issues! Thanks again Votan.