Well, your User32.decls seems to work just dandy:- It tells me if the screensaver is running and also seems pin the error to renderworld after a passworded screensaver has been invoked.
Using Yan's method I can determine if the screensaver is running and do a clearworld (and also introduce a .1 second delay so as to allow other tasks more cpu cycles - before I did that the screensaver ran like it was powered by steam). When the screensaver is no longer running I delay for 2 seconds (1 second seems to work - much less that that and the dreaded "Unable to create 3D scene" message appears) and re-initialise the screen.
I'm purely guessing that the windows password routine somehow makes BB's hooks to the front/backbuffers invalid. However, other games/apps don't seem to suffer?!
Thanks, once again, for the routemap!
Using Yan's method I can determine if the screensaver is running and do a clearworld (and also introduce a .1 second delay so as to allow other tasks more cpu cycles - before I did that the screensaver ran like it was powered by steam). When the screensaver is no longer running I delay for 2 seconds (1 second seems to work - much less that that and the dreaded "Unable to create 3D scene" message appears) and re-initialise the screen.
I'm purely guessing that the windows password routine somehow makes BB's hooks to the front/backbuffers invalid. However, other games/apps don't seem to suffer?!
Thanks, once again, for the routemap!