Error occured on Friday, August 8, 2008 at 17:39:35.
Program: C:\Warzone 2100\warzone2100.exe(warzone2100)
Command line: "C:\Warzone 2100\warzone2100.exe"
Version: Version 2.1_beta4 - DEBUG
Distributor: Warzone 2100 Resurrection Project
Compiled on: Jul 21 2008 20:49:57
Compiled by: GCC 3.4.5 (mingw special)
Executed on: Fri Aug 08 17:33:29 2008
Pointers: 32bit
Compiled against PhysicsFS version: 1.0.1
Running with PhysicsFS version: 1.0.1
C:\Warzone 2100\warzone2100.exe caused an Access Violation at location 0329e0d7 in module C:\WINDOWS\system32\atioglx2.dll Reading from location ffffffff.
Log message: warning : [seq_Play] Sequence display is currently disabled (sequences/cam1/c001.rpl)
Log message: warning : [seq_StartFullScreenVideo] seq_StartFullScreenVideo: unable to initialise sequence sequences/cam1/c001.rpl
Log message: warning : [openLoadFile] optional file sequenceaudio/cam1/cam1.txt could not be opened: File not found
Log message: warning : [seq_Play] Sequence display is currently disabled (sequences/cam1/cam1.rpl)
Log message: warning : [seq_StartFullScreenVideo] seq_StartFullScreenVideo: unable to initialise sequence sequences/cam1/cam1.rpl
Log message: warning : [openLoadFile] optional file sequenceaudio/BrfCom.txt could not be opened: File not found
Log message: warning : [openLoadFile] optional file sequenceaudio/cam1/cam1ascv.txt could not be opened: File not found
Log message: warning : [seq_Play] Sequence display is currently disabled (sequences/BrfCom.rpl)
Log message: warning : [seq_StartFullScreenVideo] seq_StartFullScreenVideo: unable to initialise sequence sequences/BrfCom.rpl
Log message: warning : [seq_Play] Sequence display is currently disabled (sequences/cam1/cam1ascv.rpl)
Log message: warning : [seq_StartFullScreenVideo] seq_StartFullScreenVideo: unable to initialise sequence sequences/cam1/cam1ascv.rpl
Registers:
eax=00000000 ebx=003defed ecx=06386d40 edx=00000000 esi=06432f40 edi=05f7f008
eip=0329e0d7 esp=0022fb30 ebp=06432f40 iopl=0 nv up ei pl nz na pe nc
cs=001b ss=0023 ds=0023 es=0023 fs=003b gs=0000 efl=00210202
Call stack:
0329E0D7 C:\WINDOWS\system32\atioglx2.dll:0329E0D7 atiPS
0329DCDF C:\WINDOWS\system32\atioglx2.dll:0329DCDF atiPS
0329D5EE C:\WINDOWS\system32\atioglx2.dll:0329D5EE atiPS
032979E7 C:\WINDOWS\system32\atioglx2.dll:032979E7 atiPS
0328CAFD C:\WINDOWS\system32\atioglx2.dll:0328CAFD atiPS
036F45AF C:\WINDOWS\system32\atioglx2.dll:036F45AF atiPS
0327FDEB C:\WINDOWS\system32\atioglx2.dll:0327FDEB atiPS
036F4937 C:\WINDOWS\system32\atioglx2.dll:036F4937 atiPS
036F4832 C:\WINDOWS\system32\atioglx2.dll:036F4832 atiPS
Campaign Crash
Campaign Crash
Xfire-->chris37killer
Re: Campaign Crash
That isn't a warzone problem, that is a ATI gfx driver problem.Alpha93 wrote:Error occured on Friday, August 8, 2008 at 17:39:35.
C:\Warzone 2100\warzone2100.exe caused an Access Violation at location 0329e0d7 in module C:\WINDOWS\system32\atioglx2.dll Reading from location ffffffff.
Report those bugs to ATI, maybe they will fix the drivers.