Quoise
Published
mangohud %command%
Tested for 4+ hours with new world modifiers, events and race; but not new biomes (need to refresh to new cycle.)
Game still runs flawlessly on 1.8 pre- and post- day 1 hotfix: played 3 full P20 games. Using my save from before the update.
SteamDeck=1 %command% vk_xwayland_wait_ready=false %command% -PSOCompileMode=1
Wayland-specific problem when switching virtual workspaces, fixable with one of the commands listed
Performs Better and Significantly More Secure than Windows
- Performs better and more consistent than on Windows despite NVidia RTX 3070 (without even the config mod I used originally)
- No need for kernel level anticheats
- Consider turning on Steam Settings>Downloads>Under Shader-Precaching, allow "Enable Shader Pre-caching" and "Allow background processing of Vulkan shaders"; not sure what the caching time was, but give it maybe 20+ minutes (press "Play" and allow Steam to process Vulkan Shaders)
- Low tinkering: no need to touch the game folder, just swapped to Proton-GE and insert launch commands in Steam
- DLSS works
- Wayland-specific (you'll likely not need this) launch commands
vk_xwayland_wait_ready=falseso game doesn't suspend switching workspaces, as in multiplayer games otherwise, this will make your game act up or treat you as "disconnected" I elieve
Consider using Proton Runtime if Audio Issues Persist
Native (both from Steam; and AUR, bins and build) audio would just not work until I switched.
On Wayland+Pipewire@Arch, main recommendation is to use Pipewire-ALSA (failed to work for me.) Audio metres would show audio is playing, though my external DAC did not output sound. I'll look into trying other native Linux games, albeit Prism Launcher-Minecraft (Java) has worked flawlessly.
Summary
Looking online, my audio issues seem to be very configuration specific (low sample counts) and is considered difficult to replicate. I doubt most people will have this issue even on Arch.
Rainbow Floof Rating
Switching workspaces while in Wayland causes game to lag
Don't use Proton Experimental; just use default proton. Had my save get corrupted(?) when I set experimental as my Steam Runtime when I migrated and booted RnS.
Fixed most of my save stuff including charms, class unlocks from Windows dual boot; but not my gem and class stats before I noticed and backups caught up.
No errors (upon 1 hour of play)
Minimum graphic setting averages around 370FPS@1080p in the practice area (no enemy ships; GPU using OC and 90% power limit.)
- Mission 1 feels fine: if anything, I'm negatively biased attempting MKB controls, with my main controller being damaged (physically, not a game issue)
- Will likely come back to the game, replay campaign and update this review once I fix my controller/order a new one
Suggested Tweaks
mangohud %command%launch command works- PCGW method of disabling EAC works (seems to improve performance by >50fps? not sure if placebo.) This does remove the popup I see for EAC I see otherwise.
- If your PC can run it, I recommend minimizing TAA setting and just use supersampling for aliasing.
