Game Mode isn’t a magic FPS button. Microsoft’s own documentation says the impact depends on how much is running in the background and how heavy it is; in many games the feature is already on by default. Diagnostics should check the state and measure the machine, not force the same policy on everyone.
HAGS depends on WDDM, driver and device support. The capabilities API reports whether the hardware supports it and whether scheduling is enabled. Rise should treat the feature as a compatible experiment, with a restart when needed and a controlled comparison.
A native request for a lower timer resolution can increase wakeups and power use; Microsoft warns about that cost. It’s a temporary diagnostic feature, not an FPS promise, and it shouldn’t stay on without a reason.
The Rise catalog keeps these options out of the automatic plan when they need measurement or a restore point. You can test, confirm and revert; the real result is what decides.
