protonscr

Aniimo

protonopen appid 4126040Game compatibility - Unofficial
ValveSoftware/Proton#9427 · opened 2026-01-23 by ruineka · updated 2026-09-19 · 11 comments · github · game page · search this game
Rruineka 2026-01-23 github

Compatibility Report

  • Name of the game with compatibility issues: Aniimo
  • Steam AppID of the game: 4126040

System Information

  • GPU: Radeon 9070 XT
  • Video driver version: Mesa 25.3.3
  • Kernel version: 6.18.3-201.nobara.fc43.x86_64
  • Link to full system information report as Gist:
  • Proton version: Proton Experimental

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

Unable to click on anything using the mouse. Gamepad inputs work fine with both Xbox and Playstation input devices.

Capture includes the time a gamepad device is added and is used to login to the game.
steam-10034832281274679296.zip (Zipped due to the size being too large for upload as a .log)

Reproduction

Launch the game and notice the mouse clicks aren't registered to login to the server. The game is available on Steam and is only accessible in the Beta only and they sent me a PC (Downloadable) version of the game instead of a Steam key. I'm anticipating the same issues for those who are playing via the Steam key as well. It being a closed beta limits the amount of players who are actually able to report on issues ahead of time.

https://github.com/user-attachments/assets/82c565b7-a19e-47f0-b31f-292b70925a11

Rruineka 2026-01-23 github

I'll be reporting more issues as I continue to play test this game on Linux.

Symptoms

DX12 (experimental with frame generation) fails to launch entirely. The game only runs in Directx 11 mode.

Image

Reproduction

Enable DirectX12 mode from the launcher and attempt to start the game. You'll be greeted with a unity crash menu with no apparent crash logs generated in the game directory.

Image

