steamtinkerlaunch VS Proton

You probably mean SteamTinkerLaunch

I've tried all of the known methods, the one using bottles:https://github.com/thesupersonic16/HedgeModManager/wiki/Running-on-Linux-(Wine), the one using Steamtinkerlaunch: https://github.com/sonic2kk/steamtinkerlaunch/wiki/Hedge-Mod-Manager and the one that used to work but doesn't anymore:https://linuxgamingcentral.com/posts/updated-sonic-frontiers-steam-deck-modding-guide/ The bottles method worked a few weeks ago (although a lot of codes and mods didn't work) but doesn't seem to work anymore, the program doesn't seem to recognize the .yml configuration file provided in the guide anymore, I even tried installing the dependencies manually but the game (Sonic Frontiers) doesn't load the mod loader (the game launches but without mods), perhaps bottles doesn't use .yml files anymore ? The Steamtinkerlaunch method using Proton 7.0 also manages to install hedgemodmanager but once the mod loader is installed the game simply won't launch (I even tried providing mscore.dll but doesn't seem to make a difference). The method detailed on linuxgamingcentral.com used to work but now doesn't anymore, probably because steamtinkerlaunch now also tries to install .net 40 and .net 48. I get an error along the lines of "error, couldn't load mscore.dll to display the correct error message, please reinstall. Net". I'm losing my mind over this. Does anyone of you have hedgemodmanager working on Steam Deck ? If so how did you do it ?

Or maybe Steam Tinker launch (if using steam): https://github.com/sonic2kk/steamtinkerlaunch

This, right? This results in the following error:

Hey. I'm currently trying to get LiveSplit to run in the same Proton instance as a game (so I have the autosplitter available). I've managed to get that working by using SteamTinkerLaunch (https://github.com/sonic2kk/steamtinkerlaunch/wiki)

Click "Add Version", then install the latest SteamTinkerLaunch

Make sure to check the wiki on GitHub. It has a page for troubleshooting and the second entry sounds like your problem.

I recently had a nice discussion with the STL dev (steamtinkerlaunch#813). This might give you also a bit of insight.

There's steamtinkerlaunch for vortex/modorganizer there's also protontricks to mess around with each game proton prefix and etc. You'll have to Google these to get a better explanation but these are just the options I know of.

The "Metaverse" is a complete joke, and among gamers, Valve has a way better reputation than Meta. Why would they want to dilute that brand?

They already have their own platform (Steam), OS (SteamOS), VR headset (Index), their own Windows translation layer (Proton, https://github.com/ValveSoftware/Proton), their own partnership with cloud gaming (Steam Cloud Play using GeForce Now , https://partner.steamgames.com/doc/features/cloudgaming), etc.

IMO: As someone with thousands of games on Steam, there's no way in hell I'd want that linked to Facebook. I think they eventually removed the requirement to have a FB account to use a Quest, but they still require a Meta account. Yuck.

This reeks of Facebook recognizing the Metaverse as the failure that it was and opening it up because it's no longer relevant...

Or Valve's Proton[0], a tool for playing Windows games on Linux.

https://github.com/ValveSoftware/Proton

Did you mount it with the correct flags?

there is a hack to try and use your existing windows game install from an NTFS drive, but i don't recommend it as steam will try to save file names that are not allowed on NTFS...plus ext4 is faster.

From a quick search, here's what I found. It looks like you're encountering some common issues that can occur with games running on Linux through Proton, especially with the recent updates to games like Satisfactory that might affect compatibility. The log entries you're seeing related to D3DCompile2 failing to compile shader and the issues with Ternary operator and LinearToSrgbBranching not being defined, suggest that there's a problem with shader compilation. This can often be related to the version of Proton or the graphics drivers you are using. Some users have reported that the game does launch with the -vulkan option but with graphical glitches and lower performance, which indicates that the Vulkan renderer is working but possibly not optimally on your setup. From the discussions in the community, users have suggested ensuring that the latest drivers for your graphics card are installed and, if using an Intel GPU, that the Mesa drivers are up to date since Intel XeSS references were found in the logs. If you're using NVIDIA graphics, make sure you have the latest drivers and possibly set the PROTON_ENABLE_NVAPI=1 %command% to enable DLSS if you're under Vulkan. If you're using an Optimus laptop with both Intel and NVIDIA GPUs, make sure your Optimus setup is correctly configured. Some users have found success by specifying DXVK_FILTER_DEVICE_NAMES=GeForce to force the game to use the NVIDIA GPU. It's also worth noting that if you're encountering issues with DirectX 11, you might want to try forcing the game to use DirectX 10 if possible or look into DXVK configurations that could resolve compatibility issues. Lastly, if none of these solutions work, you could try running a trace with apitrace to gather more detailed logs that might point to the specific issue. If you're still stuck, it would be a good idea to report the issue to the Proton GitHub page or seek further assistance in the game's community forums where others might have encountered and solved similar issues. For more information and to find others who might have resolved similar issues, check out the community discussions on GitHub​​, Steam Community​​, and the DXVK GitHub page​​.