Andreas Spanakis
Published
for those that dont have directx11 installed in their wine app, just use launch option [PROTON_USE_WINED3D=1 %command%] and you are set
initially there was an error, the game aasked or DirectX i used PROTON_USE_WINED3D=1 %command% as launch option and it works perfectly
PROTON_ENABLE_NVAPI=1 %command% --intro-skip -skipStartScreen --launcher-skip -dx12
Single crash after about 7 hours of game. Settings on high and enjoying 55-65 fps. Play smooth so far.
PROTON_ENABLE_NVAPI=1 %command% --intro-skip -skipStartScreen --launcher-skip -dx12
latest proton vertions work after you create your character
plays ok as long as i tested it (less than 30 min) - crappy game couldn't pushe myself to play more
PROTON_USE_WINED3D=1 %command% this custom launch option used to launch and play the game normally
needs fixing
load the game? yes see menus? yes start game? yes view intro? yes finish tutorial? no
game opens up, play into dialogues - all well here but on first battle (in tutorial) the game stops responding. I can move the camera only (no problem here) but mouse commands are unresponsive. Click on anything or anyone does nothing tried to force dx11 or dx12 - nothing
has minor memory issues that may cause the game/pc to freeze. But other than that it plays perfeclty
game crashes every 10-15 mins (assuming memory issues - pc freezes and become unresponsive)
You need custom proton build - the one found here https://github.com/GloriousEggroll/proton-ge-custom 5.9-GE-3-ST
PROTON_NO_FSYNC=1 %command%
tried Experimental, but failed to launch. Tried Proton GE 7.1 but also failed to get past the final tutorial mission. Reverting to previous proton 6.3 allowed me to play for an hour. Not sure yet if the PROTON_NO_FSYNC=1 is usefull.
ignore DirectX, use Opengl + VSync + Full widow + default setings (everything on high) and played the firdst mission without any issue.
only minor problem is there are no FMV, only white screen, with sound. Hit ESC to bypass these and you can play normally.
sometimes the ship will collide/merge with a nearby object. I am guessing this has nothing to do with proton, but its a "bug" of the game engine itself (not sure though, since i have not try the windows version)
PROTON_USE_WINED3D=1 %command%
