Windows Performance Issues
by Valador, Inc. · in Torque Game Engine · 09/24/2008 (8:13 am) · 0 replies
I'm having this really strange problem with starting up Torque and then context-switching between Torque and other windows.
When I first run Torque (the example demos) it takes 45+ seconds before the game comes up. This happens whether or not the .cs files have previously been compiled. Everything runs fine after that, except for when I switch context to another application and then switch back to Torque I get a 45+ second hang-up before Torque begins responding.
I've updated my graphics card drivers (GeForce 7800), tried both OpenGL and D3D, tried both windowed mode and full-screen, tried different resolutions. I also tried out TGEA 1.7 and the same thing happens. I even tried downloading the Marble Blast Ultra game demo and it does the same thing.
Other applications and games work fine.
I've tried Torque on other computers and it has worked fine everywhere else. Obviously it's something with my computer, but has anyone else ever seen this problem and found a way to fix it? Not only is it annoying, but it makes debugging the engine code damn near impossible.
When I first run Torque (the example demos) it takes 45+ seconds before the game comes up. This happens whether or not the .cs files have previously been compiled. Everything runs fine after that, except for when I switch context to another application and then switch back to Torque I get a 45+ second hang-up before Torque begins responding.
I've updated my graphics card drivers (GeForce 7800), tried both OpenGL and D3D, tried both windowed mode and full-screen, tried different resolutions. I also tried out TGEA 1.7 and the same thing happens. I even tried downloading the Marble Blast Ultra game demo and it does the same thing.
Other applications and games work fine.
I've tried Torque on other computers and it has worked fine everywhere else. Obviously it's something with my computer, but has anyone else ever seen this problem and found a way to fix it? Not only is it annoying, but it makes debugging the engine code damn near impossible.
