80 is totally normal operational temperature for GPU under heavy load. CPU is a different story. Reaching those temperatures might be fine under synthetic test load, but if you hit it that high in normal applications it's definitely not a good cooling solution.
Hardware & Technical I don't think gsync is working, why?
- Thread starter disorganise
- Start date
Enabling large page support for the game's executable and tuning the number of worker threads and their stack sizes might help, if the CPU does prove to be a limiting factor.
Also, enabling threaded optimization for the game's profile in the nvidia control panel and maxing out the terrain work slider in the game's graphics options can reduce stutter/hitching.
As for overclocking, if you don't know how to do so manually and aren't able to stress test appropriately, leave it stock. Auto overclocking options included with most board firmware are very hit or miss and will often either be unstable, or throw so much voltage at things as to seriously impact temperatures and longevity.
In the NVidia Control Panel is a setting under Setup G-Sync that allows you to use it in a windowed mode. It doesn't seem to work on Borderless mode for me. I always find the best results to be in Full Screen mode.
V-Sync should always be off in the game settings. If you have V-Sync on the in the NVidia control panel it will work as follows: When a game reaches the maximum FPS for your monitor (144 fps for a 144Hz monitor), a special form of V-sync kicks in and limits the game to your monitor’s refresh rate. It won’t be able to go above 144 frames per second. This prevents screen tearing from occurring. However, it can introduce a bit more input latency.
https://www.howtogeek.com/270672/how-to-enable-optimize-and-tweak-nvidia-g-sync/
V-Sync should always be off in the game settings. If you have V-Sync on the in the NVidia control panel it will work as follows: When a game reaches the maximum FPS for your monitor (144 fps for a 144Hz monitor), a special form of V-sync kicks in and limits the game to your monitor’s refresh rate. It won’t be able to go above 144 frames per second. This prevents screen tearing from occurring. However, it can introduce a bit more input latency.
https://www.howtogeek.com/270672/how-to-enable-optimize-and-tweak-nvidia-g-sync/
Last edited:
Did a little more testing. Definitely a bug with the gsync windowed mode.... As in, doesn't work.
Tested full-screen and watched osd show number moving around. Went windowed and border less and it sticks to 120 (while fps counter drops).
Shut down game.
Select full-screen only in ncp, apply.
Retest.
Shut game. Select full-screen and windowed. Retest.
Also tested on 2nd profile.
And then tested unplugging the 2nd monitor in case windowed is disabled because the window could be straddling the screens. But nope. Gsync only works full screen... At least for ED (not tried anything else)
Tested full-screen and watched osd show number moving around. Went windowed and border less and it sticks to 120 (while fps counter drops).
Shut down game.
Select full-screen only in ncp, apply.
Retest.
Shut game. Select full-screen and windowed. Retest.
Also tested on 2nd profile.
And then tested unplugging the 2nd monitor in case windowed is disabled because the window could be straddling the screens. But nope. Gsync only works full screen... At least for ED (not tried anything else)
how? I already have the lock pages enabled for my account..... Can't recall why now, but it's there.
Open regedit browse to "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options", create a new key called "EliteDangerous64.exe", then in that new key make a new DWORD value called "UseLargePages" and set it to "1" (omit all these quotes when actually making the entries).
Doesn't do much, but it helps reduce the number of kernel cycles I see after all the Spectre and Meltdown mitigation and generally lets the game use slightly less CPU cycles, especially in conjunction with adjustments to AppConfig.xml, namely increasing the "WorkerThreadStackSize" to "2097152" (double the default value, which is, incidentally enough, the size of a large memory page in Windows) and adjusting the "NumWorkerThreads" to something more reasonable, depending on the number of logical cores you have available and any other relevant factors. Since the game will use two or three render threads most of the time, and you only have four logical cores on your i5, I would set this to "2", but no lower, if "2" results in issues try "3".
Also, setting "PerformanceScaling" to "0" can help slightly with texture pop-in and hitching.
Anyway, improvement can range from nonexistent, to quite noticeable, depending on how frequently the game becomes CPU limited. They will generally increase the amount of memory the game needs, especially the size of contiguous chunks it must allocate, but this isn't a problem for me, and your system as twice as much RAM as the one I normally play the game on.