Dr.Seuss
Published
mangohud %COMMAND%
mouse input would hang occasionally. The framerate was fine, as I could see on mangohud, but for a fraction of a second, the mouse would just... not send input. I could continue to walk around at these times, the keyboard was fine.
dropping mouse input frequently and for up to a second at a time, in a fast paced shooter like this, renders it totaly unplayable. it's a pity since it looks great, and runs at a rock-steady 60 according to mangohud, which I had to consult because the dropped mouse input felt so much like dropped frames. On closer inspection, the characer and world do continue to move around during the brief moments of dropped input, but it's still about as jarring as a huge lag spike, maybe worse because the game just goes on around you while you don't have control. I recently bought the game on sale because I wanted to play through it again on my newly aquired fancy graphics card, but at this point, I'd rather go back to my switch. I'll take a solid 30fps experience any day of the week over a jerky, laggy mess like this.
I tried several other proton versions, including experiemental, 7.0.6, and GE, to no avail. Fullscreen, windowed, and borderless windowed also made no difference. I might come back and try some other mice later (current mouse is G 203 logitech) and report if the results are any different, since that's the only other thing I can think to test
native is borked out of the box on ubuntu as others have mentioned. could have tried to fix the dependency issue, but experimental works flawless with 1 click, so that's the easy answer....
default proton, game launched but was not playable-- the screen was not centered, it appeared streched and seemed to have detected the resolution wrong, but there was no way to get to options to change this. with proton experimental worked great
Fullscreen required setting the window to fullscreen, externally of the game, in the window manager.
switch from native to proton
to get controllers to work, launch through big picture mode. launching from regular mode would cause the controller to stop responding after a few seconds
Native doesn't launch, works almost perfect with proton but i had to use big picture mode to get proper controller support
UI elements don't scale correctly in the native vesion fo the game.
As others have noted the UI elements are not correctly scaled on the native version of the game. However it otherwise runs fine and is totally plyable.
Game runs great & didn't require proton tinkering
in both fullscreen and borderless windowed, the game didn't like that I had two monitors. It wouldn't respond to input and refused to be focused. this was solved by just turning of the other monitor
OpenRCT2 runs native on linux and is great, fixes various longstanding bugs with the game and adds new features (like larger savegames with more rollercoasters)
Native, the game's borked. Proton works OK although it did crash on me at one point.
Crashes are not particularly frequent, but they are consistent. For example, using the card "poison strike" always crashed the game.
I tried various proton versions including experimental. They all have crashing, at least with the card "poison strike"; and, I also encountered a few other crashes not associate with that particular card, that I wasn't able to identify why they occured. Still, it's plyable in spite of the crashing, and as long as it doesn't randomly crash, everything else runs great.
Regular proton recomended by steam has frequrent crashes, as does proton experimental. GE does not have crashes.
There are crashes due to some visual effects when using some proton versions, specifically the current latest stable version recomended by steam which is 9.0-2 at time of writing, and in proton experimental. The crashes are consistent, triggered by things like the effects on certain cards, which makes those cards unusable. But, the same cards don't result in chrashing when using proton-GE, so try switching to that if you're encountering the same issue.
Audio bug is not a big deal. being unable to use modded buildings might be a dealbreaker for serious players.
audio sounds like it's underwater, pich down effect. happens in both win10 and win7 versions, but in win10 version it happens a lot sooner after launching the game.
steam cloud saves didn't work, and steam would get stuck in a loop where it even refused to turn off, because it was "finishing synchronizing cloud saves". This is a minor nuisance.
mod buildings menu crashed
Works almost out of the box, and is stable and performant, apart from the one crash. I don't care too much about the audio bug, since I can just put on other music. The mod functionality being broken is a big deal for me, though. I use a lot of mods.
Audio problems occur on the win 10 version of the game, but there are no audio issues on the win 7 executable, so always choose win 7
Some issues with mods and crashing that I reported previously seem to have been resolved since my last report. Game is overall very stable and playable on the windows 7 version but the dx12/windows 10 version still suffers from horrible audio distortion.
Only in win 10 mode. Win 7 mode audio works perfect
Some issues I've previously reported are now fixed, such as frequent crashing. Game is overall very stable but the audio problem in the DX12 version is very bad. Good thing there's a DX11 version that works fine.
