Black Mesa (Steam) Closes Immediately On Startup
Desc: See title. The Steam version of Black Mesa simply quits immediately after startup when RTX Remix is installed in the /bin/ folder (putting it in the same folder as bms.exe simply does nothing). Remix version: 0.1.1 GPU: NVIDIA GeForce RTX 2070 GPU Driver Version: 31.0.15.2756 Game build: Latest stable build, via Steam. Using the -oldgameui launch parameter (makes the game launch with stock Source UII instead of the Qt DX11 UI)
To reproduce:
- Extract the remix-0.1.1.zip file's contents to Black Mesa/bin/.
- Start the game.
Expected Result: Reaching the main menu with RTX Remix enabled.
I've followed the exact same steps on a couple other Source games. Since many of them store files in a /bin/ folder, I wonder if the file structure should be slightly different for them.
Someone made it work. Tried following the instructions but no success. https://www.youtube.com/watch?v=Y2_ubIi09Ss
Someone made it work. Tried following the instructions but no success. https://www.youtube.com/watch?v=Y2_ubIi09Ss
That appears to be using the version included in Portal with RTX which supports source far better than the current version seems to
Someone made it work. Tried following the instructions but no success. https://www.youtube.com/watch?v=Y2_ubIi09Ss
That appears to be using the version included in Portal with RTX which supports source far better than the current version seems to
I wonder if that has something to do with Portal with RTX using DX8 instead of 9.
Black Mesa -as being a newer title- is a DirectX9.0c game and it probably relies on pixel shaders. https://www.pcgamingwiki.com/wiki/Black_Mesa
REMIX REQUIREMENTS Fixed Function Remix functions by intercepting the data the game sends to the GPU, recreating the game's scene based on that data, and then path tracing that recreated scene. With a fixed function graphics pipeline, the game is just sending textures and meshes to the GPU, using standardized data formats. It's reasonable (though not easy) to recreate a scene from this standardized data.
With a shader graphics pipeline, the game can send the data in any format, and the color of a given surface isn't determined until it is actually drawn on the screen. This makes it very difficult to recreate the scene - and there are a lot of other problems I haven't even touched on here.
The transition from 100% fixed function to 100% shader was gradual - most early DirectX 9.0 games only used shaders for particular tricky cases, while later DirectX 9.0 games (like most made with 9.0c) may not use the fixed function pipeline at all. Applying Remix to a game using a mix of techniques will likely result in the fixed function objects showing up, and the shader dependent objects either looking wrong, or not showing up at all. https://discord.com/channels/1028444667789967381/1096179350933618718/1096179390481711154
Just want to note that this game uses Shader Model 3, but also can run on SM 2 (as said in minimal requirements). SM 3 is unsupported by RTX Remix. I'm not sure if it's possible to force this game some how run on SM 2.
Hello @KyuuGryphon - have you revisited Black Mesa since the Remix 0.6 release? We believe that the game should launch successfully with an updated build, the -oldgameui parameter as you described, and choosing DX9 on Steam launch. Please let us know if you're still encountering a crash on startup. Thanks!
Hey @KyuuGryphon - checking in again to see if you've been able to re-test this issue. 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 2 weeks. Thank you!
Hey, sorry for the delay, this totally slipped my mind.
I'm still unable to get it to work correctly - putting the RTX Remix files in the Black Mesa\bin folder doesn't do anything on startup (yes, I'm using the DX9 fallback option, and I always use -oldgameui), nor does putting it next to bms.exe itself. The only way I seem to be able to get it to apply is by replacing the d3d9.dll file in Black Mesa\bin\thirdparty\dxvk-windows-x86 to override DXVK, whereupon it crashes soon after loading up the main menu background map. That part's probably not all that surprising, I imagine. Attached the .log files nonetheless.