NVIDIAGameWorks / NVIDIAGameWorks/rtx-remix
[Runtime Bug]: Crash on start for both Portal and HL2:RTX
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
These are for the steam release versions, not any personal meddling. The application opens, whether it be portal or half-life 2. That is it. By opens, I mean the valve brand screen displays, with the Remix blurbs in all their normal spots. That last for about 1-2 seconds. The sound of the valve theme cuts off, and the application freezes. After about 20 seconds of thinking, and my tired clicking, the application closes or the Runtime failure box appears. My drivers have always been the newest possible, but this has been a persistent issue with portal and now HL2.
How do you reproduce the bug?
Fresh download the game and press play, apparently. :)
Those were the only steps taken for HL2
What is the expected behavior?
I've played Portal RTX. Much closer to the game's release, it actually booted, and worked, and I could play levels, and it was fun. Then the next time I tried, and believe me I've scared myself with some things I've tried, it does not open.
Version
Whatever HL2 has
Logs
bridge32.log
bridge64.log
remix-dxvk.log
Crash dumps
NvRemixBridge.exe_20250313_150153.dmp
NvRemixBridge.exe_20250319_012057.dmp
NvRemixBridge.exe_20250319_012408.dmp
NvRemixBridge.exe_20250319_014729.dmp
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
Start by comparing bridge32.log, bridge64.log, remix-dxvk.log, and the four NvRemixBridge crash dumps attached to the issue. Reproduce the startup freeze with the Steam Portal or HL2 release and use those artifacts to isolate the runtime failure. Done means the affected game reaches gameplay without the Runtime failure box.
Written by the indexing model from the issue text.
Assessment
- Domain
- computer-graphics, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100