@DGUY
With my test code before RenderWorld are you attempting to restore the surfaces if TestCoop fails? If so the cause of your MAVs might be something else, like you say without the source cant tell. But if the Rendering in Renderworld uses Vertex and Index Buffers they need to be handled as well if the TestCoopertive Fails, RestoreAllSurfaces does not fix them. They need to be destroyed and recreated. Maybe the cause of your problem is tied to the failure to ensure they are in valid state.
In which case if test fails endgraphics reload might fix.
Have you tried minimal case app like my demo which destroys and recreates display and still cause it to crash?
I think your probably right we are going to be stuck until Renderworld is crash safe and possible returns a result as to what we need to do. ie RenderWorld returns false we know we need to recreate our resources.
Reason I am even looking at Dx7 for myself is I need minimal 3d support and to support lower end hardware. Which has me back at Dx7. Blitz3d nice as it is is not powerful enough for what I need in a language, an BMax doesn't support threads so the SDK seems like a happy medium. I would really hate to have to write my own Dx7 engine from scratch as this is part time fun. I already have a full time job.
I didnt have half the trouble writing the Max2d Dx9 driver as I have dealing with Dx7 clunkiness and bad drivers.
I couldnt get my test app to crash under XP but I will move it to my old Win2k laptop with a really crappy video card and try it there.
Doug
With my test code before RenderWorld are you attempting to restore the surfaces if TestCoop fails? If so the cause of your MAVs might be something else, like you say without the source cant tell. But if the Rendering in Renderworld uses Vertex and Index Buffers they need to be handled as well if the TestCoopertive Fails, RestoreAllSurfaces does not fix them. They need to be destroyed and recreated. Maybe the cause of your problem is tied to the failure to ensure they are in valid state.
In which case if test fails endgraphics reload might fix.
Have you tried minimal case app like my demo which destroys and recreates display and still cause it to crash?
I think your probably right we are going to be stuck until Renderworld is crash safe and possible returns a result as to what we need to do. ie RenderWorld returns false we know we need to recreate our resources.
Reason I am even looking at Dx7 for myself is I need minimal 3d support and to support lower end hardware. Which has me back at Dx7. Blitz3d nice as it is is not powerful enough for what I need in a language, an BMax doesn't support threads so the SDK seems like a happy medium. I would really hate to have to write my own Dx7 engine from scratch as this is part time fun. I already have a full time job.
I didnt have half the trouble writing the Max2d Dx9 driver as I have dealing with Dx7 clunkiness and bad drivers.
I couldnt get my test app to crash under XP but I will move it to my old Win2k laptop with a really crappy video card and try it there.
Doug