View Issue Details

IDProjectCategoryView StatusLast Update
0001778Spring engineGfx driver issuespublic2010-07-12 17:19
Reportertvo Assigned To 
PrioritynormalSeveritycrashReproducibilityhave not tried
Status closedResolutionnot fixable 
Product Version0.80.5 
Summary0001778: when nanoframe is rendered, ATI driver crash
Description[13:21:27] <[USSR]Nukes> Hey, I get a crash with these two coding errors anytime I give my commander away or construct a building with it
[13:21:31] <[USSR]Nukes> [ 693] Exception: Access violation (0xc0000005)
[13:21:31] <[USSR]Nukes> [ 693] Exception Address: 0x777859c3
[13:21:43] <[USSR]Nukes> is their a way to fix this?

...snip...

[13:44:59] <[USSR]Nukes> Then I'm not sure what it is then
[13:45:19] <[USSR]Nukes> becuase I can spectate a game no problem
[13:45:29] <[USSR]Nukes> just building something gives me troubles
[13:45:50] <[RoX]Tobi> when exactly in building sequence does it crash?
[13:45:59] <[RoX]Tobi> does it crash right when you click button in menu?
[13:46:11] <[RoX]Tobi> or when you place building on map?
[13:46:20] <[RoX]Tobi> or when commander creates nanoframe?
[13:54:20] <[USSR]Nukes> When the commander creates the nano fram
[13:54:23] <[USSR]Nukes> Frame*
[13:54:37] <[USSR]Nukes> but
[13:54:41] <[USSR]Nukes> I just tested this
[13:54:55] <[USSR]Nukes> If I don't ever render a nano frame, I.E dont look at them
[13:55:02] <[USSR]Nukes> then I don't crash

May be related with all the other nanoframe related ATI bugs?

Quite possibly we can't do anything about this though.
Additional Informationhttp://pastebin.com/f2c445f25
TagsNo tags attached.
Checked infolog.txt for Errors

Activities

Kloot

2010-07-12 17:19

developer   ~0005078

Assuming ATI hasn't fixed this yet in a more recent driver version, you can try setting atiHacks=1 in .springrc / springsettings.cfg (disables the wireframe clipping planes). Other than that, we can't do much about it.

Issue History

Date Modified Username Field Change
2009-12-30 14:08 tvo New Issue
2010-07-12 17:19 Kloot Note Added: 0005078
2010-07-12 17:19 Kloot Status new => closed
2010-07-12 17:19 Kloot Resolution open => not fixable