mirror of
https://github.com/games-on-whales/wolf.git
synced 2026-10-15 21:12:08 +00:00
[GH-ISSUE #248] DOOM Dark Ages Launches to a Black Screen #171
Labels
No labels
🧠 1 - 🤖 999
AMD
bug
bug
cannot reproduce
documentation
duplicate
easy
enhancement
enhancement
enhancement
fixed?
fixed?
good first issue
hard
help wanted
Intel
invalid
LXC
medium
moonlight-protocol
Multi GPU
nixos
not a bug
nvidia
pull-request
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
games-on-whales/wolf#171
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jakepi84 on GitHub (Sep 5, 2025).
Original GitHub issue: https://github.com/games-on-whales/wolf/issues/248
Hello,
The game will load, play the intro videos, but results in a black screen when entering the main menu. This is the only game this happens with. I don't see anything obvious in either the wolf or WolfSteam container logs with debugging on. I am not sure where else to look for troubleshooting?
I am running wolf docker within an LXC on Proxmox 9.0.6. My LXC meets the minimum requirements for the game (I know its finicky with anything less then 8 Cores and 16GB of RAM).
Below are my logs, guess I am not sure where to look next? Other games play great on Wolf.
WolfSteam Container
docker-compose.yml
lxc conf
@ABeltramo commented on GitHub (Sep 5, 2025):
There are a few similar reports in protondb: https://www.protondb.com/app/3017860
Have you tried changing the proton version from the Steam settings page for the game?
@jakepi84 commented on GitHub (Sep 5, 2025):
I have tried multiple versions (v9, v10, Experimental, and Hotfix) all produce the same result. You can't change the proton version more then once a day or else the DRM flags you as having installed on too many computers and locks you out of the game for 24 hours. I loaded the game on my steam deck and verified I did not have any upscaler or frame generation enabled, I know that is another common issue.
This issue if obviously a low priority, the game is a struggle to run on a native Linux desktop. Heck it is even a struggle to run on Windows it seems. :)
The config.toml for Steam does have Proton logging enabled, I am not sure where these logs are though within the container? Or are there additional logs I can dig into to try and troubleshoot? Thank you again for all of your work on this project and for the assistance.
'env = [ 'TZ=America/Chicago', 'PROTON_LOG=1', 'RUN_GAMESCOPE=true', 'GOW_REQUIRED_DEVICES=/dev/input/* /dev/dri/* /dev/nvidia*' ]'
@a-priestley commented on GitHub (Nov 25, 2025):
Same exact issue here! I've gone through several tinkerings in protondb but nothing seems to work.
@a-priestley commented on GitHub (Nov 26, 2025):
Can confirm that the game works (at least past the point where it shows a black screen running under wolf) on the host machine natively, using proton experimental and no additional tweaks.
This issue may not be the same one often seen posted on protondb. From what I'm reading, the screen typically goes black and audio can be heard after the initial loading screen following the splash logo screens. Whereas in Wolf, the splash screen logos appear as normal, after which the loading screen does not show up and no audio can be heard.
Could it be DRM related? It employs Denuvo, which sucks because as @jakepi84 mentioned, changing the compatibility tool too often will lock you out since denuvo thinks you're installing on a new machine (this literally just happened to me).
@Greaper88 commented on GitHub (Nov 26, 2025):
Was the first game I tested after installing Wolf on my server. Ran without any issue or tweaks. As for the black screen with audio, i did have that happen even on a Windows machine. Updating the drivers resolved that one though.
@a-priestley commented on GitHub (Nov 26, 2025):
could be hardware differences? I'm on an intel cpu with an amd gpu.
@Greaper88 commented on GitHub (Nov 26, 2025):
First time was Intel CPU with nVidia dGPU. Currently on a Threadripper using the same nVidia Quadro RTX card.
I do have an AMD GPU coming in, so I'll see how it goes when I get that in.
@NumberedThought commented on GitHub (Nov 26, 2025):
Have you tried it without gamescope? Edit: Nevermind. black screen in sway as well
@a-priestley commented on GitHub (Dec 3, 2025):
Hopefully this is useful information -- issue is not present when streaming the game over sunshine.
@Greaper88 commented on GitHub (Dec 3, 2025):
I tested an AMD RX 6650 XT in my system, and had the same issue. I did attempt a few things listed on the ProtonDB site, but no success. Switched back to my nVidia card and it started right up.
@NumberedThought commented on GitHub (Dec 3, 2025):
it's not an issue with proton. I've been able to run it on the same machine that GOW is on without streaming/docker and no issue. Either it's a gstreamer issue, or a docker issue. I think the latter and some lower level abstraction
@a-priestley commented on GitHub (Dec 4, 2025):
Just curious what makes you think it is one over the other?
@jakepi84 commented on GitHub (Dec 4, 2025):
Issue does seem to only impact AMD GPUs. @Greaper88 seems to have it working on Nvidia. I did test it on an Intel B580 and the game also loaded, some graphical issues but thats pretty typical on Battlemage. The game seems to be OK running in a container, so I am doubting it’s a Docker / Abstraction / DRM issue.
@a-priestley commented on GitHub (Dec 4, 2025):
Also of note: as soon as the black screen appears, steam overlay ceases to respond.
Launching without the overlay: same result.
I've also tried using integrated for encoding (QSV): same result.
@NumberedThought commented on GitHub (Dec 4, 2025):
interesting. That makes sense as I have an AMD GPU. maybe the VA gstreamer encoder?
@a-priestley commented on GitHub (Dec 4, 2025):
Like I said, I tried QSV encode but sad too say, there was no change. Is it even possible for it to be a stream encode issue? When just that one window is failing to render and produces no audio, but everything else is normal, I think it points elsewhere.
@Greaper88 commented on GitHub (Dec 5, 2025):
Oh yeah, on my AMD RX 6650 XT card, Doom Dark Ages does not work. After a few minutes, it crashes out and returns me to the Steam interface. Steam Eternal works fine though with raytracing enabled.
On my nVidia Quadro RTX 4000 card, Dark Ages launches and runs no problems, and runs pretty smooth for a workstation card.
I have not attempted running the game directly on the host though, only via GOW.
@a-priestley commented on GitHub (Dec 5, 2025):
@Greaper88 it's crashing for you? Would you be willing to share logs / game config (in steam)?
@Greaper88 commented on GitHub (Dec 5, 2025):
"Crashing" might be the wrong word? Not sure how to access those logs honestly, as it's not part of the main wolf logs. It does as you described, however. I think it's just Steam realizing something isn't working and killing it, but IDK.
It does the launching game screen, then turns black. After a few minutes the Steam interface becomes visible again and the button turns back to the green "Play" button.
@a-priestley commented on GitHub (Dec 13, 2025):
That's strange. For me it doesn't terminate. Just black screen until I manually stop it.
Same issue with the latest GE-Proton10-26. Maybe there are some AMD-specific flags I can try passing.
@jakepi84 commented on GitHub (Dec 13, 2025):
I experience the same. It makes it even harder to troubleshoot since the app doesn’t crash or throw any useful logs. It’s like it “thinks” it’s working.
It appears Wolf is using a version of Mesa from 05/2025, it might be too old for Doom Dark Ages? Unless I am understanding this build wrong.
https://raw.githubusercontent.com/games-on-whales/wolf/refs/heads/stable/.github/workflows/docker-build.yml