ValveSoftware / ValveSoftware/Proton
BloodRayne: Terminal Cut (1373510)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 32.8k
- Forks
- 1.6k
- PR merge metrics
- PR metrics pending
Description
Compatibility Report
- Name of the game with compatibility issues: BloodRayne: Terminal Cut
- Steam AppID of the game: 1373510
System Information
-
GPU: GTX 3080
-
Driver/LLVM version: 5.25
-
Kernel version: 6.1.5
-
Proton version: Experimental
I confirm:
- that I haven't found an existing compatibility report for this game.
- that I have checked whether there are updates for my system available.
Symptoms
This game happens to use a DX8 to 9 wrapper to convert its calls, but due to how proton is set up, ignores said wrapper. Causing massive performance issues (and seeing my card as a 470?) as it will fallback to wine D3D, also means no Mangohud amongst other things. Adding WINEDLLOVERRIDES="d3d8=n" to the launch options fixes all of this, as the calls get properly converted to VK. Performance is fixed and my card is properly seen as a 3080.
I'm unsure if it's possible for you to add d3d8.dll as a built in then native launch option to all of proton, as its the only fix for this on your end.
Besides that, game works fine, no issues so far, might be some graphical issues but its hard to tell whats caused by the 8-9-vk chain and whats caused by it simply being an old game.
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
Start by reproducing BloodRayne: Terminal Cut with Proton Experimental and compare its behavior with WINEDLLOVERRIDES="d3d8=n" enabled. The report names no source files or tests, so trace how Proton handles d3d8 DLL selection and determine whether the requested built-in/native behavior is feasible. Done means the game uses the intended Vulkan conversion with corrected performance and GPU detection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100