Store Page
DOOM + DOOM II
All Discussions Screenshots Artwork Broadcasts Videos News Guides Reviews

DOOM + DOOM II

Store Page
DOOM + DOOM II > Guides > Isaac Clarke S-laughter's Guides
Not enough ratings
How to remove the Remaster's FPS cap. [Can work on Linux too.]
By Isaac Clarke S-laughter
The game somehow caps the FPS to the monitor's refresh, even if no one asked it to.

Read here to remove the cap.

Works with Linux too, for better and for worse, with all the limitations Linux may bring.
   
Award
Favorite
Favorited
Unfavorite
Created by
Isaac Clarke S-laughter
Offline
Languages: English
Posted
Updated
18 Jul @ 5:35pm
19 Jul @ 3:37pm
26 Unique Visitors
0 Current Favorites
Guide Index
Overview
How? 
IF YOU WANT TO, YOU CAN INPUT THE COMMAND DIRECTLY IN THE GAME WHILE IT'S RUNNING. 
Linux is a pain in the Donkey. 
I want to credit this random YouTube video for this info. 
Comments
How?
Go to C:\Users\[YOU!!!]\Saved Games\Nightdive Studios\DOOM in your C: folder and edit kexengine.cfg.

Find the seta cl_engineFPS parameter and edit the number to the desired one.

This may or may not need to be done each time you change resolution and/or refresh rate.

ON WINDOWS I advice you to use Vulkan because D3D11 gives around 2/3 of Vulkan's performance on my machine.
[You HAVE to restart the game to make the Engine change effective.]

I have NO IDEA what "Software (WARP)" does. NOBODY wrote ANY CLEAR INSTRUCTIONS about it.
It SHOULD be "CPU rendering", but the GPU still works!
IF YOU WANT TO, YOU CAN INPUT THE COMMAND DIRECTLY IN THE GAME WHILE IT'S RUNNING.
Just open the Console with the key on your keyboard which is at the left of 1! (for my italian Querty it's the \| key) which should be the "tilde key" and insert "seta cl_engineFPS "1000"", then click Send.
Linux is a pain in the Donkey.
Linux is a capricious beast. It doesn't "just work" as Windows does.

The file on Linux is located in:
/THE_GAME'S_INSTALL_DRIVE/SteamLibrary/steamapps/compatdata/2280/pfx/drive_c/users/steamuser/Saved Games/Nightdive Studios/DOOM/
Everything else is the same.

Paradoxically enough, selecting "Vulkan renderer" gives LESS performance than selecting D3D11 (DirectX) to THEN translate its calls to Vulkan with DXVK (through Proton) WHEN LOOKING AT CPU+GPU's COST TO MAKE EACH FRAME (more on that below here).
Also, at least for Wayland, Fullscreen Vulkan games thend to get their FPS capped at the screen's refresh rate, so if you wanted more FPS for any reason at all you can't. To make things worse, this FPS cap is NOT stable, therefore it may fail to ACTUALLY MEET your monitor's refresh, falling 5 to 15 FPS short.

Selecting D3D11 allows the game to go above the refresh's cap, but you have to add the "DXVK_FRAME_RATE=[insert number here] %command%" in the Launch Options.

MY installation: Fedora KDE (with RTX 2070 and Ryzen 5600x)

Where on Windows 10 the fulscreen'd game gave 600fps with Vulkan (GPU and CPU at 40%) and 300 to 400 with D3D11 (CPU around 35% and GPU from 28 to 40%),
on Linux Vulkan HAS to be proper Windowed (NOT borderless, it HAS to have that bar atop the screen) to NOT be capped at the screen's refresh at full resolution (doing borderless 21:9 on your 16:9 monitor and vice-versa will not cap it, but fullscreen WILL);
Linux's Windowed Vulkan jumps between 520 and 560fps (CPU 40% GPU 60%),
while fullscreen D3D11 jumps from lows of 420fps to highs of 500 (CPU 40% GPU 40%), tending to stay in the middle. Fullscreen doesn't stabilize it, so one can play Borderless without any downside.
I want to credit this random YouTube video for this info.
https://youtu.be/zHR8TD10QIU