tarball
07-27-2007, 03:20 PM
I am a pre-order customer - The game is absolutely unplayable for me (very disappointing).
Requested Data:
1. I am running the Battlefront version (downloaded on 07/27/2007)
2. I have an Intel Core 2 X6800 Processor (2 x 2.93Ghz)
3. I have an ATI X1900XTX (Catalyst 7.7 drivers) with 512 of Video RAM
4. I have 2.0 Ghz of system memory.
5. I am running Vista Ultimate 32-bit
6. The EXACT problem is: When I am in the orders and planning phase with a unit selected, if I hit any movement orders button, the game crashes/freezes. The problem details are
Problem signature:
Problem Event Name: APPCRASH
Application Name: CM Shock Force.exe
Application Version: 0.0.0.0
Application Timestamp: 46a948d4
Fault Module Name: atioglxx.dll
Fault Module Version: 6.14.10.6645
Fault Module Timestamp: 4681bf53
Exception Code: c0000005
Exception Offset: 00460fda
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033
Additional Information 1: ede9
Additional Information 2: 54b55ff41d44f6ed5dd5e8af9ac022bb
Additional Information 3: 29f0
Additional Information 4: 306c6266638b89681e89ffcb06237678
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
This is an OpenGL/ATI issue, but I wonder why DirectX wasn't used?
Requested Data:
1. I am running the Battlefront version (downloaded on 07/27/2007)
2. I have an Intel Core 2 X6800 Processor (2 x 2.93Ghz)
3. I have an ATI X1900XTX (Catalyst 7.7 drivers) with 512 of Video RAM
4. I have 2.0 Ghz of system memory.
5. I am running Vista Ultimate 32-bit
6. The EXACT problem is: When I am in the orders and planning phase with a unit selected, if I hit any movement orders button, the game crashes/freezes. The problem details are
Problem signature:
Problem Event Name: APPCRASH
Application Name: CM Shock Force.exe
Application Version: 0.0.0.0
Application Timestamp: 46a948d4
Fault Module Name: atioglxx.dll
Fault Module Version: 6.14.10.6645
Fault Module Timestamp: 4681bf53
Exception Code: c0000005
Exception Offset: 00460fda
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033
Additional Information 1: ede9
Additional Information 2: 54b55ff41d44f6ed5dd5e8af9ac022bb
Additional Information 3: 29f0
Additional Information 4: 306c6266638b89681e89ffcb06237678
Read our privacy statement:
http://go.microsoft.com/fwlink/?linkid=50163&clcid=0x0409
This is an OpenGL/ATI issue, but I wonder why DirectX wasn't used?