C:\Program Files (x86)\EVGA\PrecisionX 16\ProfilesĮDIT #2 - Please be aware of the following if you use the above : Then close and save the file.ħ - Copy back the file you've just edited to the location you copied it from, ie. exe files after each reboot do the following :ġ - Browse to : C:\Program Files (x86)\EVGA\PrecisionX 16\Profiles (or wherever you installed Precision X 16 to, just get to the profiles folder)Ģ - Find the file called "precisionxserver.cfg"ģ - Copy this file to your desktop or another locationĤ - Rename the original "precisionxserver.cfg" in C:\Program Files (x86)\EVGA\PrecisionX 16\Profiles to something like "precisionxservercfg.old"ĥ - Goto the desktop, or wherever you placed the copy of the file and open it in either Notepad or WorpadĦ - Remove bf3.exe, bf4.exe and bf4_x86.exe" from in there. Even the toggle is working fine for me now, (I've assigned INSERT as my toggle key).ĮDIT - To stop having to remove these three.
Only downside is that even if you remove them and click OK, after a restart it reverts back to what I presume is the default and those three. So as a test I removed them from there, and OSD started working instantly. Surely you'd want to INCLUDE those in monitoring? Found this really odd as you will notice that BF3.exe, BF4.exe and BF4_x86.exe are listed in there. exe files that were EXCLUDED from framerate monitoring. This will open the following box :įound a thread on the EVGA forums, ( ) and some guy on there said that this was a list of. If you hover over it, you'll see it's called " EVGA Precision X 16 Server v5.2.0", as below : Once you've started Precision X 16, you'll also notice in your task bar you have an additional EVGA icon. If you don’t lift your foot, the engine revs into its redline.Ok to solve the BF4 OSD issue seems you have to do the following. That could cause a GPU to suddenly go from an in-game frame rate of 100 fps to roaring along at 800 fps. It’s akin to driving a car at full throttle going up hill and accidentally putting the car into neutral. The New World beta in question did not implement a frame rate limiter in the menu system, which many released games include.
EVGA said it could not replicate the issue, but it was working to add a method to screen for the particular power profile the beta version created. No customers have reported issues to EVGA since Amazon added frame rate limiters to the game.īoth EVGA and Nvidia worked with Amazon Games to obtain the version of the game that bricked the cards to conduct further testing. AmazonĬustomers told EVGA that the cards died while in the game’s menu system or while loading the game. The company declined to say how many GeForce RTX 3090 cards it has sold, but did characterize this small batch as significantly less than 1 percent of the total.
0 kommentar(er)
