|
|
|
|
|||||||
| Fixed Geek Squad Rescued These Threads |
|
Login or Register now to see less ads. |
|
|
Thread Tools | Display Modes |
|
|
|
#1
|
||||
|
||||
|
I believe what is happening, is that changing the file to say pandadx9 (or 10) forces the software to change its default. When it loads up afterwards, it must be using the pandadx# option as the default.
I cant believe this, I have lived with the game crashing upon exit on my vista laptop forever. I just changed the setting from pandadx9 to pandadx10, and no more CRASH!!!! |
|
#2
|
||||
|
||||
|
Thanks for your answers OFxZeppers !
__________________
I'm Fighting for the French because I'm French !![]() |
|
#3
|
||||
|
||||
|
Your welcome.
After a bit more playing with my system and that setting, im thinking what it does is actually just remind the game to try more current versions of DirectX support. Studied some old logs and found it was originally diverting to DX8 when it couldnt get OpenGL to work on its own. Now of course it uses DX10 (im assuming, these log files arent THAT clear.. hehe). I know I had used the pandadx9 before, with measured success, and now that im using pandadx10 it seems to have improved even more. |
| Thread Tools | |
| Display Modes | |
|
|