Windows Hardware Accelerated Graphics Scheduler of HAGS is a bit of a mystery. It’s off by default (you can turn it on in Display settings / Graphics Settings sub-menu) and apparently it should speed up stuff to be given to the GPU to munch on. It has always seemed ineffective.
Here’s a tech write up for nerds of what it’s trying to do:
Here’s a review of a bunch of games where it doesn’t really help, and in some cases makes worse:
So I thought I’d at least try it again with the most recent driver and my ‘house or GPU’ priced hardware - perhaps things are better?
Here’s a quick CapFrameX run with HAGS off and then HAGS on, in VR using the OpenXR NIS of 80%. This is from a 60 second capture average of a freeflight in a C152 over YVR in real weather - the exact settings aren’t so important more that just the single HAGS setting had changed between runs.
Ok, seat of the pants test: no noticeable difference. With HAGS = On I did get a blue screen while it tried to load a dense urban scene but that could be a SteamVr/WMR/LMNOP thing. It came back within a second. Not scientific, more a a WAG on HAGS Couldn’t resist.
I tried a few different ways a some more games and I just can’t get any improvement out of it. I think it’s a good idea, but the trouble is that games when they get tested and profiled before release already have to deal with the CPU → GPU instruction buffer without HAGS. No-one is going to release a title that relies on there being a hardware scheduler (because they all use a buffer anyway), so any bottleneck around GPU instruction hand-off has to be sorted out assuming HAGS doesn’t exist.