Alec H.
Published
Won't launch OOTB, makes it to an infinite loading screen using a funky launch option. Either way, unplayable.
This is due to a messy proton initialisation where certain launch strings are interpreted in proton as Linux command shell redirections.
However, by placing the launch option eval "$(echo "%command%" | sed 's/+connect.*$//')" inside the launch options menu, the game will launch, and it'll be able to go through the first time launch prompts (Language, Tutorial prompt).
Afterwards, the game will throw an error in the top right stating it can't connect to the proprietary voice chat servers, and it'll be stuck in an infinite loading screen.
Unfortunately, this game is borked.
Until this changes, Dual boot or use KVM.
Proton-6.21-GE-2, Disabling Mangohud
On the first launch after installation, the game would take a while, then would crash upon startup.
Reading through the github issue comment regarding the protontricks workaround, I found that attempting to run mangohud over this game might cause issues. Putting "MANGOHUD=0" in the launch options to override my global mangohud setting fixed the launch issue.
Though you could probably get away without using GE, I've also heard that there would be cutscene errors with vanilla proton, so I recommend running this under Proton GE.
So far 6.21-GE-2 has been stable for my playthrough. Use other versions at your own discretion.
gamemoderun %command%
Audio Tracks currently missing from intro cutscenes (Company Logos), animated cutscenes.
Something about the colors and lighting feel sorta... off. I don't know how else to describe it. Maybe I'm just crazy.
Game stutters and is generally unstable in windowed mode, change to fullscreen ASAP to prevent crashing.
Crashed the first two launches, likely intertwined with the windowed mode issues.
With all the caveats, I will hold off playing this for now. At least until a solution for decoding the cutscenes audio becomes available.
With minimal tinkering and some strategic planning around small bugs, I had a great time.
gamemoderun %command%
Not sure if thats a linux problem, but the campsite map was notably more sluggish than the other maps we played on, getting ~60 fps rather than 100+ fps on the house-like maps. Most certainly not a deal breaker.
The desktop may seize for a brief moment when moving in and out of loading menus with varying degrees of severity. A bit jarring, but it never caused any crashes.
I didn't try to replicate the spirit box voice recognition bug, as the consensus is that its borked due to it being based on Cortana. (Here's a guaranteed solution: have Windows friends take care of that for you ;) ) Everything else worked buttery smooth.
NOTES:
- The last time I played this title on Linux, the game had severe performance issues. However in recent months I had tinkered with gamemode and enabling shader pre-caching for all titles. I assume one of or all of these tinkering methoded solved the performance issues.
- Before setting the gamemode launch option, you'll need to install the gamemode package. All major package managers have it.
- I never attempted playing through the VR mode, as I do not own such hardware. Previous reports say the latest update borked it. Use VR mode at your own discretion.
Pleasant experience if you're on KDE, determined and use this software like I do, but not for the faint of heart.
Using KDE, follow the instructions on how to install and use Wallpaper Engine Plugin for KDE
Even when all the plugin libraries are installed properly, not every Wallpaper runs as intended. Its a hit or miss, but a general rule of thumb is that most simple wallpapers (Mostly 2D) work completely normal, more complex wallpapers employing multiple layers have slight artifacting and/or missing textures, and highly complex 3D models have heavy artifacting or do not appear on screen at all.
Changing the properties of a customizable wallpaper can be finicky; you have to go into the wallpaper json config file (in the wallpaper plugin menu, hover the mouse over a wallpaper and click the folder icon) and manually find the setting you want to change.
Rarely, on startup or if when you're updating the plugin improperly (Examples being when new dependencies pop up for updated builds on GitHub), plasmashell (the desktop panel) doesn't load properly, leaving the system frozen on a static frame of the wallpaper. A restart of the system or a proper update to the plugin will 9/10 fix this.
MISSING FUNCTIONALITY IN THE APP
Connecting to android mobile devices doesn't function (Likely a driver and/or firewall issue.)
Exporting a pre-rendered .mpkg for use in the android app fails (Transcoding issue.)
Creating wallpapers in the editor is buggy ("Works" in theory, but its not a good idea. From the 10 minutes of testing I did, its slow and glitchy.)
WORKING FUNCTIONALITY IN THE APP
- The downloading/installing function itself runs normally under proton.
