PlayableShow Details
Unknown
Works out-of-the-box and plays perfect.
DRI_PRIME=1 gamemoderun %command%
see problems for stability
game crashes whenever i alt tab
if on kde, whenever the game is not the main focus window it will crash, e.g. alt tabs. this makes it fairly unplayable if you only have one monitor.
The game in the native version kept crashing when I Alt-Tabbed. After switching to the Windows Version, everything went smooth
I would attribute the crashing to the early access stage of the game.
The game stutters a lot under proton GE. The native version runs perfectly fine but the constant crashing is kind of unbearable.
When the game is fullscreened, it crashed when alt-tabbing or whenever any other window is in front of it on KDE Wayland
Works out out of the box
Buy, download, play
Runs really well, stable frame rate on high settings.
Wouldn't launch on the default monitor I set but on the laptop monitor. I had to disable the laptop monitor in the OS display settings for it to launch on the correct monitor.
First time I launched it worked perfectly, I started it again a few hours later and the game would hang for a few minutes on each of the title screens, had to restart my laptop for it to start working normally again
Had some issues with shapes rendering but using vulkan through proton 9.0 solved that issue.
Game runs fine, just the glitches with the second monitore are anying, but the game it self runs really good.
Borders of Windows on second screen become wide black glitches, hard to grab them from there when game is running in fullscreen mode. Windowed not testet yet.
Just works
The game chooses the first audio device in the system's device list. If it isn't the one, you're using, you need to change it manually.
Worked out of the box. Changed to experimental, launched with Vulkan, and saw a huge FPS increase over DX11 and DX12.
Vulkan has the best performance for me (GTX 3060) and no issues outside of that. Experienced 1 crash but I think that was on steams end. I have played for around 18 hours with no issues. Both in Lutris, and in Steam.
Just done use Boxtron, Boxtron frikks your Audio in Shapez2. Runs like a charm. And use the Steam start menu for the game, there you can automaticly switch to Vulcan
Unplayable with this many crashes.
Audio worked on first launch. Once the game crashed for the first time audio no longer worked on the native version. Switching to proton fixes the audio. Audio is still missing when switching back to native .
Game ran about 1h on first launch then crashed, requiring a system reboot to recover. After that the game crashes within 10 minutes of startup every time, completely freezing the PC and requiring a hard reboot. This is true for native and all three windows verions under Proton.
native linux version works out of the box
no tinkering required, everything seems to be fine
Works good, BUT: bad stuttering until you restart the game + audio output disabling
The game disables all audio on game-start. Only switching audio output fixes this. You can then switch back. Changing volume does not fix this.
After 1h to 1h 30 minutes of continuous gameplay, the whole game starts stuttering. Only restarting the game helps.
Literally everything else works perfectly fine, but both of the mentioned issues need to get fixed. Cannot recommend the native version the way it is currently.
Game selects wrong audio device on start; fixed by using qjackctl
Game selects wrong audio device on native build; fix by selecting correct device with something like qjackctl
Shapez 2 automatically selects the first audio device, which is why you might not hear any audio. To fix, install "pulseaudio control panel" On Fedora: sudo dnf install pavucontrol. Then run pavucontrol, launch the game and select your prefered audio device.
wrong audio device selected, unable to change audio device without pavucontrol
Currently requires pretty beefy hardware to run at a smooth 60 fps, it's incredibly agressive on the graphics API so many iGPUs will suffer.
The Current patch, 0.0.7, has many known and fixed bugs in the beta 0.0.8, this includes the audio device selection bug present in 0.0.7
The popularity of the game's initial relaease as it is right now means the devs are flooded with bug reports, feedback, and spam. They cannot handle everything right now, especially the more complex your issue is. REMEMBER: if a bug is triggered in multiple games, its most likely not Shapez 2, it's an issue with your OS configuration. Do no worry if you're currently having issues running shapez 2, if you're using nVidia, I highly reccomend X11 as the display backend. Wayland support is perfect for AMD. Keep in mind this is EARLY ACCESS, expect bugs, broken features, and rough edges for quite a while before Shapez 2 gets a stable release. I've already tested beta 0.0.8, and my issues with 0.0.7 have fully dissappeared.
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.
Limited to 30 fps to save battery
No issues apart from a minor audio bug
Game selects the first audio device, which may not necessarily be the system default audio device. I have to change the application's selected audio device on each launch.
Adding another report to correct my previous report. I had mistakenly thought that the audio bug was fixed. It's not, the audio issue is still present.
Works out of the box
No issues to report. During the first few days there was a bug where the game selects the first audio device, rather than the one configured as the system default. A patch has fixed this issue, and the system default audio device is selected now.
gamemoderun %command%
Native version seems good, I haven't tested with a huge factory yet, but for now got a solid 110-120 FPS with ultra settings (and capped to 120 FPS).
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.
I have 3 outputs. For some reason the game sometimes selects random one on launch. This is easy to fix by just selecting the right output.
Great expirience OOB (out of the box). The game is surprisingly stable for the amount of stuff happening on the screen. If you played Shapez 1, this is a must try, especially with the 20% launch offer. And this is just an alpha test!
Controller Support could be improved
