[Runtime Bug]: When starting
Describe the bug
getting a RTX Remix Runtime Error when trying to launch the game
How do you reproduce the bug?
start the game via steam
Specs: AMD Ryzen 7 5700X3D Nvidia RTX 4070 Ti 32GB RAM
What is the expected behavior?
the game launches
Version
Build 17766009
Logs
bridge32.log bridge64.log remix-dxvk.log
Crash dumps
NvRemixBridge.exe_20250313_150153.dmp
Media
Were there any other dump files in the .trex folder along with this crash? This NvRemixBridge.exe_20250313_150153.dmp file was accidentally included in the current build of HL2: RTX and isn't the one associated with a crash.
Were there any other dump files in the .trex folder along with this crash? This
NvRemixBridge.exe_20250313_150153.dmpfile was accidentally included in the current build of HL2: RTX and isn't the one associated with a crash.
nope, thats the only one i could find i'll redownload the game and take a look if there is another dump somewhere
i can not find any other dump file anywhere
Might not be able to diagnose what this is in that case since it's a crash of some sort but without a dump it's a bit of a mystery.
thats unfortunate. is there anything i could try to get the dump file to be created when the game crashes?
Well you can try running it multiple times, crashing is rather unpredictable and sometimes it crashes before it can write a dump file out which results in either no file or an empty file. So if you can run it a few times and get it to crash in the same way it may get more lucky and output a dump like it should.
Alternatively you can try to uncomment (remove the # from) this line in the dxvk.conf in the root directory of the game:
dxvk.enableAftermath = True
That will enable aftermath dumps which may be able to output as well if there's some sort of GPU crash causing this. It will output a file like hl2_*-*_aftermath.nv-gpudmp in the game's root directory if it detects a problem like that and is able to (but may not if this is just a CPU-related crash).
Hi @whk2518 - checking in to see if you've been able to find another dump after reproducing this crash, per the previous comment. We'd also like to inform you of our stale ticket policy, specifically that this ticket will be closed as 'went stale' if it does not receive a response in the next 2 weeks. Thank you!
Hi @whk2518 - checking in to see if you've been able to find another dump after reproducing this crash, per the comment above. Thank you!