ValveSoftware / ValveSoftware/Proton
Display issues and crashes with multiple GPUs.
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 32.8k
- Forks
- 1.6k
- PR merge metrics
- PR metrics pending
Description
This may be more of a Wine issue than Proton, but I just found out why no versions of Proton (4.x - 5.6) were working for me. This issue comes from part of a thread started here: https://github.com/ValveSoftware/Proton/issues/3224#issuecomment-612948434
I have a primary NVidia card and a secondary AMD card with no monitor attached. Any app starting that attempts to set resolution fails as the AMD card has no screen and thus no modes available. I finally found the answers in a D3D log. The only solution I've found is to physically remove the AMD device so everything defaults to my primary. Not sure if Wine is sorting GPU devices by alphabetical order or what but how frustrating...
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
No source file, test, or entry point is named. Start by reviewing the linked Proton issue thread and reproducing the failure with primary NVIDIA and secondary AMD GPUs, then use the D3D log to identify the affected display or GPU-selection path; done means the reported multi-GPU resolution failure is fixed and verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100