steam-10034832281274679296.log (Crash log during the crash using DirectX12 mode.

Rruineka 2026-01-23 github

Aniimo consistently crashes after teleporting to some location at "idyll".

Symptoms

The game locks up after the player reaches a location shortly after the initial tutorials.

Reproduction

Complete the initial tutorials of the game and reach the point where you are able to teleport to a location at idyll. After you teleport the game will lock up.

Exact location at the time of crash.
Image

steam-10034832281274679296.log

Rruineka 2026-01-24 github

The game hasn't been crashing using Proton: 1752901048 GE-Proton10-10. The mouse issue remains though.

Rruineka 2026-01-26 github

It seems to be related to an issue with newer builds of Unity. I'm seeing reports with other games that are having the exact same issue I'm seeing with Aniimo. https://www.codeweavers.com/support/forums/general/?t=27;mhl=340150;msg=340150

Aandrfisch 2026-09-16 github

Continuing on this, Aniimo has launched and instantly crashes unless you are using Protons on version 10. So any Proton 11 and later crashes at menu, DX11 and DX12. The mouse issue does not appear to be an issue for me at game launch.

MMelechtna 2026-09-16 github

Seems to be a regression, works on 10-34

TTaithrah 2026-09-16 github

Official launch crashes at login for me when using [experimental-bleeding-edge-11.0-435061-20260916-p4db187-wc24a38-d7df359-v5d0db7-x86_64] and anything else. However 10.0-4 [10.1000-105] works fine.

Kkisak-valve maintainer 2026-09-16 github

Game crash after 20 seconds (4126040)

Issue transferred from https://github.com/ValveSoftware/Proton/issues/10150.
@cyber-insomniac posted on 2026-09-16T17:45:43:

Compatibility Report

  • Name of the game with compatibility issues: Aniimo
  • Steam AppID of the game: 4126040

System Information

  • GPU: Radeon RX 9070 XT (RADV)
  • Kernel version: 7.2.4-3-cachyos / 7.2.5-cachyos (reproduced across kernel updates)
  • Proton versions tested: Proton 10.0-4b, Proton Experimental (official, build experimental-bleeding-edge-11.0-434871-20260916), and Proton-CachyOS-SLR (cachyos-11.0-20260703-slr) — identical crash on all three

I confirm

  • [x] that I haven't found an existing compatibility report for this specific crash (there is an existing unofficial report, #9427, but it covers an unrelated symptom — mouse input not registering)
  • [x] that I have checked whether there are updates for my system available

Symptoms

Game launches, gets to the Steam login step, then reliably crashes ~20 seconds in, every launch, on every Proton build tested.

Crash details 
Exception 0xc0000005 (EXCEPTION_ACCESS_VIOLATION)
Access: Read
Address: 0x0000000000000060

Backtrace (from Proton Experimental official build, offsets from matching cachyos build in parentheses where they differ):

0 rsaenh.dll   +0x26432  (also seen at +0x32332 on a different Wine build)
1 rsaenh.dll   +0x5403   (also +0x6d2f)
2 advapi32.dll +0x10fa7  (also +0x13307)
3 FPXSteam.dll +0x4be69
4 FPXSteam.dll +0x1261d
5 FPXSteam.dll +0xe3aa
6 FPXSteam.dll +0x2b56e
7 FPXSteam.dll +0xc62de
8 kernel32.dll +0x11649
9 ntdll.dll    +0x10e0f

Faulting instruction at the crash site: callq *0x60(%rax) — an indirect call through what appears to be a null or uninitialized function pointer at offset 0x60 of some internal structure.

Analysis

FPXSteam.dll (the game's Steam-auth integration library) computes an HMAC using the legacy CryptoAPI (CryptCreateHash with CALG_HMAC, then CryptSetHashParam(HP_HMAC_INFO, ...) with HashAlgid = CALG_SHA_256). The crash happens inside rsaenh.dll's HMAC hash-init/update path.

I initially suspected this was the known issue where RSAENH_CPSetHashParam's CALG_HMAC case fails to find SHA-256 in a CSP's algorithm table and mis-reports success — but checking current Wine master (dlls/rsaenh/rsaenh.c), that specific path already guards against it:

pAlgInfo = get_algid_info(pCryptHash->hProv, pCryptHash->pHMACInfo->HashAlgid);
if (!pAlgInfo)
{
    FIXME("Hash algroithm %#x not found.\
", pCryptHash->pHMACInfo->HashAlgid);
    return FALSE;
}

Since the crash backtrace is past this point (inside the actual hash init/update calls that only run after pAlgInfo is found), the algorithm lookup is succeeding, and the null-pointer deref is happening somewhere inside the hash context setup/update itself — a distinct, apparently still-open bug.

I also tested a registry-based workaround (adding a duplicate PROV_RSA_FULL-type provider entry aliased to the AES-capable personality, to rule out CSP-selection as the cause). The crash was byte-for-byte identical with and without that change, which further supports this being a bug inside rsaenh.dll's HMAC code path itself rather than a CSP/personality selection issue.

Reproduction

  1. Launch Aniimo through Steam (any recent Proton build).
  2. Log in through the in-game Steam auth step.
  3. Crash occurs ~20 seconds after launch, always at the same location.

Attachments

  • crashinfo.txt from <library>/steamapps/compatdata/4126040/pfx/drive_c/users/steamuser/AppData/Local/Temp/Aniimo/Aniimo/Crashes/
  • Full PROTON_LOG=1 Wine debug log (steam-4126040.log)

Happy to provide additional logs or test patches if anyone wants to dig further — this looks like a genuine crypto-provider bug in rsaenh.dll, not a GPU/driver/anticheat issue.

steam-4126040.log

crashinfo.txt

PPuppy-Derg 2026-09-17 github

I have a laptop with a nvidia gpu in it and the game works fine once you use proton 10.0-4. I have working mouse and keyboard aswell. I'm using openSUSE Tumbleweed with linux kernel version 7.2.4 and kde. I've not had any issues with the mouse and keyboard in-game even on different proton versions. Maybe it could be something with amd cards or an earlier version of the game.
I can post a video of it running (the framerate is not amazing but it works)

Nneptuwunium 2026-09-17 github

I've only encountered mouse issues on Proton 11 variants while forcing Wayland compositing, likely due to the web view frame taking over the entire screen and not passing through input. Given that the game crashes upon authentication on proton 11 from a rsaenh null deref, I don't think anyone is encountering this issue at the moment and the mouse issue is an older issue from one of the betas.

Proton 10 and variants work fine due to rsaenh still using bcrypt, as does standalone wine 11.11 with the off-steam launcher due to wine 11.11 replacing TomCrypt with Wine SymCrypt.

LLupinio 2026-09-19 github

Working workaround for the login crash (rsaenh HMAC-SHA256), tested on proton-cachyos 11

Follow-up to the root cause in Wine bug 60345: the crash can be worked around today with a registry change in the game's prefix.

Why the earlier registry test didn't help: rsaenh picks its algorithm set ("personality") by provider name via string compare in new_key_container(). Only the AES personality lists CALG_SHA_256. A new or duplicate provider name falls through to the Strong personality, which still lacks SHA-256, so nothing changes. The existing name Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype) (MS_ENH_RSA_AES_PROV_XP_A) is mapped to AES. Registering that provider as type 1 and making it the default for PROV_RSA_FULL gives FPXSteam an HMAC-SHA256-capable provider.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Defaults\Provider\Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype)]
"Type"=dword:00000001

[HKEY_LOCAL_MACHINE\Software\Microsoft\Cryptography\Defaults\Provider Types\Type 001]
"Name"="Microsoft Enhanced RSA and AES Cryptographic Provider (Prototype)"

Save it as aniimo-rsaenh-fix.reg and import it with the game closed, either via protontricks (protontricks -c "wine regedit aniimo-rsaenh-fix.reg" 4126040, run from the folder containing the file) or directly with the wine binary of the Proton build the game uses: WINEPREFIX=<steamapps>/compatdata/4126040/pfx <proton>/files/bin/wine regedit aniimo-rsaenh-fix.reg. Tested: importing this file with wine regedit into an unmodified prefix sets both values. Type 024 and the 32-bit (Wow6432Node) view stay unchanged; the game is 64-bit.

Verified with WINEDEBUG=+crypt: same sequence as in the crash (CryptImportKey 44 bytes → CryptCreateHash(CALG_HMAC) → CryptSetHashParam(HP_HMAC_INFO, CALG_SHA_256) → CryptHashData(84)), but the fixme:crypt:init_hash Hash algroithm 0x800c not found line is gone, CryptHashData succeeds, and CryptGetHashParam returns a 32-byte HMAC-SHA256 that FPXSteam base64-encodes. Login and server list work, no crash.

Note: a Proton version switch may re-register rsaenh and revert this, so re-apply after switching.

For the real fix in rsaenh: RSAENH_CPSetHashParam(HP_HMAC_INFO) ignores the return value of init_hash() and returns TRUE with an uninitialized hash. Windows also accepts SHA-2 inner hashes for HMAC on PROV_RSA_FULL.

System: GPD Win Max 2 (Ryzen 7 6800U / Radeon 680M), CachyOS, proton-cachyos 11.0

Related threads

Proton versions

Launch options

Upstream links

DLLs

Error codes