T3D 1.1BETA 1, 2 and 3 BLUE SCREEN OF DOOM! Possibly reflections - RESOLVED

#61 Sean,you're absolutely right - this is a temporal solution.

Actually I have several PCs, all with Ati cards and was never able to reproduce this bug.I'll apply Henry's fix in order to render safe.

#62 Everyone I have seen with this issue seems to have an nVidia card as well. All of my machines have nVidia cards which could be why I seem to have it on all of them.

#63 Henry's fix did it! I had big problems, when I start using AFX and played with the spells. The screen went totaly mad. I tried so many things downgrading video driver to several versions, downgrading DX-SDK, underclocking graphic card, testing every possible configuration with nvidia control center. I was close to plug in my old 9600 GT but my 260GTX works well with everything else expect Torque3d.

And now it works :)


Some impressions how it did look for me before, after casting some spells (== a lot of particles)

#64 Has anyone made any progress on an proper fix?

#65 A "proper" fix most likely won't come out unless someone can identify the major issue. Since turning off the reflections resolves a great deal of the issues this is definitely the first place to look.

#66 yeah, this is becoming a serious issue for me too, the speckles eat up both my screens within 30 seconds, that same 4 split window freeze, and the BSOD's.

GTX 295, Windows7.

it seems like there is a trend.

GTX ***, with Window7/vista

could it be an incompatability between these 2(GTX + W7)??

#67 I have had this same issue on Windows XP and the GTS, so I don't believe its directly related to the OS. I know that since I applied Henry's fix from above I have yet to have a single issue with it crashing.

#68 I see on the net, that this is a known issue,
trying the recomended fix now....
will report back

#69 It seems the engine is crashing at this line :

while( ( hRes = mQuery->GetData( &dwOccluded, sizeof(DWORD), D3DGETDATA_FLUSH ) ) == S_FALSE)

For those who can reproduce the bug,try this way:

while( ( hRes = mQuery->GetData( &dwOccluded, sizeof(DWORD), D3DGETDATA_FLUSH ) ) == (S_FALSE | S_OK) )

According to MSDN, GetData "should be not called" on a query that is in the building state,this way it will never return something different from S_FALSE.

#70 FYI, the file that Ivan is refering to is Torque3D-Beta3EnginesourcegfxD3D9gfxD3D9OcclusionQuery.cpp

I made the above changes from Ivan and reverted the changes from Henry. I will be testing on my machines this evening and will report with results.

#71 I'll have a test then ...

Thanks Ivan (and Sean).

#72 It is not crashing anymore, but it is still "pausing" at almost every rocket launch.

#73 Yeah, I'm still getting the second long GPU lock-up in beta 3.

#74 Way back when I was doing the particle fx for the various weapons I never experienced this... crashes, hangs, locks, or graphical corruption... and still don't -- even on a crappy laptop 7150 nVidia card.

#75 Ok, doing a little debugging tonight I came across a couple of things. The console spammed the below error once. I also noticed that the screen flashed "yellow" during the time that the driver locked up.

GFXPCD3D9Device::beginScene - Device needs to be reset, waiting on device...


During this whole time I only had one item generate an error.
it points to this I believe

ParticleRenderInst *ri = renderManager->allocInst<ParticleRenderInst>();

- ri 0xc273a630 {vertBuff=??? primBuff=??? count=??? ...} ParticleRenderInst *
- RenderInst {type=??? translucentSort=??? sortDistSq=??? ...} RenderInst
type CXX0030: Error: expression cannot be evaluated
translucentSort CXX0030: Error: expression cannot be evaluated
sortDistSq CXX0030: Error: expression cannot be evaluated
defaultKey CXX0030: Error: expression cannot be evaluated
defaultKey2 CXX0030: Error: expression cannot be evaluated
vertBuff CXX0017: Error: symbol "" not found
primBuff CXX0017: Error: symbol "" not found
count CXX0030: Error: expression cannot be evaluated
modelViewProj CXX0030: Error: expression cannot be evaluated
blendStyle CXX0030: Error: expression cannot be evaluated
targetIndex CXX0030: Error: expression cannot be evaluated
systemState CXX0030: Error: expression cannot be evaluated
softnessDistance CXX0030: Error: expression cannot be evaluated
bbModelViewProj CXX0030: Error: expression cannot be evaluated
diffuseTex CXX0017: Error: symbol "" not found

#76 @Michael this doesn't seem to affect all weapons, my pistols/rifles have no issue. The rocket launcher and the AFX machine gun do cause the problem.

#77 FYI.

We've sent a test case to NVidia for this bug a few weeks ago. They have been able to reproduce it and we've identified that it happens with the latest NVidia drivers on certain Geforce models.

They are working on identifying the reason for the driver crash and a fix. Hopefully they can give me an idea of a work around which avoids the issue as it will take time for a new driver to get on to everyone's system.

#78 Cool. :)

#79 Cool good news about nVidia admitting a problem ;)

@Sean: that's why i commented, because i'm the one who setup the particle fx for the stock/default rocketlauncher in T3D (as well as all weapons that were originally in the FPS example) and never experienced this issue despite, admittedly, getting carried away with particle counts :D

Of course my newer comp has an ATI card which has other problems, just not this one.

#80 @Tom awesome man, thanks for your hardwork on this!