PlayableShow Details
Unknown
I forced Proton 9 instead of native.
When the native version was installed, I was not able to play because the game acted liked I had a controller connected and holding leftwards. It fought my keyboard. I couldn't even navigate menus and had to Alt+TAB and then force quit via Steam.
Keyboard + Mouse Don't Work
Enabling Steam Input oddly solved this problem a while ago, but it no longer does the trick. I cannot use keyboard and mouse because the game acts like I'm using a controller. I do not have any wired or wireless or Bluetooth controller connected.
I uninstalled the game and may retry with Proton instead of native.
gamescope -f -w 2560 -h 1440 -r 180 --hdr-enabled gamemoderun %command%
After changing settings and going back in-game, the camera will spin until you left-click.
Be sure to adjust your HDR intensity in settings to get an accurate experience.
Quite Good
Even without a controller connected, the game acted like one was fighting my keyboard and mouse. It was unplayable until I enabled Steam Input, which made my keyboard and mouse work.
Perhaps the game detected my keyboard or mouse as a controller...? I am using a Razer Naga Pro which has buttons on the side. It was not possible to use the keyboard, mouse, nor controller until I force enabled Steam Input. Then, all of those accessories worked.
I got great framerates using High graphic settings at 1440p.
Everything works perfectly
With Proton 6.3-8, the game simply works well on Pop!_OS, unlike with 7.0-6 and 8.0-2, or Natively.
Again, note that this is on Pop!_OS, which might have some inherent issue with this game, as it won't even run Natively. - For now I can tell that the newest Proton-version that does work without issues is 6.3-8.
Flickering lighting and corrupted shadows.
Even though Proton 7.0-6 doesn't have the broken screenspace-reflections and sudden lighting-changes that 8.0-2 has, neither is ideal.
Simply does not launch Natively on Pop!_OS
Not sure if it is indeed Pop!_OS to blame, but the process doesn't even keep running. It actually shuts down immediately with nothing even showing. - It's worth noting that it does run through Proton, albeit flawed, as noted in a different report of mine.
I think the visual anomalies are probably too distracting, as they look too unusual to not notice.
Some popping, but not sure if it's unrelated.
Broken lighting, switching between light and dark when turning the view in many certain areas, with the screenspace-reflections being projected incorrectly, and probably more issues.
Works ootb.
As previous reports mention, running through proton instead of native, gives better performance.
Works perfectly fine with proton.
Native version is broken.
Lock 40 fps
Small letters
sometimes drops to 20 fps
All works perfect!
To fix occasional freezes - turn off your second monitor
Fixed by unplugging/turning off the second monitor
And that's really it. I can see people reporting the same issue I have on Nvidia hardware, but it was all gone after I switched off my second screen. Note that I have it plugged in by DisplayPort, but if you're using some other method, you might want to physically unplug the cable from the machine. Just make sure your OS doesn't "see" it plugged it.
yes it runs very well
even at the highest graphics
I have no Idea why this is marked as unsupported, because it runs perfectly on the SD out of the box.
No problem to run it under Linux out of the box
The native version crashes starting. Use the proton version forcing proton 7.0-3 in Steam properties of the game.
Crashes my system when trying to load the game despite Deck verification.
The Feral Launcher of the nativ Linux Port just won't start the game and makes the Steam Deck reboot. Use Proton instead.
Feral Launcher makes Steam Deck reboot when you try to launch the game from it. Use Proton Instead of Native
If you use DX12, you'll get heavy flickering on the Colorado level. DX11 solves this issue with no apparent drawback.
I played it with Proton just to test how it run and forgot to switch back to native because it run great.
On another hand, like always, turn on Steam Input if you have a Dualsense and want to use the touchpad, and to enable more options. However, this adds some delay (like a minute) when you launch HITMAN (if you use GNOME, this delay, for some reason, can crash your desktop. This didn't happen on KDE).
Worked flawlessly
I used Proton-6.18 from GloriousEggroll
Given the frequent crashes with no clue as to why I deem it would be frustrating for the average game enjoyer at this current state.
sometimes when alt+tabbing the game will not return to full screen
game will crash at random. seems to happen shortly after triggering an event i.e in paris it keeps crashing when I either get a new disguise or further an opportunity. Happens on both d3d11 and d3d12. Various proton versions do this as well as proton GE.
Had htop and cpu-x running on second monitor to see if it was due to temp or anything like that and saw no gpu temp above 66C and cpu never above 45C (hyper 212 keeps that thang cool)
Works great
Initial installation config was defaulted to Steam Linux Runtime, which didn't worked for me (crashed), but once I changed the compatibility to Proton Experimental, it loaded and ran with no issues what so ever.
Proton-6.14-GE-1 GloriousEggroll
DX12 don't render properly - everything was yellow, use DX11 instead
This is report for proton with FSR, game runs up-scaled to 4k just as 1080p on native. FPS can be allover the place, but for me runs above 60, 100+ most of the time. From 1080 to 4k with no performance drop, pretty neat.
