I am a huge proponent of not pushing to any limits if you are trying to achieve smooth. If your goal is max fps for the title you are tweaking then 100% is where you will find it. Stability requires having headroom. Windows resource scheduling and management is notorious for adding red lines to your event logs when running flat out. Most of the “fails” in the log will not crash anything but eventually…
Hardware-accelerated GPU scheduling is supported on Pascal and Turing cards from NVIDIA, as well as AMD’s 5600+ series of cards. The 1660 is based on the TU116 graphics processor (Turing) but, you are right, at the bottom end of the scale. As long as you don’t attempt exceeding 1080p you may see some improvement with HAGS on but any resolution above that will be taxing the GPU to the point where you will likely benefit from letting your CPU do the heavy lifting.
I will trust report about difference between HAGS ON or OFF in MSFS when this feature will be switchable via an Hotkey during a fly (read: never).
I say this because just hitting ESC during an MSFS test scene to go to settings, play a little with them saving each time, set back them to original and return to fly and monitored performance has changed, (fps or gpu usage, reproducible on my machine).
Same if you monitor precisely a specific scene, exit, relaunch the sim and return to the same exact scenario, and performance has changed, sometimes a few fps, sometimes more.
So asking a report for a feature which need a complete reboot of your computer, with the MSFS current inconsistency …
Saying that, I saw an improvement in GPU usage in aerofly FS2 in VR with HAGS ON, but this sim run already at 90fps so I had to monitor gpu usage instead. But I really can’t say its impact on MSFS, too many other factors interfering at the same time…
Did you notice each time Microsoft tried to help Gamers (of all kind) by creating stuffs like HAGS, or “Fullscreen Optimization” on executable properties, or “Game Mode” it smell kind of fishy and have the exact opposite effect? I would like to be astonish once by them on this topic…
Sorry, I had a bad day
Thank you!!!
I agree. If you want reproducible test you have to start MS-Windows, start the application with a “check list” and run the test. Before the next test do the same.
Well, this is not Microsoft expertise. I remember the time when all the fast 3D games did NOT use DirectX, because this Microsoft solution was inferior.
Just to close the loop on this, I’ve decided to keep HAGS off unless I start running into problems. 'Course it might have been a solution in search of a problem to begin with, as I wasn’t having any performance issues, except for super high density areas to begin with.
If that changes, or if someone comes along with a “You’d be a dumbass NOT to make the change”, then I’ll revisit it.
Thanks all for your assistance and participation! But this doesn’t mean the conversation is over, please, by all means, keep it up. The more, the merrier!
I had good expectations about the “Game Mode”. At least, who better know than Microsoft which of the thousands processes are useless during a gaming session and can be stopped? I was expecting them to turn them off and save resource, at least this is what I thought. But the “Fullscreen Optimization” seems to do the exact oposite. Instead of let the game having full access to the GPU and the display they intercept it to keep the hand and keep managing it as a window (through the dwn.exe window process) and the game think it run on exclusive fullscreen, but run it in fact in a borderless window.
Regarding HAGS, it’s more obscure for me, I didn’t do research on what they try to achieve here…
Edit : So I did some research about HAGS purposes and several tests I found. The conclusion is pretty clear : Having HAGS ON or OFF is not reliable to save resource in a way or the other It could be slightly positive, or slightly negative, and sometimes both, depending each apps
So the real conclusion is : no conclusion available.
Perhaps in the future when it will be more mature…
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.