Thanks.
I see, so OpenGL tries to hold all the graphics in VRAM and runs out of room thus bombs. But it doesn't bomb in a nice way at all that can be trapped. Maybe I'll need to write a little file on exit called "goodexit" and then delete it when it loads (before setting the screen up). Then if, when loading, the goodexit file is missing I can revert to a standard .ini file with DirectX as the default mode. (The laptop is XP SP2 btw, I shoulda said)
OK, so GraphicsModeExists may be redundanct but Graphics() does return a TGraphics object and I'm checking that for null and taking action if it is. Would you suggest a different method? Probably it's bombing later anyway by the time the graphics are fully loaded into VRAM and it overflows. Now there isn't any decent easy code to check for remaining VRAM in BMax is there?...
I see, so OpenGL tries to hold all the graphics in VRAM and runs out of room thus bombs. But it doesn't bomb in a nice way at all that can be trapped. Maybe I'll need to write a little file on exit called "goodexit" and then delete it when it loads (before setting the screen up). Then if, when loading, the goodexit file is missing I can revert to a standard .ini file with DirectX as the default mode. (The laptop is XP SP2 btw, I shoulda said)
OK, so GraphicsModeExists may be redundanct but Graphics() does return a TGraphics object and I'm checking that for null and taking action if it is. Would you suggest a different method? Probably it's bombing later anyway by the time the graphics are fully loaded into VRAM and it overflows. Now there isn't any decent easy code to check for remaining VRAM in BMax is there?...