The Alters (1601570)
Compatibility Report
- Name of the game with compatibility issues: The Alters
- Steam AppID of the game: 1601570
System Information
- GPU: RTX 4080
- Video driver version: 4.6.0 NVIDIA 575.57.08
- Kernel version: 6.15.2-arch1-1
- Link to full system information report as Gist:https://gist.github.com/EnLaLuna91/fdace481cde9cffe0a3206ab8894da8a
- Proton version: Proton experimental and Proton 10.0-1 (beta)
PD: I have compressed the log in a tar.gz because it won't let me upload it, as it weighs more than 35Mb.
I confirm:
- [x] that I haven't found an existing compatibility report for this game.
- [x] that I have checked whether there are updates for my system available.
Symptoms
After displaying the logos, warnings and loading the shaders, the screen freezes, I have waited for more than 10 minutes, but it does nothing.
Reproduction
Start the game.
I am having the exact same issue, but with very different hardware/desktop etc.
https://gist.github.com/screwylightbulb/0cfca68000ba76c9c4b26353af2b7700
The game for me crashes if I do any kind of input with Keyboard or Mouse. If I launch the game and only use the controller without touching kb/m then it does not crash.
The game for me crashes if I do any kind of input with Keyboard or Mouse. If I launch the game and only use the controller without touching kb/m then it does not crash.
I can confirm this, game immediately crashes when I move the mouse, but I could get past the crash with a controller.
The game for me crashes if I do any kind of input with Keyboard or Mouse. If I launch the game and only use the controller without touching kb/m then it does not crash.
I can confirm this, game immediately crashes when I move the mouse, but I could get past the crash with a controller.
Did you happen to find a workaround?
Did you happen to find a workaround?
I have not been able to find anything to stop it crashing on mouse input.
Edit: Changing the display mode to "Windowed" makes the crashes on mouse input stop, but that starts causing weird artifacting around the mouse cursor.
Yeah can also confirm it crashes on mouse / keyboard input. Wonder if there's some kind of workaround using gamescope.
I don't have a controller to test or fix the problem, I only have a keyboard and a mouse.
It's strange that with keyboard and mouse it fails in this way, isn't it?
Yeah can also confirm it crashes on mouse / keyboard input. Wonder if there's some kind of workaround using gamescope.
Did you have any luck with gamescope?
Experienced a couple game crashes on 575.57.08, usually happening at the beginning of some cutscenes. Most recent was starting Journey 1.
Notable line in logging seems to be:
3047.131:016c:0244:err:msvcrt:_wassert (L"iface->lpVtbl == &d3d12_resource_vtbl",L"../src-vkd3d-proton/libs/vkd3d/vkd3d_private.h",1159)
System:
Host: blackwell Kernel: 6.15.2-2-cachyos arch: x86_64 bits: 64
Desktop: Cosmic v: N/A Distro: CachyOS
CPU:
Info: 8-core model: AMD Ryzen 7 9800X3D bits: 64 type: MT MCP cache:
L2: 8 MiB
Speed (MHz): avg: 4133 min/max: 603/5272 cores: 1: 4133 2: 4133 3: 4133
4: 4133 5: 4133 6: 4133 7: 4133 8: 4133 9: 4133 10: 4133 11: 4133 12: 4133
13: 4133 14: 4133 15: 4133 16: 4133
Graphics:
Device-1: NVIDIA GB202 [GeForce RTX 5090] driver: nvidia v: 575.57.08
Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
compositor: cosmic-comp driver: gpu: nvidia,nvidia-nvswitch
resolution: 640x480~60Hz
API: EGL v: 1.5 drivers: nvidia,swrast
platforms: gbm,wayland,x11,surfaceless,device
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 575.57.08
renderer: NVIDIA GeForce RTX 5090/PCIe/SSE2
API: Vulkan v: 1.4.313 drivers: nvidia surfaces: N/A
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor gpu: nvidia-settings,nvidia-smi
wl: wayland-info x11: xdpyinfo, xprop, xrandr
Any idea of a possible solution to get the keyboard and mouse to work and not freeze the screen? I understand that there is no possible solution?
There's a thread about it here on the steam forums. I think the only viable workaround at the moment is to run the game in windowed mode. It works fine for me with mouse and keyboard, but any attempt to switch to fullscreen will cause the menus to freeze upon keyboard/mouse interaction.
Thanks, it seems that when I play with %command% -ResX=2440 -ResY=1361 -windowed at least I get to the menu, which before even that, now I can not test I can not play for time, but tomorrow I will try to see if you can play.
Windowed mode isn't ideal, but I'm in the third chapter. It's never crashed, and I haven't noticed any unintentional graphics corruption.
Alters are crashing (or just exit) after chapter is done or some cutscenes played on Steamdeck OLED 1TB. Tested with default proton config, proton-10.0-2 (beta), proton hotfix, proton experimental. It frustrating but playable.
Full game is borked on Nvidia GPUs (Seems to work for some AMD users, needs confirmation)
You can run it in a windowed mode, and it is kind of playable with a gamepad, but the moment you move your mouse or press any key it dies. Also water texture colors are wrong.
I've tried to address this in my Steam review and asked devs to confirm if this WILL NOT be worked on to fix, and got this in response from the developer:
Hello sTiKyt,
Thank you for taking the time to leave a review. We're sorry to hear you've encountered technical issues with our game.
I confirm that, while it's supported on Steam Deck, the game is not and will not be supported on Linux OS.
The system requirements are always available both on the Steam Store and on our FAQ site.
Wishing you well!
Agata, 11 bit studios
Basically, some community manager is simply telling us it won't be fixed and they don't care. I'm refunding the game.
I hope someone checks at this, unplayable on fullscreen even with AMD GPU :S
The game freezes on default settings after the initial logos and prompts.
I was able to get to the menus with the -windowed launch option, and then set to exclusive fullscreen in the game options, which seems to work fine with mouse+keyboard (have yet to start a journey). However you need to enable fullscreen every time.
I have AMD hardware with a multi monitor setup.
The game freezes on default settings after the initial logos and prompts.
I was able to get to the menus with the
-windowedlaunch option, and then set to exclusive fullscreen in the game options, which seems to work fine with mouse+keyboard (have yet to start a journey). However you need to enable fullscreen every time.I have AMD hardware with a multi monitor setup.
FYI, it mouse and keyboard only seems to work for AMD users, for Nvidia game is broken, I've yet to see at least one case where it works on Nvidia
Game freezing after shaders are built. I've tried various fixes mentioned on ProtonDB but none work, I've not been able to run it in windowed mode on my AMD hardware, having to dual-boot to play this game which I find a little painful.
I was saddened to read the response from the developers that was posted above.
Can confirm that mouse and keyboard causes a crash after the shader compilation window. Thankfully, with the gamepad it seems to be quite stable (it crashed once for me after the opening sequence, but afterwards it's been rock solid for ~10-15 in-game days on nvidia)
The Alters received a bigger update today and I tried it with Proton Hotfix and it seems to work now. At least I can get into the main menu - didn't have the time to properly start it at the moment because I'm busy.
The Alters received a bigger update today and I tried it with Proton Hotfix and it seems to work now. At least I can get into the main menu - didn't have the time to properly start it at the moment because I'm busy.
It works, just playing now! Thank you for your post about the update.