I cant really describe it other than that. 3dgs and engine loading works fine after I boot up my computer fresh. After awhile working on my level in WED, however, I build it, then try loading it. It only gets as far as loading my script and then it crashes. I have to CTRL ALT delete to bring up task manager and then end task for A6/3dGamestudio. Also to note SED also crashes and refuses to load thereafter. I have to reboot my comp everytime this happens to get SED and the 3dgs engine working so I can see my work in realtime. Dont get me wrong WED does not crash, just the engine.

I really dont want to keep rebooting every time I work on my game, does this problem classify as a bug?

Older versions of SED have some issues with crashing, but you can always restart the program without rebooting your PC. Using Taskmanager try closing all other applications and see if that makes a difference in stability. Next step up would be reinstalling Windows and GameStudio.

Thanks for the advice!

Well actually I have A6 Commercial v.6.22, I think that also updated SED too. I've never used A6 before the update, so I dont know any difference between the older and newer versions. However the problem still remains.

I have this problem from time to time. It seems to be caused by a process that is running in the background. If I access the Windows Task Manager when the engine is not running and then end a few processes then the engine will suddenly run. I have found, for example, that Windows Task Manager (under the Processes tab) that IExplorer.exe is running when, in fact, I do not have an intance of Internet Explorer running at all (i.e. no browser window is open). By ending this process A6 and SED will run perfectly. I am not sure why there is an IExplorer.exe process though. It could be a bug in IE or it could be some sort of virus or something. You might want to check for something like this on your system, though.

I don't know if this plays a role in the whole topic, but I'm experiencing the exact same problems with Max Payne 2. Bringing the taskmanager to the screen and then ending the manager solves the problem for some time. I thougt this was a game specific problem, but as the same happens with 3dgs this is maybe a directx or windows related problem?

Win2k
Amd Athlon XP