if it's DX9 game try -force-d3d9 in launcher, or try to play with/without esync - PROTON_NO_ESYNC=1

running mirror's edge now just to test it, running fine for me (ryzen 1700, gtx 970:396.54 linuxmint 18.3) 1440p, high gfx 60-70fps

Originally posted by Cat on Linux:

if it's DX9 game try -force-d3d9 in launcher, or try to play with/without esync - PROTON_NO_ESYNC=1

Thanks! PROTON_NO_ESYNC=1 seems to get Path of Exile running. With it, I was prompted to use dx9, rather than the game just shutting down without message. -force-d3d9 did not help, when I last tried a few days ago. I removed PROTON_NO_ESYNC=1 from launch options to see if it would fail as before, but now Path runs without it. Which is why I said "seems," since I can't tell now if something else didn't change in the last few days to cause the prompt. Or else I reckon the game just had to start right once to get the dx setting set correctly.

Originally posted by Dѻѻm:

since I can't tell now if something else didn't change in the last few days to cause the prompt. Or else I reckon the game just had to start right once to get the dx setting set correctly.

They rolled Proton update with 23th Aug update, now it can use 2 Proton variants, so maybe game in question got fixes in updated Beta.

Strange i am still prompted to use directx 9 in Path of exile.

I did many hours of experimenting with this about 3 or 4 months ago and found that there is also, in my opinion, a 64 bit issue as well. I was experimenting because I wanted to get my 64 bit version of Skyrim to work in Linux. I learned that there where those who got there older 32 bit version of Skyrim working so why not my newer version? I found that I could get almost all my older 32 bit Windows games to work in Linux but none of my newer 64 bit games would work.

Since that time I have read of those getting the newest Doom to work and I know that steam has even gotten a few of the newer, (the newest Tumb Raider comes to mind) 64 bit games to work in Linux. I know others have mentioned that it's a Direct X issue but I also think it has to do with how system demanding these newest 64 bit games are. My opinion.

Originally posted by shellback84:

I did many hours of experimenting with this about 3 or 4 months ago and found that there is also, in my opinion, a 64 bit issue as well. I was experimenting because I wanted to get my 64 bit version of Skyrim to work in Linux.

what is 32 bit and 64 bit Skyrim? do you mean Skyrim original and Skyrim SE? they are not platform dependent, it's rather DirectX standard that makes Original to work in wine (used Dx9) and Special Edition with DX12 has very little chance to work because at the moment not every instruction in DX12 translated to mono. it's still DX issue, there's no platform dependency.

Originally posted by ripper81:

Strange i am still prompted to use directx 9 in Path of exile.

when exactly that happens?

64 Bit Skyrim is SE, released in 2016. The 32 bit version of Skyrim was released in 2011. BTW, I got Elder Scrolls 4 to work great under Linux and it is 32 bit. Anyway I am not saying Direct X is not an issue. What I am saying is I think the newer 64 bit games are much more resource dependent then the older 32 bit games. I tried a lot of different games from hard copies to downloadable games. I got about 90 percent of all my Window 32 bit games to work in Ubuntu 16.04. Not one of my newer 64 bit games worked. Zero. I am not going to do a huge write up about this because I think 90 percent of the people out there do not read those huge write ups some people do and spend to much time writing. But I can assure you when I say, I spent hours and days on it.

I did this because I wanted my 64 bit Skyrim to work in Linux because I was wanting to get rid of Windows. I love Linux and wanted to use one operating system rather than two. You can see my frustration because I got 85-90 of my other games to work except for the one I love the most. I would do away with windows in a snap if I could only get Skyrim SE to work.

