VerifiedShow Details
Unknown
Game works well. Multimon needs mouse bound to main monitor using gamescope to say within game boundry.
gamescope -W 3440 -H 1440 -e -f --force-grab-cursor %command%
Windowed mode leaves the gnome top bar visable. Fullscreen works like Windowed borderless
If have multiple monitors, mouse will move outside the main monitor. Fixed the issue with gamescopes --force-grab-cursor. See launch options.
Game runs well, no issues. Players with multiple monitors should use gamescope's force-grab-cursor to keep mouse on main monitor while playing. Run the game in fullscreen to get rid of the Gnome top bar while playing.
Works out of the box with Native HOTAS support on Saitek X52 joystick and throttle.
Computer will randomly freeze up and require a hard reboot when playing.
I cannot conclude which part of my system is causing this, but I can confirm that it only happens while playing House of the Dying Sun.
No issues
Completed a playthrough using a DualSense controller, everything worked fine.
If the game is having issues and it's on external storage, try moving it to internal storage first.
Switched deck to beta branches to run, otherwise game would freeze in cockpit.
mission objectives hard to read. lowering resolution below defaults makes it worse quickly
A lot of the HUD text, like objectives and targeting data, is too small.
Save data is deleted when the game is uninstalled
Flawless out of the box experience. Played the entire game on max settings & difficulty with no issues
mangohud %command%
Didn't try using controllers, joysticks or VR.
Worked on 5.13-6 without additional tinkering. Played tutorial in VR mode (about 20 minutes) and then desktop mode (10 minutes).
Played with HTC Vive and Steam controller.
Does not seem to work in VR (Valve Index, Proton 5.13-1 and 5.09-1)
A black window appears and some background voices are heard and it gets stuck there. Cursor is locked to the window, so you have to interrupt it to get out and it then crashes SteamVR.
I think it will work well as long as you don't use a HOTAS
This uses the same binding system as absolute territory, it does not work with my hotas, it cannot detect throttles
Unknown(< 1 hour with Proton)In my case, I have a different timezone and language. Had to go to properties -> set launch options -> TZ= LANG=C LC_ALL=C %command% --- then it worked perfectly.
Unknown(< 1 hour with Proton)
Ran with zero issues.
Really good performance. Get around 120 FPS at 4k, only graphics options tweaked was reduced AA down to 2x.
Literally bought this game because it was recommended. I didn't know if it worked or would but sure enough, It was plug and play. If I didn't know about proton and DXVK I'd believe that this was a native title.
Unknown(an hour with Proton)VR was not tested. Did not try the DX9 start option.
Unknown(an hour with Proton)UnknownHTC Vive. No issues apart from not detecting Steam Controller
UnknownUnknownRuns flawlessly
Unknown
