wine-mono VS Proton

2) Personally, I follow these directions, which I got from the above ProtonDB link to play Elite Dangerous.

1) I need .NET framework for WINE which is this https://github.com/redmcg/wine-mono but I can't use protontricks if the game hasn't been launched at all, which is the case here.

If possible use Steam / Proton. Depending on the version of Proton there are steps to take to get Mono working, which the launcher needs. https://github.com/redmcg/wine-mono/wiki#with-protontricks

Hello, I urgently need help with a problem that is not allowing me to install and play odyssey on Linux, even following the instructions for installing custom wine-mono for the game described by Brendan McGrath: https://github.com/redmcg/wine-mono/wiki. I have the following problem: I can open the game launcher and press the button to install odyssey, however, the launcher closes randomly, even when downloading the update (when I'm saying "download the update" it is in the state that "syncing files" appears), which makes me not complete the installation and thus play the update. However, I can play Elite: Dangerous Horizons, without any problems. My distribution is Manjaro, the customized version of wine-mono is 6.1.0_ED (I have already tried 5.1.1.2_ED), and I have also tested all recent versions of Proton, including the customized version proton-ge-custom: https://github.com/GloriousEggroll/proton-ge-custom/wiki. I appreciate it if you can help me in any way, I really love Elite and would love to try and play this wonderful new expansion.

I'm stuck on proton 5.0-10 because when I try any newer version my EDTracker is not detected. I just tried again with 5.13-6 and GE 6-5-GE-1. No EDTracker. As soon as I go back to 5.0-10 it works fine ? But while doing this I upgraded to wine-mono-6.1.0_ED (https://github.com/redmcg/wine-mono/releases). I was on wine-mono-5.1.1.2_ED before. The launcher seem more stable now. Could well just be luck :)

To use the latest Proton 5.13, a specific version of mono is needed: https://github.com/redmcg/wine-mono/wiki#with-protontricks

It's a mono issue follow this guide: https://github.com/redmcg/wine-mono/wiki

https://github.com/redmcg/wine-mono/wiki#with-protontricks

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​​.