Since TESVSE uses DX11 (whoch still remains incomplete and utterly slow within wine's Open GL translation) soes require the newer DirectX over Vulkan DXVK override, which simply put converts from DX11 to Vulkan rather than OpenGL. Let us not forget that OpenGL temained backwards compatible until versions 3.x , version 4.x is not, and is up to the driver to allow for older standards, which is in part why conversion of DX11 to OGL was taking so long and was so slow. DX11 correlatea roughly to OpenGL 4, and Vulkan actually implements much of OGL4 functions, which is why, uaually OpenGL 4.5 capable hardware is Vulkan compatible. Since Vulkan is much lower level than OpenGL, it has many advantages to it, but the bulk of these for all intents and purposes is that it is intrinsically multithreaded (yes OGL 4.5 is too, but through the use of extensions, albeit core extensions, not intrinsically), which helps yielding faster performance for similar workloads, another thing that helps Vulkan is that it can be paralellized in its execution, which, though possible in OGL, it has greater overhead, hence VK is faster, so DX110+ over VK is much faster and its only limitation would be the available drivers on the host.

Also, this means that Apple is "compatible", through the use of MoltenVK, which is Vulkan over Metal, since the lateat OGL version macos supports is up to version 3.3, despite the hardware being capable of higher spec OGL.

At any rate, support for TESVSE was not fully possible with vanilla wine's DX11 implementation due to a number of factors, paramount of which is its lacking D3D11 state, but that was addressed, albeit only "recently" with DXVK.

Skyrim Special Edition runs beautifully with DXVK. Sure there are some quirks, especially with sound, and Proton, which makes use of DXVK runs it equally fine.

DXVK is growing in complexity as it has incorporated into it DXUP, an effort to point DX10 implementation to DXVK, in order to run DX10 over Vulkan (well, over DXVK), and VKD3D for running DX12 over Vulkan.

TL;DR: you could only get TESVSE to run in wine with the use of DXVK until fairly recently, and DXVK is part of Proton in Steam Play now. Both Wine and DXVK have come a long way, and now both projects enjpy the auspice of Valve as well, which as the implementation matures, will only yield greater games compatibility, especially useful for the Steam Play usecase here are application profiles recently introduced into DXVK.

Originally posted by Cat on Linux:

Originally posted by ripper81:

Strange i am still prompted to use directx 9 in Path of exile.

when exactly that happens?

It happens when i start Path of exile after installation. The game gives me a row of errors. The only thing you could do is to click on the ok button. If you do that until the last error the game gives you the option to start in directx 9.

Originally posted by ripper81:

Originally posted by Cat on Linux:

when exactly that happens?

It happens when i start Path of exile after installation. The game gives me a row of errors. The only thing you could do is to click on the ok button. If you do that until the last error the game gives you the option to start in directx 9.

Did you happen to try to run PoE right after the beta was released, like first or second day? Because if its giving the prompt/row of errors now, and you didnt try it then and aren't using the esync command, its possible the update fixed this. If you did and the prompt/row of errors showed up then too, idk what was wrong in my case. Mine would get to the point it would finish installing its Microsoft-whichever packages for the first time run, then suddenly would quit with no mesage with the button I can now push to choose dx9. I don't recall any error messages with okay buttons. It would just silently quit.

Originally posted by Dѻѻm:

Originally posted by ripper81:

It happens when i start Path of exile after installation. The game gives me a row of errors. The only thing you could do is to click on the ok button. If you do that until the last error the game gives you the option to start in directx 9.

Did you happen to try to run PoE right after the beta was released, like first or second day? Because if its giving the prompt/row of errors now, and you didnt try it then and aren't using the esync command, its possible the update fixed this. If you did and the prompt/row of errors showed up then too, idk what was wrong in my case. Mine would get to the point it would finish installing its Microsoft-whichever packages for the first time run, then suddenly would quit with no mesage with the button I can now push to choose dx9. I don't recall any error messages with okay buttons. It would just silently quit.

I have tried the eyesync command and switched the proton version. The Outcome remains the same. But i can play POE on Linux at least. This might have somoething to do with the nvidia driver.

I found a solution in this post to playing AvP 2010 on Linux. Apparently after another "helpful" update, the entire thing quit working correctly today (I played it yesterday without problems, now ANYTHING that requires older versions of DirectX seems to not work correctly, at least on my machine).

https://gtm.you1.cn/app/221410/discussions/8/1629664607001626033/?tscn=1719973512

The thread is 6 years old, it is effectively irrelevant today. All directx games just work. I played elden ring just few hours ago with zero tinkering