mesa-dist-win VS dxvk

Go to the website https://github.com/pal1000/mesa-dist-win/releases and download mesa3d-23.3.0-release-msvc.7z, or whatever the latest version is. Just make sure it’s the release version. I assume either the MinGW version or the MSVC version will work, but I’ve only tried the MSVC version (and it's a smaller download).

The thing is, I'm only a little more smart than most normies and the instructions provided in the website aren't clear enough for me, so I figured out I could use a precompiled version of Mesa3D (if it even exists) for Windows for convenience sake. In my searches, I have found two Github repositories of pre-built Mesa3D drivers but I don't know if they're safe. (https://github.com/pal1000/mesa-dist-win) (https://github.com/mmozeiko/build-mesa)

all you need to do is download and run this thing called the "Mesa Injector"

The default WDDM driver provided by Microsoft for that GPU is a stripped down version of Intel's reference drivers without the control panel applet and the OpenGL dlls. The older Windows 7 driver will not install on anything newer because it is hardcoded to expect NT version 6.x. There were some patches released about a decade ago to fix this but you're better off running Mesa3D which re-implements OpenGL 3.3 in software https://github.com/pal1000/mesa-dist-win

I've managed to run Windows game (Homeworld Remastered) that uses modern OpenGL (3.3) on Crossover using Mesa Zink (OpenGL implementation over Vulkan) build for Windows that you can find here: mesa-dist-win. So if you check Homeworld Remastered or any other modern OpenGL game status on Crossover you will notice that it doesn't work. The issue is that Crossover OpenGL support is limited to 2.1 even if macOS itself supports up to 4.1. I'm not sure why but that means no modern OpenGL Windows games for us. This is where Mesa Zink comes to shine. Zink is Mesa (open source OpenGL/Vulkan/etc. and drivers implementations that are used by Linux and some other operating systems) driver that implements OpenGL on top of Vulkan. There is no native Vulkan on macOS but there is MoltenVK. I was curious if MoltenVK is good enough to run Zink and some big game and turns out it is. Homeworld is working fine and performance is good. I didn't play whole campaign so I can't promise it will work without any issues but I tested it in tutorials and Player vs CPU mode and it seems to work fine with only two minor issues - game will crash if anti aliasing is enabled and there is some minor graphical glitches with invisible ships.

If it's OpenGL-based, have you tried Zink? It was originally meant for Wine/Linux environments, but it should be in there as a normal DLL. It will redirect OpenGL calls to its own Vulkan-based compatibility layer.

i do wonder if you can use https://github.com/pal1000/mesa-dist-win to solve your opengl errors, ive only ever tried it in a vm though

Just gonna leave this here.

instead of 46 & 460 with my Windows drivers. So I think there is still something preventing your system from working. I would recommend you submit an issue and see if pal1000 or someone else can help troubleshoot the issue: https://github.com/pal1000/mesa-dist-win/issues

Try this like the Hiacenty did but for win https://github.com/pal1000/mesa-dist-win/issues/63

Someone is trying to game on them, or at least run DirectX apps in Linux, based on this PR: https://github.com/doitsujin/dxvk/pull/3795

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

Kid named DXVK :

DXVK versions after 2.0 require Vulkan 1.3 support, which may not be available on your GPU. Try using an older build, such as this one.

Give DXVK a try https://github.com/doitsujin/dxvk/releases, use 32bit d3d9.dll

What to download:https://github.com/doitsujin/dxvk/releases/tag/v2.3