Use the Comparison to Diagnose a Rendering Problem
Vulkan versus OpenGL in Divine Frequency is not a proven one-size-fits-all performance choice. In a September 2024 Demo discussion about missing or see-through surfaces, a developer suggested checking the active renderer and trying OpenGL on affected hardware. That is a concrete compatibility test, rather than evidence that OpenGL is always faster.
The Steam bug-thread response gives the actual setting and explains why it was relevant to that player's graphical problem.
Check the Documented Renderer Values
The developer asked the player to enter vid_renderer in the console to check the renderer in use. The response identifies these values:
| Value | Renderer in the documented Demo advice |
|---|---|
1 | Vulkan |
0 | OpenGL |
For the reported Vulkan problem, the suggested command was vid_renderer 0. Note your current value before changing it, so you retain a clear record of the test.
The source does not give a console-opening key or a complete menu walkthrough. Use the controls available in your installed version instead of assuming an undocumented default binding.
Understand What the Test Can Tell You
The developer explained that the GZDoom Vulkan renderer could have trouble with certain video cards. In that context, checking whether the value was 1 and trying OpenGL was a way to investigate missing floor, ceiling or wall rendering.
A later player reported the same problem with both Vulkan and OpenGL. That result is an important limit: a backend change may help a compatibility issue, but it does not rule out other causes or guarantee a repair.
These are historical Demo reports, not current Early Access benchmarks. Compare the actual visual symptom after a change and include your CPU, GPU and renderer value when reporting a remaining problem. Do not read a general graphics-API benchmark as a measurement of this game on your computer.
FAQ
Which value selects OpenGL in the documented advice?
The September 2024 response suggests vid_renderer 0 for OpenGL when investigating the reported Vulkan rendering issue.
Does Vulkan always cause the missing-surface problem?
No. The response describes possible trouble on certain cards, while another player reported the issue on both backends.
Which renderer is fastest in the current game?
The collected discussion does not establish that ranking. Its useful answer is the historical renderer mapping and a conditional compatibility test, without a guaranteed frame-rate result.