Game Development Community

Beta4 bug: hard GPU lockup

by Manoel Neto · in Torque 3D Professional · 07/18/2009 (6:19 am) · 3 replies

Okay, I've been seeing this one since b3, actually, but since it hapenned again with b4 AND after I switched from XP SP3 to Win 7 I think its time to report.

The GPU is a ATI HD 4850 and I'm getting *hard* GPU crashes with T3D only: my screen goes grey and I have to reset the PC. I can't figure out yet what exactly are the steps to reproduce the bug, but I think it has to do with switching back and fort between BL and AL and switching between missions, because just leaving Warrior Camp for hours doesn't crash.

I don't think its my GPU, because I play a lot of other games and I never saw a crash like that. I think something isn't being cleared or there's a not-so-kosher leftover vertex buffer somewhere that causes the GPU to go haywire. The crash happened with different driver versions, and it happened in Windows 7 as well as XP SP3.

Years ago when I working with TGEA I remember I made something stupid that made it cause hard GPU crashes (with nVidia cards) and I think it had to do with a few bogus entries in my index buffers.
NextNext Thread
PrevPrevious Thread
More from Torque 3D Professional


Associate James Ford
Sickhead Games
#1
07/18/2009 (6:36 am)
From tests a few betas ago I suspect that video memory (GFXResource) is getting leaking when light managers are changed repeatedly but I could not track it down. Is there any slowdown/etc that occurs before it locks up?

Of course this could be something else entirely... but we have had performance problems and crashes in the past resulting from frequent LM switches.

Associate Manoel Neto
Default Studio Name
#2
07/19/2009 (6:26 am)
No slowdowns, it always crashes without warning. I can get consistent crashes with the PureLIGHT demo, however, by spending a few minutes using the mission editor. I wasn't doing anything too strange, just added a point light, added Gideon as a TSStatic and was moving them around.

Torque 3D Owner William Gooding
#3
07/19/2009 (8:31 am)
I think that is somewhat related to the latest problems I am experiencing as well (www.garagegames.com/community/forums/viewthread/97331) since my debugger stops at gfxD3D9Device.h. If that is so, I think this reinforces the possibility of the existence of an issue with video memory management....