Opening the console
In an 18 October 2026 reply, the project lead says to open the console with ~, type gl_precache 1, and press Enter. The thread opened on 14 October; the command instructions are from the later reply.
- 1. Open the console with ~, as the project lead instructs.
- 2. For the resource-loading workaround, enter gl_precache 1 and press Enter.
- 3. To turn that option off, enter gl_precache 0. The developer supplies 0 as the off value in the same reply.
Resource precaching: what changes and what it costs
The project lead explicitly distinguishes resource loading from shader compilation: the engine grabs resources as needed and retains them in memory. The proposed workaround preloads resources at the cost of potentially much longer loads when entering a level or reloading a save. It is not described as a shader-compilation pass.
The reporting player later says stutter improved on their machine and loads remained quick. That is one player’s result in the same thread, not a benchmark or a promise for your hardware. The posts discuss the demo before Early Access; behavior in a later build can differ.
| Exact line | Purpose in the reply | Evidence and version |
|---|---|---|
| gl_precache 1 | Enable the resource-preloading workaround. | Project lead, 18 Oct 2026; pre-Early Access demo discussion. |
| gl_precache 0 | Disable that option. | Same developer reply, not a separate independent source. |
HUD scaling: a player’s exact 2023 workaround
First look for the HUD scaling option in the game settings. The official 7 November 2023 demo patch says that option was added. The console workaround below predates it: Iazu posted these lines on 29 October 2023, in a thread opened on 28 October. These are a single player’s demo-era instructions, not verified current Early Access settings.
- 1. Try the HUD scaling setting in the menu first; the patch confirms its existence but does not give a menu path.
- 2. If you need the older workaround, note your existing settings, open the console, and use hud_oldscale false before the scaling line.
- 3. The player’s literal second line is hud_scalefactor=0.6. Keep the example separate from your preferred scale; no alternate syntax or reset value is established by this post.
| Exact text posted | Player’s explanation | Limit |
|---|---|---|
| hud_oldscale false | Turn off automatic HUD scaling before setting a value. | Single player report, 29 Oct 2023. |
| hud_scalefactor=0.6 | Set the desired scale; 0.6 is the player’s example. | Equals sign preserved from the post. The value is not a universal recommendation. |
Game-specific evidence is not a complete cheat list
These console variables appear in discussions about Divine Frequency; that does not make them exclusive commands written for this game. The cited posts do not provide a complete cheat, item-spawn, or bind list. Commands from a general engine reference should not be presented as confirmed features of the shipped game without game-specific evidence.


Questions
How do you open the console in Divine Frequency?
The project lead says to press ~, type the command, and press Enter, in a reply dated 18 October 2026. The thread itself opened on 14 October.
What are all the Divine Frequency cheats?
The sources on this page do not supply a complete cheat list. They document a resource-loading workaround and a separate player’s 2023 HUD-scaling workaround.
Sources and check date
Last checked 2026-10-29. Where sources disagree, both are kept.
Steam store and API data share one publisher. Attributed developer replies and player reports remain single-source unless a separate source is identified.Verification method.
- Project lead: resource precaching and console instructions — 2026-10-18. Single developer reply in a demo discussion; distinguishes resource loading from shader compilation. Checked 2026-10-29.
- Iazu: exact HUD command syntax — 2023-10-29. Single player workaround, before the HUD menu option. Checked 2026-10-29.
- HUD scaling option: official demo patch via Steam news API — 2023-11-07. Item 5288974951225571912; checked 2026-10-29.
Support mail published by the developer: [email protected]. Editorial mail: [email protected].