GPT have me a boat load of info here is a bit more detail for the tech gurus here. I don’t vet all this info so let me know if it’s throwing shade my way.
If the Monitor Supports Higher Refresh Rates (Same Setup Otherwise)
• Higher Hz reduces visible stutter but does not remove the root cause, because the DX11 presentation stall still occurs inside the Windows compositor pipeline.
• VRR can mask short stalls on high-Hz monitors, but longer 1–2 second DXGI stalls will still break frame delivery and be noticeable.
• Running uncapped or mismatched Hz can worsen timing conflicts, increasing the chance of DX11 queue desynchronization under Windows scheduling.
• Best practice remains fixed refresh + capped FPS, even on high-Hz panels, to keep presentation timing deterministic and stable.
Why DX9 “Fixes” the Issue (What That Proves)
1. DX9 bypasses the modern DXGI presentation pipeline, avoiding Windows compositor, flip-model swaps, and frame pacing layers required by DX11.
2. DX11 depends on OS-level frame presentation timing, so Windows scheduling hiccups can stall frames even when GPU utilization and FPS counters look normal.
3. Hardware-Accelerated GPU Scheduling interferes with DX11 queue depth, creating long presentation stalls on fixed-refresh displays without triggering GPU overload.
4. DX9 stability proves rendering is not the problem, confirming the fault occurs after frame completion during OS-managed presentation.
5. Fixed-refresh TVs expose presentation stalls more clearly, because missed vsync intervals manifest as visible pauses instead of minor tearing or adaptive correction.
6. Recent Windows updates tightened flip-model behavior, increasing sensitivity to timing conflicts between the CPU scheduler, GPU queues, and display refresh.
7. DX11’s reliance on modern driver paths increases fragility, while DX9’s legacy immediate-mode path remains largely untouched by newer Windows graphics changes.
If DX9 “Fixes” the Issue, What That Actually Proves
Core conclusion:
The fault lies in the Windows 10/11 DX11 presentation and scheduling pipeline, not GPU throughput, thermals, or raw rendering performance.
Expanded technical breakdown
• DX9 uses a legacy, CPU-driven presentation path
DX9 relies on an older, synchronous Present model with limited OS-level GPU scheduling involvement, bypassing modern DXGI flip-model complexities entirely.
• DX11 depends on DXGI + Windows GPU scheduler correctness
DX11 frame delivery is mediated by DXGI, the Desktop Window Manager (DWM), and the Windows graphics scheduler, making it sensitive to timing mismatches introduced by HAGS or driver-level queue reordering.
• Hardware Accelerated GPU Scheduling (HAGS) alters frame submission order
HAGS shifts scheduling responsibility from the OS to the GPU, introducing asynchronous command submission that can conflict with applications expecting deterministic Present timing.
• Fixed-refresh displays magnify scheduling jitter
TVs locked at 59–60 Hz provide no adaptive refresh buffer, so even brief scheduling stalls manifest as visible 1–2 second micro-stutters instead of minor frame drops.
• DX9 avoids the flip-model swap chain entirely
By using a blit-based or legacy swap chain path, DX9 sidesteps modern flip-model behavior where missed presentation deadlines can stall the render queue.
• The GPU is never the bottleneck in this failure mode
The absence of sustained FPS drops, thermal throttling, or load spikes confirms the GPU is underutilized; the stall occurs after rendering, during presentation.
• Why VR users cannot rely on DX9
VR runtimes require DX11+ features, explicit synchronization, and low-latency present paths, making DX9 an unacceptable workaround for affected VR players.
⸻
What DX9 “Fixing It” Does Not Mean
• ❌ It does not mean the GPU is too weak
• ❌ It does not mean Aces High III is poorly optimized
• ❌ It does not mean the NVIDIA driver is fundamentally broken
• ❌ It does not mean reducing graphics settings is required
It means the DX11 → Windows → Display timing chain is being disrupted by modern scheduling features that AHIII does not need and does not benefit from.
If You Do NOT Have an NVIDIA GPU
The root issue still applies
• The stutter is not NVIDIA-specific.
• It originates from DX11 + Windows flip-model presentation + fixed-refresh displays.
• Any GPU that uses the modern Windows compositor path can be affected.
⸻
AMD GPUs
Usually fixable with similar steps, but needs closer attention.
• AMD drivers expose fewer explicit presentation controls than NVIDIA.
• HAGS, fullscreen optimizations, and flip-model conflicts still apply.
• AMD’s frame pacing is more sensitive to mixed refresh logic.
Typical fixes:
• Disable HAGS in Windows.
• Disable Optimizations for Windowed Games.
• Turn off FreeSync on fixed-refresh TVs.
• Use exclusive fullscreen where possible.
Result:
Most AMD users report improvement, but may need trial-and-error with VSync and FreeSync combinations.
⸻
Intel iGPU / Arc GPUs
More variable and requires more review.
• Intel relies heavily on OS-managed scheduling.
• Driver maturity and presentation stability vary by generation.
• Micro-stutter often correlates with power management and memory latency.
Additional steps often required:
• Lock CPU minimum frequency in Windows power plan.
• Disable panel self-refresh and adaptive brightness.
• Avoid borderless/windowed modes entirely.
Result:
Fixable in many cases, but not guaranteed without deeper tuning.
⸻
Why NVIDIA Was “Easier” in Your Case
• NVIDIA exposes clear driver-level controls.
• Their DX11 implementation handles fixed-refresh TVs more predictably.
• Disabling HAGS + letting the app control VSync removes nearly all ambiguity.
Your fix worked cleanly because:
• Fixed 59.94 Hz display
• No VRR
• Strong driver-level override support
• Stable DX11 frame queue behavior
⸻
Bottom Line (Forum-Safe Summary)
• This is a Windows/DX11 presentation issue, not a GPU brand defect.
• NVIDIA systems are easier to stabilize, not immune.
• AMD and Intel users can often fix it, but may require extra tuning and validation.
• If DX9 eliminates the stutter, the GPU is not underpowered—the pipeline is misaligned.
