In the box to the left of DeviceID, enter "592" without the quotes. In the box to the left of VendorID, enter "4318" without the quotes. Text boxes with "VendorID" and "DeviceID" next to them. exe file, NOT the "Launch Conflict - Desert Storm" program that's also in theģ) On the left hand side of the application's window, below the two buttons and the logo, you should see two blank Unzip the file it comes in (Dont run it from inside theĢ) On the first screen you should see two large buttons on the left hand side with orange numbers next to them.Ĭlick the "SELECT" button and choose the "DesertStorm.exe" from your installation folder. I usedġ) Download the program, it does not need to be installed. Program: 3D-Analyze 2.34 Download: No links, search 3D Analyze 2.34 and look for a trusted download site. I don't know if this will work for everyone and some feedback would be appreciated. UPDATE: I have found a way to eliminate the bug on my system using a free third party program. My Hardware: Nvidia GTX 980M, Intel Core i7-4810MQ clocked at 3.5Ghz, Windows 10 64bit If we do find a fix that is GPU dependent the next step would be to see if we can translate it over to the other brands or models. I implore you to still try the Nvidia settings yourselves to see if I missed anything because my testing has been far from clinical. I tried the aforementioned in compatibility mode for both Windows 7 and XP (SP 2). I tried both Vsync in the Nvidia control panel, and both forcing Vsync and limiting the framerate to both 60 and 30 fps in the Nvidia Profile Inspector. This fix does not appear to work on Windows 10 64bit. It appears that this bug might be tied to the game's fps. The existing fix for earlier versions of windows is to force Vsync in the Nvidia Control Panel or whatever the AMD and Intel equivalents are. The issue is that whenever a character (Player controlled or not so it seems) moves from a higher elevation to a lower one if in the process the character leaves the ground, he will float in the air until he freezes in place.
I was considering a refund but if we can squash this bug it might save this game for all those trying to play on Win10.
I know that I am not the only person having this issue so if a fix exists this would probably be the best place to find it. This specific issue is quite game breaking and so far the info I have found (posted below) does not pertain to users of Windows 10.
0 kommentar(er)
