Andromeda
Published
%command% --launcher-skip -skipStartScreen --intro-skip PROTON_FORCE_NVAPI=1
Alt-tabbing kinda works. But I'd reccomend to switch with "super" rather than A+Tab
Save games are "marked as incompatible" but work.
It works slightly slower than on windows. ~10%
Rare crashes here and there.
I'd reccomend to tinker a lot witht his game. You can get some decent gameplay out of it. And it works well!
Also run FSR. It'll help a lot. Works well otherwise. I almost finished the (Don't fear) the reaper ending.
Depends a lot. Sometimes doesn't fullscreen properly. Sometimes does. It's not 100% the same everytime.
Some mods saved with save files might not load at all. Keep those in mind or start a new save.
Certain mods from the workshop might not work at all.
Launch it within proton. It's far better and gives you more options. I noticed far better stability and performance under proton rather than native.
Also for those with a g923 XBOX edition like me on arch: https://aur.archlinux.org/packages/logitech-g923-xbox-udev Someone setup udev rules that work insanely well! That with oversteer under proton makes it as playable as windows!
It was perfect. My gigabit connection worked perfectly with people from the US and europe the same way.
Enable proton and you're good to go!
Generally fun to play with smaller hiccups here and there.
Some smaller audio loss or entirely wrong audioclips. not sure if it's up to the game or proton related.
Sometimes the game start's lagging for no good reason until I restart the game.
It's a bit wishy-washy. Sometimes it does it sometimes it doesn't.
Certain lagspikes that didn't occur under windows. Yet to figure out why.
It runs as-well though it might need a bit longer to boot up, or require multiple launch tries till it runs.
mangohud WINE_FULLSCREEN_FSR=1 %command%
Very delayed. Atleast a second
Initial loading screen doesn't load if you tab out before it loads in.
It will just run worse as FSR is almost needed to get decent framerate
As long as you run it on vulkan and enable FSR to help out with framerate. You're golden.
About ~10% less performance than expected with the same quality settings.
Add this to enable FSR
WINE_FULLSCREEN_FSR=1 %command%
Good game. Tons of fun and works well on linux with no tinkering needed.
Most of the issues I assume were because of the netcode itself and not necessarely proton interfering.
Native works perfectly. Though expect help or official support to be "yeah won't fix" a lot. Sadly the dev's for whatever reason have a linux build but don't care about trying to make it work or follow linux conventions. Some notable stuff:
- Screenshots land in the root home folder
- "Wayland" issues are dismissed as they only support x11
- Crashes which won't be fixed (e.g. -> Export Save, marked as "won't fix")
Sad to see a dev be this stubborn about these issues. Esepcially if they build it natively for linux.
Other than that ran fine.
Extreme lag within ~ 1 hr of playing the game natively.
Occassional crashing even under proton.
Significant performance degredation in the hexagon mode after ~1 hrs of being in the save-file. Requiring a game-restart.
Don't use the native build. Some problems: The save file is in .config (why not .local? what the hell?) The in-game screenshotter saves into ~/ (Again, what?!) Frequent crashing requiring a system-reboot to fix it (it doesn't launch at all until I reboot) Various audio issues that were fixed by me forcefully pointing the game at the right device.(To be fair, I am on a weird setup, I don't blame the game, but other games do it far better..)
Conclusion: If you run into issues on native: Swap to proton and just take the performance hit. It's not worth running natively after that.
Game crashes and leaves with a kernel panic and OOM corruptions
Somewhere between 20 minutes and 6 hrs the game OOM's and causes a kernel panic afterwards. Same with proton. Works fine under windows but under my (up to date!) arch linux it crashes and misbehaves like cyberpunk 2077 and worse on launch. Conclusion: To play I dualboot onto a windows 10 install. This is also after 40 hrs of debugging and trying to find the issue with the dev's being decently unhelpful.
