NVIDIAGameWorks
Extreme Texture Corruption, RTX Remix Runtime Error
I am having extreme texture corruption in Portal with RTX, and I can't open up the RTX Remix menu unless I first start up the game, to which I can only run the RTX Remix menu for ~5 seconds when I get the RTX Remix Runtime Error. Not sure if that will fix my texture corruption by fixing the RTX Remix, but I can assure you I have deleted all the files and reinstalled my game and that hasn't fixed it. Below I have attached some screenshots and the logs/dmp files.
Logs: bridge32.log bridge64.log remix-dxvk.log
Dmps: NvRemixBridge.exe_20250522_022342.dmp NvRemixBridge.exe_20250522_022402.dmp NvRemixBridge.exe_20250522_022419.dmp NvRemixBridge.exe_20250522_022518.dmp NvRemixBridge.exe_20250522_022627.dmp NvRemixBridge.exe_20250522_022727.dmp NvRemixBridge.exe_20250522_022822.dmp
Corruption: (pictures kept failing to upload so here is a Google Drive with them) https://drive.google.com/drive/folders/1A0jX-8tBLorRA3mrIiD4feQZnlbohchE?usp=sharing
This looks like RTX IO failing to load the textures, though not sure why that'd be happening on a 50 Series card (we've had some issues with it running on AMD in the past, but that's not the case here). Have you tried updating your driver? I think there is a newer one available and that is worth a try.
Also just to clarify, is Portal RTX crashing every time you launch it, or is it only when you open the menu? Just unclear if you're seeing this corruption and then having it crash or if those are two different issues.
I have the latest drivers installed, and Portal RTX only crashes when I open up the Remix menu, so I think they are two different issues.
Well the cause seems to be some sort of issue we have seen before where for whatever reason 2 D3D9 devices are created rather than 1, and this isn't really intended so it crashes or corrupts things. The real question is why is this second device created though and that is less clear by just the logs unfortunately. It may be something Source engine is doing or some sort of bug in the Remix bridge, but it is unknown currently and unable to be reproduced as far as I know.
Given the game runs fine for most people, there is probably something specific about your machine that is causing this to happen which we'd ideally want to identify to be able to reproduce the issue. Did you change any options in Portal RTX related to stuff like resolution of the fullscreen mode at all or did this just start happening on the first launch of the game? Also what sort of monitor do you use, I assume it is 4K based on the resolution it is trying to pick but just want to make sure in case that has something to do with it. Additionally are you using anything uncommonly used in the driver like dynamic resolution scaling? Are you using any sort of overlays that may be causing issues with the game (e.g. hardware monitor-esque things)?
As another test, can you run the game with the arguments -window -width 1920 -height 1080? You can find the command line arguments in Steam by right clicking the game and going to Properties, and it should be the "Launch Options" box in the General tab.
In addition getting some more debug info from the Bridge may be useful, so if you could add logLevel = Debug to a new line into the bridge configuration found at bin/.trex/bridge.conf within the game's Steam directory (Accessible via Properties -> Installed Files -> Browse...), then run the game and collect the bridge32.log and the bridge64.log files that may help.
Well, to start off, I am using a 4K monitor and I can't remember if Portal RTX worked fine on it, as my full playthrough for the first time was on 1920x1080p. I do remember, however, was that shortly before the recent update on May 19th, with DLSS 4, I wanted to launch Portal RTX, as I had just built my new PC. What was different though, is that itt had given me an error completely different from the RTX Remix error I get in HL2 RTX and rarely in Portal RTX. With the update coming out though, that error is gone and I can't remember what it was. Now typing that out though, it gives me an idea. I built my new computer about a month ago, and transferred my SSD from my old PC to my new PC, but never wiped the SSD, so maybe as a thought it could have created 2 D3D9 devices, with one being for my old PC and one for my new PC?? Something that reinforces that is that my brother built an almost identical PC to mine, but inserted a brand new SSD into it and Portal RTX works just fine for him.
This is the monitor I play Portal RTX on: https://www.msi.com/Monitor/MAG-274UPF-E2 And this monitor is on I have to the side that I don't play games on, but I use for other stuff like Youtube. https://www.samsung.com/us/computing/monitors/gaming/27--crg5-240hz-curved-gaming-monitor-lc27rg50fqnxza/
I am not using anything uncommonly used in the driver, and the only overlays I have is Discord Overlay that shows up when I start the game and NVIDIA Overlay, but no monitor overlays.
As for the 1920x1080 test, it did nothing but shrink my game size to 1920x1080.
I added LogLevel = Debug into bridge.conf and ran the game. Here are the files.
Unfortunately I should've specified that log level option in the bridge config is case sensitive, it should be logLevel = Debug not LogLevel = Debug, so if you could adjust it to have the proper case sensitivity and re-run it that will be useful.
Oh, oops. Here you are. I tried to type it word-for-word as what you had said. Probably would have been better to copy-paste it as I didn't realize the log part was lowercase.
