jerb
Published
Gameplay works fine, but the game will give an access violation upon exiting, and Steam still sees the game as running.
As other reports documented, replacing Launcher with the Borderlands executable allows the game to work.
Invisible characters are due to the lack of Stream Output support in drivers- use Mesa 18.3-git or Nvidia 396.54.09 to avoid this.
In my case I'm not using Mesa 18.3 until the first release contestant, so disabling D3D11 and falling back to the D3D9 renderer is necessary. When these drivers are more commonplace, the game will run perfectly out of the box.
Game launches, but the controllers do not appear in the VR space. Tested with Index controllers.
Very fluid experience overall.
Occasionally the mouse would not appear after completing a level- easily worked around by alt-tabbing, not a big issue.
Game launches and runs out of the box, however there is extremely heavy stuttering to the point that the game is almost unplayable. Setting RADV_PERFTEST=aco %command% significantly reduces the stuttering. I can only assume this is related to shader compilation, and Steam probably doesn't have a shader cache for this game yet since it just came out.
Game does not render properly. Both eyes are displaying on the left lens.
I'd recommend using Proton-GE and setting DXVK_ASYNC=1 to eliminate shader compilation stutter, but this is absolutely not necessary to play by any means.
The only issue is that the frame limiter doesn't apply until you go into settings and re-apply it. I have never ran this game on Windows, so I am unsure if this is a bug with Proton, or a bug with the game. Otherwise the game runs perfectly on my RX 580.
Performance has significantly improved since I last made a report for this game. My 580 has gone from hitting high at 60 to running perfectly at 75 with everything except motion blur maxed.
Install vcrun2019.
All settings set to off, except for textures, which is set to medium.
Some of the HUD is small.
This is a downside with the Verified program- it doesn't account for game updates.
Following the 1.7 update, the game no longer functions out of the box. vcrun2019 needs to be installed in Protontricks, which changes the emulated Windows version to 7 as well.
Protontricks needs to be installed via Discover, then Redout needs to be selected. Install vcrun2019, then change the setting back to win10.
Good news is, based on my (very) limited testing, the new DX12 renderer is more performance (and therefore, better on battery life) than the game's old DX11 renderer.
Install vcrun2019.
Following the 1.7 update, the game no longer functions out of the box. vcrun2019 needs to be installed in Protontricks, which changes the emulated Windows version to 7 as well. Change the setting back to win10 or the DX12 renderer will be nonfunctional.
Good news is, based on my (very) limited testing, the new DX12 renderer is more performant than the game's old DX11 renderer.
Runs like a dream maxed out on my RX 580, hits 1080p@75 no sweat. No tweaking was required.
The reason the launcher doesn't work is because it's a .NET application that depends on Windows Presentation Framework, which Mono doesn't implement, and Proton doesn't implement by default as a result. The solution is to install dotnet40 with Protontricks.
Game works perfectly, it's just the launcher that requires this tweak.
Could just be a thing with i3, but occasionally when tabbing out and back in the screen would be black. Repeating the process allows the game to display properly again.
I haven't played this game on Windows, so it could just be a matter of the game being in Early Access, but I do get crashes every now and then.
(Ignore my previous report, had the wrong system specs.)
Could just be a thing with i3, but occasionally when tabbing out and back in the screen would be black. Repeating the process allows the game to display properly again.
I haven’t played this game on Windows, so it could just be a matter of the game being in Early Access, but I do get crashes every now and then.
WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command%
Game does not consistently hit 144FPS. Likely a game problem instead of a Proton deficiency.
Videos can be fixed by setting WINE_DO_NOT_CREATE_DXGI_DEVICE_MANAGER=1 %command% as a launch option as I've detailed. This is common for a lot of newer Unity games, so if you see video degradation similar or identical to what Turbo Overkill has, give this a shot. If it works, Proton is internally maintaining a list of games that have this problem and is overriding this automatically as-needed. Turbo Overkill is not on the list yet, but I submitted a pull request for this and Slayers X: Terminal Aftermath: Vengeance of the Slayer's demo, so hopefully it's in the next release.
