daprice
Published
Like other reports have mentioned, choosing "UE4 No options menu" allows the game to start. I noticed occasional graphical glitches (parts of the screen would be blurred until I moved the camera) but don't know if those were due to Proton or the game itself. BeamNG export works if you first run ln -s ~/.steam/steam/steamapps/compatdata/284160/pfx/drive_c/users/steamuser/My\ Documents/BeamNG.drive/mods ~/.steam/steam/steamapps/compatdata/293760/pfx/drive_c/users/steamuser/My\ Documents/BeamNG.drive/mods (after having installed and launched both games at least once) to give Automation access to the BeamNG mods folder in BeamNG's proton prefix.
Does not stay in fullscreen or remember resolution across multiple launches
Clicking "Render animatic to disk" appears to work but the rendered file doesn't seem to be saved anywhere that I can find. Taking screenshots works but they are saved deep within Steam's internal wine prefix and do not show up in Steam or anywhere user-accessible.
Exporting to BeamNG does not work out of the box and requires fucking around with symlinks inside Steam's internal file system.
Works out of the box, performance is odd
With my setup, DX11 gets almost double the FPS of Vulkan. Surprising, since Vulkan is usually slightly faster.
40 to 60fps in most areas at 3440x1440 with low to medium settings. In some specific locations, it drops to 15fps regardless of graphics settings.
First launch took several minutes of a black screen with "Steam app ID 1086940 is not responding" dialogs appearing every few seconds, which I had to repeatedly dismiss. Subsequent launches have been nearly instant.
Even after Steam took 5 minutes pre-caching shaders, the game still did its own shader precaching that took just as long. That doesn't seem like it should have been necessary.
Performance is generally 60+ fps at high graphics settings except it drops down when GUI menus are shown; occasional crashes when changing/adding vehicles; can't load the Italy map (largest default map) without crashing after only displaying 1-2 frames (error 0x00000001); background processes are sometimes left running after exiting (part of BeamNG's crash reporter, I think, but Proton seems to hide its system tray when the main game is closed so there's no obvious way to interact with it other than manually killing the process)
Logitech Momo Racing wheel is detected and can be used as an input, but there is no force feedback on any setting. Changes to controls require a restart of the game for them to even show up in the GUI.
Update on the steering wheel force feedback that I couldn't get working: I discovered that if your default vehicle is specifically a non-power-steering variant of the Gavril Vanster (Drift Missile or Off-Road), force feedback works, but as soon as you change your vehicle to something other than those two (even if you change back) it is broken until you restart the game. This means that to get FFB, you have to go to the Garage, load up one of the two vans, set it as the default vehicle, exit and reopen the game, then play free roam or one of the scenarios that uses those variants of the Vanster. I have no idea why this is the case -- I believe the game normally supports force feedback on all vehicles.
Steering wheel force feedback doesn't work even tough the game showed my wheel as supporting force feedback
Menus and campaign cutscenes are extremely laggy but gameplay is fine
Some changes to control mapping don't take effect until the game is quit and restarted
Borderless fullscreen works fine, just not "true" fullscreen
Force feedback does not work on Logitech Momo wheel even though it should be supported and works in other games
Newly mapped controls don't always appear or work until the game is restarted
Using the feature to drive cars imported from Automation does not work unless you manually make some symbolic links between convoluted Steam file paths
Just don't alt tab out
After alt-tabbing out of the game, I could not alt-tab back in. Attempting to do so caused a momentary black screen and the game would not stay focused.
As long as you don't mind waiting longer than other Proton games for it to launch
Game runs fine once open, but Steam processes Vulkan shaders for 5+ minutes on every launch. Game also freezes on launch for 30 seconds or so before showing main menu.
Music crackles during the intro but all other audio is fine
Occasional frame drops when many entities are on screen
Crashes usually occur when disassembling a part or when a part goes into the processor, which is also reported by Windows users, so probably not Proton related.
Video cutscenes (such as before the main menu) get stuck on either a white or black screen, but are not essential for gameplay and can be skipped by pressing enter/escape.
Mouse works as expected with no drift or sticking issues, framerate is decent. With Proton 4.11-1, it works fine with a Logitech Momo Racing wheel, including force feedback (I didn't touch the controls in the Unity launcher, just within the game). Pedals need to be held before assigning their axes as suggested by the text on the game's configuration screen. I disabled all dead zones, set wheel rotation to 240 to visually match the Momo wheel, turned on force feedback with multiplier and clamp both set to 100, and force invert on. Buttons and shifter can be assigned as desired.
I tried d9vk as another report suggested (with the game's "Golden Eye" graphics setting) and it caused shadows to glitch out, especially inside the house, although it did slightly improve framerate and reduce CPU load. With the default (i.e. not d9vk), there are no graphical glitches and performance is still acceptable.
Turn off Steam Cloud before playing! Back up your saves!
Logitech Momo racing wheel: Even with new-lg4ff driver, only half of each axis works, the other half randomly sends minimum and maximum values and cannot be mapped properly, making it unusable. No idea if the game supports this wheel on Windows, so may not be a Proton issue.
Steam Controller with "Driving with Faux Wheel" community configuration (I'm using tilt controls!) works well, except the Steam Overlay "controller connected" notifications cause the game to freeze for a second when they appear, and the gyro needs recalibrating almost every time I pick up the controller.
Steam Cloud corrupts saves if enabled.
Just having the Steam Overlay enabled reduces fps, but is necessary for the Steam Controller to work in the game.
Maybe 1 in 20 times, quitting the game from the main menu crashes the entire desktop environment and/or Steam will think the game is still running until its process is manually killed. This is reproducable on multiple machines.
If you want to use a steering wheel, use proton 6.3.8 and the game's beta branch for controller mapping
Logitech steering wheel (including FFB) only works with the game's controller beta branch, Steam Input disabled, the new-lg4ff driver, and proton 6.3.8. It's completely unusable with any newer or older proton version.
After the Beyond update, NMS crashed on loading a previous save. I was able to create a new save and turn down the graphics options to the Enhanced preset, which also caused a crash but allowed me to load my old save again after relaunching. Performance is horrible compared to pre-Beyond, ~30fps with minimum settings and 15-20fps with Enhanced. Any higher presets are unplayable and may immediately crash the game. Before Beyond (but also with older Proton versions so I don't know which thing caused the performance difference), I usually got ~60fps with relatively high settings. Psensor shows low to no CPU or VRAM usage while playing, but GPU usage maxed out (pre-Beyond, it would show very CPU and mid-to-high GPU and VRAM usage). I have not yet tried any tweaks other than the settings within the game.
I opted into the game's Experimental branch in Steam and it resolved the graphics performance issue. I now get ~60fps on High settings with only occasional minor stuttering. The game now uses VRAM and CPU effectively.
Audio sometimes crackles when many sounds are playing at the same time.
Stutters a lot but might just be my CPU not keeping up. Very rarely, drops to 1fps until I alt-tab out and back in which fixes it(???)
The game froze once and had to be force quit, but this seems to be very rare.
Occasionally loses connection to multiplayer and/or discovery services.
Only occasionally crackles. It's fine most of the time.
Since the July 26 Steam client update, steamwebhelper frequently uses 100% of a CPU core, which causes the game to lag. Are we really supposed to buy a CPU with more cores than we need, just so Steam can consume one while it sits idle in the background?
The game froze once and had to be force quit.
Sometimes the game still shows as running in Steam forever after quitting it, and has to be manually stopped.
Both joining Steam friends' games and just running into people during the expedition work perfectly. Any occasional disconnects I've ever had were probably caused by the game's servers
Don't trigger the Steam Overlay! Valve, fix the Steam Overlay, it causes a different problem for every game in Proton!
Using the Steam Overlay web browser (e.g. to read the discussions for the game) causes the game to run extremely slowly upon closing the overlay, even after the web browser is closed.
If the Steam Overlay is not used, performance is perfect.
Game froze once while playing (no obvious cause) and had to be force quit.
Only the first few minutes work and then it crashes Xorg.
The loading screen after clicking the linking book causes Xorg to crash, which kills all open programs and logs me out of my PC.
Tested using the demo
Decent FPS on high and extremely infrequent stuttering despite not meeting CPU requirement
Audio in Cyan intro animation plays at normal speed while video plays in slow motion. Audio sync is fine after game is started.
Shadows don't always cover the bottom two rows of pixels, causing a bright line at the bottom of the screen in some scenes. Cyan logo intro plays in slow motion.
Updating OS and switching to Proton 9.0-2 fixed the crashes I was having before.
Steam Cloud lost my save.
It's been two years since they released hardware that literally depends on Steam Cloud, you'd think they would have fixed it by now.
Sometimes the mouse cursor turns invisible in menus
I've gotten past the starting area and haven't experienced any of the slowdowns or audio issues that others have reported. ~100fps at 3440x1440.
Haven't tested for long but seems good so far.
Far LOD trees look very different from their closer up versions, causing a slight but noticeable pop-in like effect. Also, shadows sometimes have weirdly cut off edges. I don't know if these issues are specific to Proton.
The default mouse smoothing results in annoying input lag, but disabling smoothing eliminates it in game. In menus (but not during gameplay), mouse cursor lags by ~0.2s and has awkward acceleration regardless of mouse smoothing setting or OS mouse acceleration setting (I have it disabled).
I get smooth >60fps @ 3440x1400 wandering around the starting area with the default (mostly ultra) settings, but only if the game is set to use DX12. If the game is set to Vulkan, I get lower FPS, frequent stuttering, horrible screen tearing regardless of vsync/gsync, and severe input lag. I don't know if these issues are caused by the game's Vulkan renderer, or by Proton. Again, none of these issues occur with the game's default DX12, just a heads up in case you expected Vulkan to work better on Linux.
This review is for game version 0.5.1.10 - build 177909.
If using Vulkan, the game doesn't quit on its own and has to be stopped through Steam or task manager.
Connecting to a Steam friend, game gives warnings about "TBD NAT" no matter how anyone's network is set up, but seems to work fine except for known bugs in this Early Access version.
Nvidia 510 driver fixed the previous issues I had with Vulkan. Vulkan (selected in game's settings screen or using command line option) now performs slightly better than DX12.
Factory sounds occasionally make crackling/popping sounds when using the aptly named Pop_OS 22.04; they did not when using Pop_OS 20.04.
For every launch of the game, there's about a 50% chance that Nvidia Gsync won't work, resulting in game-breaking stuttering and screen tearing even if Vsync is enabled. This issue was previously fixed by Nvidia 510 drivers, but now it's back.
gamemoderun %command%
Lots of audio crackling/clipping when near sound-producing machines, otherwise fine
Frequent game freezes and crashes when playing a multiplayer game hosted by someone else. No issues when hosting or playing single player.
Game always warns of NAT issues even when NAT is open, but works fine anyway. Frequent crashes that only occur in multiplayer.
Using Vulkan instead of DX12 adds 10fps, but the game's Vulkan support is extremely buggy and only works for about 10 minutes before glitches make the game nearly unplayable (known game issue, not Proton-specific). DX12 still performs ok and is 100% reliable.
Mostly fine
Game froze immediately after stepping out of the drop pod the first time. Worked fine after force quitting and relaunching.
My computer crashed once while the game was open (the game did not cause the crash), and somehow this reset all graphics settings in the game to their lowest possible values.
Shader precaching took >30 mins but there was still a brief hang every time a new graphical effect happened, like the cached shaders weren't being used.
-vulkan
~60fps with Vulkan on High preset, ~30 with DX12. Blowing up a rock with Nobelisk causes the FPS to drop to the single digits for several minutes, but it recovers when the debris despawns.
If the Steam window is open at the same time as the game, the shimmering effect around achievement icons in the Steam UI cuts the game's FPS in half.
Game crashed once on first start but has been fine since.
Steam spends 10-30 minutes processing Vulkan shaders on every launch. The pre-cached shaders don't appear to be used by the game, which stutters the first time any shader is used. Pressing "skip" on the Launching dialog resets progress to 0% instead of skipping shader processing.
-vulkan
Works ok with analog output, but audio over Displayport cuts in and out with a lot of popping and static. They don't call it Pop!OS for nothing. Increasing pipewire latency helps but does not fully fix it, and adds noticeable audio lag.
Metallic finishes from the AWESOME Shop only reflect black. Other materials like glass and water reflect correctly.
"Windowed fullscreen" works fine, regular fullscreen only takes a small portion of the screen.
Vulkan performs well, DX11 and 12 do not.
Seems to have a memory leak and freezes after 1-2 hours when it reaches 8gb despite plenty of available memory. Is it not running in 64 bit?
Upscaling settings revert to preset every launch, so I have to change them every time to get decent performance.
Video cuts out every few seconds (monitor totally loses signal) if Gsync is enabled.
Steam is too buggy on Linux for this to work well
Had to increase pipewire buffer size, which adds noticeable lag. Default audio system settings caused audio to cut in and out with lots of static.
Ambient lighting and reflections on metallic surfaces are totally missing in Vulkan, but work in DX11/12 with the same settings.
Had to use windowed fullscreen
Steam wants to spend 30+ minutes(!) compiling Vulkan shaders on every launch, the skip button doesn't skip but just resets to 0, and the game still stutters every time a new shader appears, as if the cache isn't being used. Had to turn off shader caching in Steam entirely and live with the stuttering, which gradually goes away after several minutes of gameplay. Vulkan performs significantly better than DX12 but seems to be missing shaders/textures.
If I sit on the main menu for longer than 30 seconds (e.g. waiting for a friend to start multiplayer) the game freezes.
Steam overlay does not allow inviting friends or joining friends' games. Only option is "invite to watch". Had to enter the session ID manually + game would freeze on the menu if I didn't type the session ID fast enough. After joining, worked fine except combat was laggy.
Runs perfectly with no crashes that I've encountered. Lags slightly in large cities, but it always did running natively, too. Works great at ridiculous resolutions the game designers never predicted using the launch options "-CustomResolution:enabled -r3440x1440x32" (replace 3440x1440 with your own resolution). Add "-intro:off" to skip the long intro. I tried lowering the CPU count as others have suggested, but that made performance worse so I left it at the default. Works with mods, but they'll need to be installed in ~/.steam/steam/steamapps/compatdata/24780/pfx/drive_c/users/steamuser/My Documents/SimCity 4
50-80 fps on high preset at 3440x1440. Every mouse-related input causes a slight drift of the view down and to the right, but it's possible to compensate for (severity depends on mouse sensitivity setting and mouse DPI). Also, after about 30 minutes of gameplay, the mouse becomes locked to the center of the screen in menus; alt-tabbing out and back in after entering the menu allows normal cursor movement until you exit the menu, upon which the view will go crazy, then you can alt-tab out and back in again to regain normal control (this workaround is annoying to have to do every time you use a menu but the game is still playable).
runs perfectly out of the box
The issues that were there previously (mouse cursor getting stuck, mouse drift, minor performance issues) are now 100% fixed through a combination of game and proton updates.
This suffers from the mouse drift issue common to many Unity games including the original Subnautica (view moves down and to the right with every mouse input) but that's minor. I haven't yet encountered the stuck cursor bug that occurred in the original Subnautica under Proton. Performance is lower than the original game with the same settings, but that's to be expected as the game is in early access and lacks optimization for now.
