DX persistent states?

It shouldn't. It's probably a driver bug.

Quote:

Original post by Namethatnobodyelsetook It shouldn't. It's probably a driver bug.

I concur - have you tried running your applications using the reference rasterizer? If you suspect the hardware/driver of being wrong you can usually verify it if the RefRast works as expected...

hth
Jack

Render states should be reset to default for each D3D device. If you're using a PURE device, do it yourself - drivers sometimes do the wrong thing...


The other (and possibly more likely) alternative explanation is one or both of the applications is using a surface, texture or other resource without having cleared it or set its content to some known state.

Video memory doesn't get cleared when you create a resource, so you get whatever was there previously (random crap, the last frame of the previously running app, etc)


For example:

- app A renders a 3D scene and uses Z buffering, it clears and writes to the Z buffer and colour buffer every frame. When app A is terminated, the memory used by the Z buffer still contains the final frame Z buffer.

- app B renders a 3D scene and uses Z buffering, it clears and writes to the colour buffer every frame but the programmer forgot to clear the Z buffer so the Z seen in app B also contains stuff from app A.

- if app B has different allocation sizes or orders than app A, then what's in app B's Z buffer could be anything - app A's frame buffer, one of app A's textures, one of app A's index buffers, or even just random uninitialised memory....


Using the debug runtime will help you eliminate some of these possibilities.