VerifiedShow Details
Unknown
Some small text
Game runs exactly the same as on windows with a slight performance boost but there is a problem with the game itself where the longer you play the worse the performance becomes but it was exactly the same when I used windows
Below 30fps frame rates
No additional bugs on Linux, works same as windows
A few minor graphical and optimisation issues but windows has those two, so for proton purposes it's "flawless".
Changed my control settings to anything and everything. Controller simply doesn't work, therefor playing on Steam Deck doesn't work. Non-functioning. Somehow, my experiences aren't the same as everyone else's, but they persist even after re-installing, using different controllers, etc.
MANGOHUD=1 gamemoderun %command%
Game works absolutely fine under linux. As a game it has performance/optimization issues and a bunch of bugs - but that's equally true under windows too
Played combined 9 hours on Steam Deck and desktop
Game seems unoptimized based on visual art style, so hard to rate performance on Linux because of this. Game works out of the box with no hassel, simply download and play.
gamemoderun %command%
In large cities there's a lot of stuttering in busy streets (not sure if Linux specific though)
There's some jank but I believe most of it is on the game itself
It works well on Linux and Steam Deck
I doubt the problems I faced were proton exclusive, as the game is still new.
Loading a game reset some aspects of the world, like bullet holes. I imagined they had some overhaul or something.
Game just left early access, I reported all the bugs to the devs
On Steam Deck, the defaults caps at 30 FPS, it is very playable but the TDP can go +20W when it is raining outside. You might want to tweak some settings to improve your battery life.
Works great!
Took a few tries getting the settings right with a tiling wm.
gamemoderun %command%
Frame stuttering occurs but it seems to also be an issue on windows.
taskset -c 0-7 %command%
There is stutter when entering parts of the city, as well as during the openning cutscene (but the cut scene was also a problem on windows)
Loading screen when booting took longer than expected.
The game is playable if you're fine with stutters or just locking your framerate to 30.
taskset -c 0-7 %command%
Maximused fullscreen, windowed fullscreen, and exclusive fullscreen all act exactly the same as if they were just exclusive fullscreen.
The game does not fully utilise my CPU, GPU, nor system memory, yet still has problems. It runs at 400 FPS in the menus. Without this launch option, while in-game and un-paused, I get 55-65 FPS indoors and 35-55 FPS outdoors on a vey large city. Using the listed launch option gives me 80-90 FPS indoors and 50-60 FPS outdoors on a very large city. The game also slows down over time and needs to be restarted to fix.
If you are running around the city, you will occasionally have items appear right in front of you or fall through the map when entering buildings/rooms.
To my knowledge, the issues I have listed(except maybe the fullscreen issues) are not exclusive to linux/wine/proton and also occur on Windows.
Been playing in desktop mode in 1080p with FPS capped to 45, AA and rain detail turned down a bit. Frames are a bit choppy, often sitting in 30s indoors and dropping to 20s outside. Outside rain is the worst. No instability in 7h playtime though.
Unable to launch the game
I used to be able to play normally back when I used Arch with proprietary Nvidia drivers. I moved to Fedora 40 since the Wayland implementation with the latest Nouveau drivers were perfect in this aspect (I use my machine to work as well, so I needed it =/ ) however I'm not able to launch the game. I'll always get the 'Failed to initialize graphics.' error. Or, running with an older version of Proton (7.0) I can get to the 'Press any button' screen, then it will load forever (waited for more than 15 minutes and still there).
Trying with "PROTON_USE_WINED3D=1" I can get to the 'Press any button' as well, but then the game crashes.
Great game, working well in Linux
Found no problems at all
Works perfectly
Works perfectly
The game runs fine but takes 4 to 6 minutes to get to the main menu
This is an amendment to my previous report that stated it doesn't run. It turns out if you wait long enough the game does eventually load. From a little bit of searching around I found other people reporting the same thing, the developers said they're not sure why that happens at this time but it doesn't seem to affect everyone. If you're getting that, just try waiting. The game seems to run fine other than that.
You get to 'Press any Key' and after you do the egg timer loading icon spins for a second and then holds still and the game does not load.
This game worked perfectly previously, not sure what has changed.
To overwrite a previous report were I thought I used the default version
Game crash with some UI interaction.
Tutorial video playback play, but have serious visual issue.
The game crash with many interaction on the board, like creating any connection. This also include looking up the name at the beggining of the tutorial.
Tried switching to any of the 2 beta branch, as well as using the Nvidia gpu.
Unplayable as is. City exploration seems to work fine, thought.
Worked flawlessly
Works out of the box
No special configuration needed, install and hit play, runs flawlessly.
Fun mystery detective game hampered currently by it's procedural generation. Repetitive once you know all the types of murders.
Early access game, so probably that if not issues with proton. Generates 0 thickness walls on it's procedural generation and makes buggy maps.
Had a very large map. Broke that save when I tried to reload. Used a Large map and worked fine.
Probably because of early access and some unoptimized code. I think memory leaks when reloading while playing a file.
taskset -c 0-7 %command% -window-mode exclusive
Since the version 34.02 update the game has some serious FPS issues. You need to limit the cores count to 8 or less, or you end up having less than 10 fps in outside areas. This is actually an Unity engine memory allocator issue.
If the effect of core count limiting wears off after playing some minutes you very likely ran into low-memory issues. To fight this you have to modify the file "Shadows of Doubt_Data/boot.config" and increase the memory pools to values actually used in the Unity editor itself: memorysetup-bucket-allocator-block-size=8388608 memorysetup-bucket-allocator-block-count=8 memorysetup-temp-allocator-size-preload-manager=33554432
taskset -c 0-7 %command% -window-mode exclusive
Since the version 34.02 update the game has some serious FPS issues. You need to limit the cores count to 8 or less, or you end up having less than 10 fps in outside areas. After limiting the core count the game runs fine again.
The Proton version doesn't really matter, it is important the game does not use more than 8 cores.
Overall it worked out of the box. In Proton 7 there were two bugs: if you clicked off of the game window at all, it would go black, and the only fix was a game restart. The second bug was that pictures shown in hints would not appear. This bug was fixed if you used the GloriousEggroll fork of Proton.
As of GE Proton v8, everything works absolutely perfectly. I haven't tested vanilla Proton v8, but I'm guessing it works as well.
Started moving things around for more comfortable gameplay but this scheme worked fine ootb.
TDP Limit 12
Currently there's issues with which in-game window is focussed when using a controller. In the past that left me unable to continue playing. Fortunately; switching to keyboard and mouse makes the game really playable.
Some Frame Drops, particularly when going from inside to outside in the rain. Additional stutter during save, nothing terrible for an early access at all.
Initially I struggled to get things to feel okay, after switching to keyboard and mouse it's pretty solid. I'm really glad because this game seems like it has huge potential; it's a fascinating concept.
TDP Limit 12
Some dips when walking out into the rain.
Got soft locked on the tutorial windows opening above the case board, but the case board being selected. This lead to not being able to close the tutorial windows. Happened twice in separate save games. Also got a forever spinner on one load after pressing the any key.
Have submitted a bug report and will definitely play again after updates.
Worked out of the box but had some frustrating UI Bugs and I wasn't able to complete the tutorials.
I think the game has great potential and have submitted bug reports. Hopefully the devs are on it, I'll wait for an update then try again.
