NVIDIAGameWorks / NVIDIAGameWorks/rtx-remix
[Runtime Bug]: Remove Stale Halo CE Configuration
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.7k
- Forks
- 99
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
As discussed on discord with NV_Mark, Halo CE / PC currently has hardcoded config.cpp options which may have been accidentally saved or added. It should probably be removed, or at the very least the default dxvk base options should be left, and useObsoleteHashOnTextureUpload + textures removed.
How do you reproduce the bug?
See description
What is the expected behavior?
The runtime should...
Version
latest
Logs
No response
Crash dumps
No response
Media
No response
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
Open src/util/config/config.cpp around line 340 and inspect the hardcoded Halo CE/PC options. Compare them with the default DXVK base options, then remove the stale configuration, including useObsoleteHashOnTextureUpload and the specified textures. Done means those accidental Halo CE/PC overrides are no longer present.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100