ValveSoftware / ValveSoftware/Proton
Doom 2016 (379720) Black screen on start up, no sound. Game crashes after a few minutes.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 32.8k
- Forks
- 1.6k
- PR merge metrics
- PR metrics pending
Description
Hello, I originally made a post in this thread : https://github.com/ValveSoftware/Proton/issues/217
I'm not sure if it is a better idea to just make a new post on this subject, or stay with that one. So I'll just create a new thread.
I am having the same issue seen in the thread above. I try to run the game and it goes to a black screen with no sound.
-
I've tried launching the game with different settings like +r_renderAPI 1 and +r_renderAPI 0 as well as the no intro video command. Nothing worked.
-
I tried the Winetricks Xinput suggestion listed here:
https://github.com/ValveSoftware/Proton/issues/217#issuecomment-415440649
And no luck either.
- I also tried this Winetrick: https://github.com/ValveSoftware/Proton/issues/217#issuecomment-415407297
But, to be honest, I have no idea how to install vcrun2015 using Winetricks.
- Finally, I do not own a wireless gamepad for my PC and I unplugged my wired gamepads.
My system specs
- i5 2600k
- Geforce 660 3GB
- 16GB DDR3
- Linux Mint 19
- Nvidia 396.54 drivers
- Proton 3.7-4
- Linux Kernel 4.15.0-33-generic
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names no source file, test, or entry point. Start by reviewing the linked Proton issue 217 and reproducing the failure with Proton 3.7-4 on the listed Linux Mint, Nvidia driver, and hardware setup. Done means identifying and resolving the black screen, missing sound, and subsequent crash.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- linux
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100