Divine Frequency Stutter Fix: FPS Drops, VSync, and Alt-Tab

What should I try first for Divine Frequency stutter or FPS drops?

Some Windows Early Access players of Divine Frequency (Abraxaes) report hitching, FPS drops, or the GPU pegged at 100% in community threads. Try the official itch.io known issue first (VSync), then community-reported steps (HUD size 1.0, alt-tab, GL Texture Precaching, mouse polling)—none are guaranteed fixes. See system requirements and Proton for OpenGL 3.3 minimum vs OpenGL 4.0 / Vulkan recommended specs.

Quick triage (try in this order)

1. Set HUD size to 1.0 — Community-reported (pinned Steam discussion, Lupmzzcat): larger HUD scale numbers in the menu mean a smaller HUD and were associated with stutter in that thread. The HUD scaling option exists per a 2023 demo patch; confirm the same menu in EA.
2. Toggle VSync — Official known issue (itch.io): VSync destroys framerates (sometimes helps — “known bug!”). Test on and off; do not assume one setting wins everywhere.
3. If FPS collapses after a few minutes until you alt-tab — Community-reported: alt-tab away and refocus the window; the thread exists because others saw GPU 100% and ~9–12 FPS after 1–5 minutes until refocus.
4. Adjust GL Texture Precaching — Community suggestion (same GPU/alt-tab thread): players suggest tweaking this option in the menu; effect varies by machine.
5. Lower mouse polling rate — Community suggestion (same thread): 1000 Hz may be too high for the engine; try a lower rate if you use a high-polling gaming mouse.

For Defender false positives on DivineFrequency.exe, see engine, GZDoom/UZDoom, and Windows Defender—that is separate from frame pacing but can block a clean launch.

Why does VSync behave oddly in Divine Frequency?

The itch.io project page documents a known issue: VSync destroys framerates, with a note that it sometimes helps—labeled “known bug!” by the developer on that page. That is official acknowledgment of inconsistent behavior, not a prescription to leave VSync on or off. If your search landed on “divine frequency vsync,” treat it as a toggle to experiment with after you note baseline FPS with VSync off and on. Pair this with the settings and keybinds guide for other menu options added across demo patches—always confirm in the current Early Access build.

How do I reduce general stutter and hitching?

Beyond VSync, the strongest recurring community signal is HUD size at 1.0 in the pinned stutter thread (Lupmzzcat, Steam). The counter-intuitive part—higher HUD scale numbers shrink the HUD—is how that poster described the menu; if your HUD scale is not 1.0, resetting to 1.0 is the thread’s first suggestion. GL Texture Precaching and mouse polling rate appear as additional suggestions in the GPU 100% / alt-tab discussion; one community member proposed that 1000 Hz polling may be too high for the engine. Players also report demo-era-style collapses from very high FPS to ~30 FPS and room-related instability in an EA launch discussion—treat that as anecdotal unless you reproduce it.

A Steam hub review comment by ltron asked for shader pre-compilation to reduce stutter—that is a feature request, not evidence that missing pre-compilation is the confirmed cause of EA stutter. We do not list it as a fix.

What is the GPU at 100% and alt-tab FPS drop?

In a Steam thread created for the issue, players describe GPU usage at 100% with roughly 9–12 FPS after one to five minutes of play until alt-tabbing out and back refocuses the game and performance returns. That pattern is community-reported; the thread’s purpose is exactly that symptom cluster. If it matches you, try alt-tab refocus as a temporary workaround and note whether GL Texture Precaching or mouse polling changes anything—same thread, same hedging. Heavy screen effects in the intro bothered at least one GamingOnLinux reviewer (2026-10-27); that is media opinion, not a GPU-at-100% diagnosis.

What could not be verified yet?

• No official EA launch-day patch notes or build ID appeared in Steam news on 2026-10-28—we cannot say Abraxaes shipped a post-launch performance hotfix under a public changelog.
• HUD 1.0, alt-tab, GL Texture Precaching, and mouse polling are not confirmed as adopted fixes on an official roadmap—only as player reports and thread suggestions.
• Shader pre-compilation as a stutter cause is not confirmed; only requested in a review comment.
• Demo patch notes (2023-11-07, 2026-06-22) document options like HUD scaling; menu names in EA may match or drift—verify in-game.

If performance kills the fun, weigh that against EA scope in is Divine Frequency worth it? before you assume a driver or settings silver bullet exists.

How do I report a performance bug usefully?

Post in the pinned bug-reporting thread by Bridgeburner on the Steam community hub for Divine Frequency. Include Windows version, GPU model, whether you are on minimum OpenGL 3.3 or recommended OpenGL 4.0 / Vulkan, VSync on/off, HUD size value, and whether alt-tab changed FPS. Link to the stutter or GPU threads if your symptoms match—duplicate structured reports help more than “it lags.”

Symptom quick reference

Where does this information come from?

• Divine Frequency on itch.io — VSync known issue (observed 2026-10-28).
• Steam discussion: pinned stutter / HUD size — Lupmzzcat HUD 1.0 workaround (observed 2026-10-28).
• Steam discussion: GPU 100% / alt-tab — FPS collapse until refocus; GL Texture Precaching and mouse polling suggestions (observed 2026-10-28).
• Steam discussion: EA launch FPS / room report — high FPS to ~30 FPS report (observed 2026-10-28).
• Steam store / hub — ltron shader pre-compilation feature request context (observed 2026-10-28).
• Steam discussion: pinned bug reports — Bridgeburner thread (observed 2026-10-28).
• Demo update 2023-11-07 (Bridgeburner) — HUD scaling option (observed 2026-10-28).
• GamingOnLinux Early Access article — GZDoom/UZDoom engine note (published 2026-10-27, observed 2026-10-28).

Verified against the sources above on 2026-10-28.