Callisto Shot
Published
The selectable "Play Abiotic Factor (DX11 for Lower-End PCs)"
Occasional client-side failure to see what server user had placed. Possibly just an early access bug and platform agnostic.
It wouldn't launch by default, but given the built in launch option and change to forced experimental fixed the problem it's not much tinkering to do for me. My low-end GPU could very well be the only reason the launch option is necessary.
Excellent compatibility, absolute love letter to both Half-Life 1 and SCP-style settings.
LD_PRELOAD="" %command%
Primarily over LAN, but no issues.
I love this game, they keep making it more delightful. I imagine it's even more fun with more people, I've mostly played as a duo.
Worked fine first thing on Bazzite, save the listed issue.
Alt-tab out of fullscreen makes game unresponsive to mouse clicks until you alt tab again, even if you clicked back in.
The battle music in this game has been stuck in my head for days.
Slowdown during initial load predicted menu crash issues for that play session; unavoidable except with relaunching, which would have required the menu, or killing the process, which would be marginally better than crashing all of KDE, but menu opens when you lose focus on the application.
Only happens once in a while, and autosaves are pretty frequent. Noticed no fans in my computer are spinning up, so it may be attempting to use a device that doesn't exist to render menus? A guess.
Got a travel together quest from a main quest NPC, wanted to go very far. I escorted her through a nightmare ruin and nearly 2 hours of gameplay, she fell in a lake with no outside interference at the finish line and the quest failed. Love this game.
The game feels great, even on mouse and keyboard. I found myself falling for the "one more run" urge faster than expected.
DXVK_FILTER_DEVICE_NAME=1080 %command%
Echoing what others have said, it doesn't select your GPU automatically. I don't have any other GPU and it still had trouble until I added the launch option. In the menu it selected "Auto" and the other option was my GPU, so I think it's an issue of detection outside of the expected OS.
Occasional slowdown, unsure of cause so far. Very seldom and I'm willing to blame Nvidia tbh. It's usually fair, on Linux.
At this early stage, already promising! Supergiant have once again earned my heart.
The beta will not actually start for 5 hours, so any reports before this one may need to be re-attempted at that time.
It launched, pre-compiled shaders, let me select language, and failed to find a server. This was expected behaviour.
Noting this is a beta report, the game had great feel but a total lack of stability, leaving me unable to play despite hours of tinkering.
VKD3D_CONFIG=disable_uav_compression
The recommended Frame Generation setting would always have ghosting every time the camera angle changed on every object. I found it nauseating.
I finished one hunt in the 10 hours of the game I played. After tutorial I experienced crashes within minutes of leaving the hub area, if not in the hub area itself. I'm told there is a texture memory leak issue for AMD graphics cards in the beta.
I really don't know why I got my hopes up for a beta on this engine, but I still have hopes for the full release.
So long as Capcom doesn't break the game repeatedly and one's system can run the thing, it's a good MonHun
MESA_DISK_CACHE_SINGLE_FILE=0 %command% LD_PRELOAD=""
https://github.com/ValveSoftware/Proton/issues/8206#issuecomment-2777572002 As noted by a previous report, followed this info after Title Update 1 rendered the game unlaunchable. Downgrade of DirectStorage v1.2.3 to v1.2.2 solves the problem, though slight increase in performance problems from before update even with that.
Sometimes I catch the PS1 polygons momentarily undressed before they put on their current gen trappings.
Sometimes the inputs would become very finicky and sticky, where my character would begin to walk in a direction I pressed on the keyboard a second ago and not stop, or inputs would not be registered (even while typing in another window while the game ran).
This usually predicated a full KDE desktop environment crash, so it may partially be a conflict with my desktop environment. Unpleasant, but rare enough I'm putting up with it, and it's usually not enough to force me to abandon a hunt.
Occasional slowdown in effect heavy weather events or monster encounters.
Previously mentioned full desktop environment crash, which has been a problem for me since release; I have not experienced it with any other game I've played through Proton.
Rey Dau once got stuck flying against a lightning rod for nearly 10 minutes, out of even gunlance reach. I had to wait for the game to realize there was a problem and teleport it to its nest.
Once or twice in my 114 hours I had a desync where we ended up on separate hunts, but not common and probably platform agnostic.
I was worried this would be unplayable on Linux, but it's been pretty decent (at least on my hardware) and I love the direction they're taking the series, too.
