Static on monitors in intro cutscene

[JasonFyre2k]

Describe the bug
On Nightly Windows builds from Nov 21, 2024 to the most recent ones there is a bug/glitch where during the intro cutscene the monitors show only static. I mostly tested x64 builds, but seems to occur in x86 builds as well. Due to lack of time, I didn't play long enough to see if other monitors further in the game are affected.

The Nightly Windows build from Nov 19, 2024 seems to be the most recent version that does not have this issue.

To Reproduce
Steps to reproduce the behavior:
Download the most recent Windows Nightly build, or any build going back to Nov 21, 2024 or later, and start a new game.

Expected behavior
Instead of static, the monitors should show various charts and graphs and a camera following Swann's( and the players') ship as it passes by the control room.

Screenshots

Monitors with static glitches:
https://i.imgur.com/BA41cG8.jpeg
https://i.imgur.com/nmYzyeU.jpeg

How they're supposed to look:
https://i.imgur.com/7Tqy5jA.jpeg
https://i.imgur.com/SwyeW7T.jpeg

Desktop (please complete the following information):

• OS: Windows 11 Home
• CPU: 13th Gen Intel(R) Core(TM) i7-13700F
• GPU: RTX 4070
• Memory: 16 GB DDR5-5600
• Monitor: Samsung TV
• GPU Driver Version: 572.16
• Version: nightly-2024-11-21-21-02-1732222953 (and above)

Additional context
Add any other context about the problem here.

[MadDeCoDeR]

Hi there, sorry for the late reply. Can you also share the log file? In order to generate it use the debug build and run it with the launch argument +set logfile 1, the log file will be in C:\Users<username>\Saved Games\id software\DOOM BFA\base\qconsole.log.
Another workaround is to delete the folder renderprogs in the above folder

[JasonFyre2k]

Sure, this is the log from the lastest nightly build, atm. I zipped it up bc it was 120+ mbs. I did a fresh install of DoomBFA, started a new game and played a little past meeting the sarge.
qconsole_1.zip

Also, I noticed this glitch affects many, many screens, not just the monitors from the intro cutscene but also signage, the green and red mini-screens on doors(that let you know if they are open or locked) and even some interactive monitors and keypads -- including the keypads on the storage cabinets.

I tried deleting the renderprogs folder just now and ran the game again and it didn't seem to help.

[MadDeCoDeR]

It might sound stupid but can you try to use the launch argument +set g_useNewGuiCode 0.
It should in theory use something closer to the OG DOOM 3 gui code and hopefully it can make the screens to render properly.

EDIT: Also sorry for asking for the logs (they barely mention anything about the issue). I just wanted logs from anyone with a Nvidia GPU (and oh god the verbosity of those logs)

[JasonFyre2k]

I tried it with the latest x64 bit version:
[ nightly-2025-04-15-17-13-1744737221
OpenAL - Minor buffer cleanup improvement ]

Unfortunately, the launch argument makes the static issue worse.

The monitor from the intro cutscene:
https://imgur.com/0bwRb33
(there is now an additional constant glitch on the left side, plus other artifacts that where popping in-and-out that I didn't catch in the screenshot.)

Also, if you look closely here, you'll see that not only does this monitor display static, but now there are also lines extruding outwards from the corners.
https://imgur.com/MR6lVgF
(these additional lines coming out of the corners where on other monitors with the static glitches too.)

These additional artifacts/glitches aren't present without the launch argument, just the static.

[MadDeCoDeR]

So I found also this Steam forum post: https://steamcommunity.com/app/208200/discussions/0/517142253868828494.
It says that one fix is to delete the C:\Users\ \Saved Games\Id Software\DOOM BFA\base\DBFAConfig.cfg.
Before you do that (and if it works) can you send me your config file (in order to see what cvars has)

[JasonFyre2k]

I actually have the clean Doom3BFG game files backed up in a zip file in my Steam Library folder. So every time I tested DoomBFA I've downloaded a fresh version and installed it on top of 'clean' game files and then after I was done with it, I deleted the whole Doom3BFG game folder and the saves/config files in the C:\Users...\id Software\DOOMBFA folder. Then I unzipped the clean backup Doom3BFG zip into my Steam Library folder and verified files through Steam.

So basically, I've always started from scratch without the config file anyway and the settings and cvars should be default. But for thoroughness, I did just now re-install the latest x64 bit version, ran it once to generate the Doombfa config file and started a new game to verify the static glitch was still happening, then quit the game, moved the config to the desktop and re-ran the game. It didn't help.

Idk if you'd still be interested as all settings are presumably default, and the static glitch was still present afterwards, but here is the config file.
(I changed the extension to .txt so I could attach it to this post.)
DBFAConfig.cfg.txt

Well I don't want to take up anymore of your time with this as according to that Steam post, some people where experiencing this issue even with the original game anyway(which I'm not, interestingly.)

Thanks for your time.

[CODEX0827]

i also have this problem

[dwing4g]

I also encountered the same issue, but the trigger condition ONLY occurs with NVIDIA GPUs when HDR is turned off. If HDR is on, it works fine.
Additionally, there are NO problems with AMD GPUs. I have also confirmed that this issue started from the DOOM BFA Nightly 2024-11-21-21-02-1732222953.

[MadDeCoDeR]

I just undid some weird changes I had done on glimp (possibly for VR rendering before the new triple buffering rendering system I made). Hopefully those changes were the reason for the issue. If anyone with nVidia GPU want try to test it to verify (sadly I don't have an nVidia GPU)

[dwing4g]

I just undid some weird changes I had done on glimp (possibly for VR rendering before the new triple buffering rendering system I made). Hopefully those changes were the reason for the issue. If anyone with nVidia GPU want try to test it to verify (sadly I don't have an nVidia GPU)

I just tested this latest release and it does indeed solve the rendering issue of nVidia GPUs. It also works fine when HDR is off.