Ridiculous Amounts of Crashing

[Serman]

@ Warzone 2100 v. 2.2.1

The amount of times the game crashes is just annoying and exhausting. Whenever I am on a skirmish or multiplayer game, on Skirmish the game crashes unpredictably, at least every 2 - 20 minutes. I have to literally save every minute in order to prevent from losing too much progress. Same thing with multiplayer, except you can't really save there; so the game is usually ruined. This usually happens the most on T3, and happens more often when there are more players in-game at a time (this theory was not tested)

And the worst part is, it does not provide a .mdmp, so I can't report it to you guys like any other bug. :[
The game just closes and exits to desktop within a split second, without so much as a dialog box explaining the fatal error.

Halp!

[Tiberian]

try the stderr file in your warzone directory, that, and warzone2100.rpt.

[Serman]

Ah, here we go;

Code: Select all

Error occured on Tuesday, August 4, 2009 at 17:54:40.

Program: C:\Program Files\Warzone 2100\warzone2100.exe(warzone2100)
Command line: "C:\Program Files\Warzone 2100\warzone2100.exe" 
Version: Version 2.2.1
Distributor: wz2100.net
Compiled on: Jun 21 2009 11:34:24
Compiled by: GCC 4.2.1-sjlj (mingw32-2)
Executed on: Tue Aug 04 17:49:43 2009

Pointers: 32bit

Compiled against PhysicsFS version: 1.0.1
Running with PhysicsFS version: 1.0.1

Misc Data:
[05:49:44]OpenGL Vendor : ATI Technologies Inc.
[05:49:44]OpenGL Renderer : Radeon X1300/X1550 Series
[05:49:44]OpenGL Version : 2.1.8543 Release
[05:49:44]OpenAL Vendor: Creative Labs Inc.
[05:49:44]OpenAL Version: 1.1
[05:49:44]OpenAL Renderer: Software
[05:49:44]Using language: System locale
[05:50:01]Current Level/map is Sk-SandCastles-T3


C:\Program Files\Warzone 2100\warzone2100.exe caused an Access Violation at location 004933d3 in module C:\Program Files\Warzone 2100\warzone2100.exe Reading from location 09632ff8.


Registers:
eax=09632ff8 ebx=06a93660 ecx=040801a1 edx=09632ff8 esi=00000380 edi=00000101
eip=004933d3 esp=0022f960 ebp=0022f9a8 iopl=0         nv up ei ng nz ac po cy
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00210297

Call stack:
004933D3  C:\Program Files\Warzone 2100\warzone2100.exe:004933D3  world_coord  /home/admins/wz2.2/2.2.1/src/map.h:225
0049446A  C:\Program Files\Warzone 2100\warzone2100.exe:0049446A  moveUpdateDroid  /home/admins/wz2.2/2.2.1/src/move.c:3078
00438FC0  C:\Program Files\Warzone 2100\warzone2100.exe:00438FC0  droidUpdate  /home/admins/wz2.2/2.2.1/src/droid.c:847
0047F866  C:\Program Files\Warzone 2100\warzone2100.exe:0047F866  gameLoop  /home/admins/wz2.2/2.2.1/src/loop.c:299
00481C8C  C:\Program Files\Warzone 2100\warzone2100.exe:00481C8C  runGameLoop  /home/admins/wz2.2/2.2.1/src/main.c:649
005805AA  C:\Program Files\Warzone 2100\warzone2100.exe:005805AA
00580792  C:\Program Files\Warzone 2100\warzone2100.exe:00580792
00580249  C:\Program Files\Warzone 2100\warzone2100.exe:00580249
004010A7  C:\Program Files\Warzone 2100\warzone2100.exe:004010A7  __mingw_CRTStartup  /home/ron/devel/debian/mingw32-runtime/mingw32-runtime-3.13/build_dir/src/mingw-runtime-3.13-20070825-1/crt1.c:237
00401123  C:\Program Files\Warzone 2100\warzone2100.exe:00401123-------------------

This mean anything bad in particular? I'm guessing it's something related to OpenGL.

[Zarel]

lol, the world_coord crash. We've fixed that one.

We've fixed nearly all the crashes in 2.2.1 for 2.2.2, it's just that we haven't released it yet.

[Serman]

lol, the world_coord crash. We've fixed that one.

We've fixed nearly all the crashes in 2.2.1 for 2.2.2, it's just that we haven't released it yet.

Ah, I'm glad to hear that.

Will be looking forward to playing my huge skirmishes once it's released.

[yamar]

any idea when 2.2.2 will be released? the crashes are too much!