Compatibility Report

the exact same thing happens to me

It's just a workaround, not a fix, but I'm having no issues with the latest Proton GE and this launch command: PROTON_MEDIA_USE_GST=1 GST_PLUGIN_FEATURE_RANK=protonaudioconverterbin:NONE %command%

This initial-video crash doesn't seem to happen on latest experimental. Can anyone else confirm?

System Information

• GPU: AMD Radeon RX 7900 GRE
• Video driver version: Mesa 26.1.0-devel
• Kernel version: 6.19.6-200.fc43.x86_64
• Link to full system information report: systeminfo.txt
• Proton version: proton-10.0-4

I have played 8+ hours so far without any crashes on my setup, for the record I did not have any problems with the demo either.

For reference including log of playing the game up until you get to actual gameplay:
steam-3920610.zip

This initial-video crash doesn't seem to happen on latest experimental. Can anyone else confirm?

yes, seems to work for me. i see that there was an update to atelier yumia no longer crashing because of videos in the tutorial, which is also a Koei Tecmo game. Maybe that was the very same issue plagueing this one

I can also confirm that the initial cutscene crash seems to be fixed for me on the latest Proton Experimental.

Attaching my Proton log from a recent test run for reference.
steam-3920610.zip

However, the gamepad issue is still present on my system. The game does not respond to any gamepad input, either on the main menu or in gameplay.

So while the crash appears to be resolved, the controller issue remains.

What gamepad do you have and how are you connecting it to your computer? My
8bitdo ultimate works, at least with its 2.4ghz dongle

On Sat, Mar 14, 2026, 8:09 PM Mikhail @.***> wrote:

NTMan left a comment (ValveSoftware/Proton#9567)
https://github.com/ValveSoftware/Proton/issues/9567#issuecomment-4061757786

I can also confirm that the initial cutscene crash seems to be fixed for
me on the latest Proton Experimental.

Attaching my Proton log from a recent test run for reference.
steam-3920610.zip
https://github.com/user-attachments/files/26000535/steam-3920610.zip

However, the gamepad issue is still present on my system. The game does
not respond to any gamepad input, either on the main menu or in gameplay.

So while the crash appears to be resolved, the controller issue remains.

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/9567#issuecomment-4061757786,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQZQ4ECXI556PWCCQ7VQJHT4QXYB3AVCNFSM6AAAAACWPGZWFOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DANRRG42TONZYGY
.
You are receiving this because you commented.Message ID:
@.***>

I'm having no input issues on Experimental. I have Steam Input disabled, those having the issue might try turning it off if it's on.

If I restart the game with the controller on, it does see the buttons.
I use a ps5 controller over bluetooth.

I'd like to point out that on Steam Deck the lastest Proton Experimental helps pass the initial crash, but some videos are still consistently causing crashes later in the game, no matter the Proton version used.

Foe example, in the Bloodstained Room of the Kurosawa House, there is a bead item on the floor. When you pick up the bead item an effect plays in the background as you pick it up. Kind of like a "you acquired a new item" sort of effect. However, this effect is broken and crashes the game on all tested proton versions - Proton Experimental, Proton Hot fix, Proton 9, Proton GE latest.

You can see the effect having a blown out look which then crashes the game (although if you cancel the item pickup fast enough you can avoid the crash).

I attempted to capture a screenshot of it, but it unfortunately crashes the game before I can do so.

Can you share a save file close to a crash?

On Wed, Mar 18, 2026, 11:00 PM Matthew Galbraith @.***>
wrote:

MatthewCGalbraith left a comment (ValveSoftware/Proton#9567)
https://github.com/ValveSoftware/Proton/issues/9567#issuecomment-4087355093

I'd like to point out that on Steam Deck the lastest Proton Experimental
helps pass the initial crash, but some videos are still consistently
causing crashes later in the game, no matter the Proton version used.

Foe example, in the Bloodstained Room of the Kurosawa House, there is a
bead item on the floor. When you pick up the bead item an effect plays in
the background as you pick it up. Kind of like a "you acquired a new item"
sort of effect. However, this effect is broken and crashes the game on all
tested proton versions - Proton Experimental, Proton Hot fix, Proton 9,
Proton GE latest.

You can see the effect having a blown out look which then crashes the game
(although if you cancel the item pickup fast enough you can avoid the
crash).

—
Reply to this email directly, view it on GitHub
https://github.com/ValveSoftware/Proton/issues/9567#issuecomment-4087355093,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQZQ4EDWMR2F2SGXL36RGVD4RNPE3AVCNFSM6AAAAACWPGZWFOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DAOBXGM2TKMBZGM
.
You are receiving this because you commented.Message ID:
@.***>

What gamepad do you have and how are you connecting it to your computer? My
8bitdo ultimate works, at least with its 2.4ghz dongle

I am using a Flydigi Vader 5 Pro connected through its dedicated USB dongle.

On my system, Steam detects it as a "Generic X-Box pad". The game is using the default Steam Input settings.

Even though the controller is detected by Steam, the game does not respond to any gamepad input, either on the main menu or during gameplay.

Relevant kernel log when the controller is connected:

[Thu Mar 19 11:10:52 2026] usb 1-1.1.4: new full-speed USB device number 10 using xhci_hcd
[Thu Mar 19 11:10:52 2026] usb 1-1.1.4: not running at top speed; connect to a high speed hub
[Thu Mar 19 11:10:52 2026] usb 1-1.1.4: New USB device found, idVendor=37d7, idProduct=2401, bcdDevice= 0.01
[Thu Mar 19 11:10:52 2026] usb 1-1.1.4: New USB device strings: Mfr=0, Product=2, SerialNumber=3
[Thu Mar 19 11:10:52 2026] usb 1-1.1.4: Product: Flydigi Vader 5 Pro
[Thu Mar 19 11:10:52 2026] usb 1-1.1.4: SerialNumber: Flydigi Vader 5 Pro
[Thu Mar 19 11:10:52 2026] input: Generic X-Box pad as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:0c:00.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4:1.0/input/input26
[Thu Mar 19 11:10:52 2026] hid-generic 0003:37D7:2401.000F: hiddev99,hidraw10: USB HID v1.10 Device [Flydigi Vader 5 Pro] on usb-0000:0c:00.0-1.1.4/input1
[Thu Mar 19 11:10:52 2026] input: Flydigi Vader 5 Pro as /devices/pci0000:00/0000:00:02.1/0000:05:00.0/0000:06:0c.0/0000:0c:00.0/usb1/1-1/1-1.1/1-1.1.4/1-1.1.4:1.2/0003:37D7:2401.0010/input/input27
[Thu Mar 19 11:10:52 2026] hid-generic 0003:37D7:2401.0010: input,hidraw11: USB HID v1.11 Mouse [Flydigi Vader 5 Pro] on usb-0000:0c:00.0-1.1.4/input2
[Thu Mar 19 11:10:52 2026] hid-generic 0003:37D7:2401.0011: hiddev100,hidraw12: USB HID v1.11 Device [Flydigi Vader 5 Pro] on usb-0000:0c:00.0-1.1.4/input3
[Thu Mar 19 11:10:52 2026] input input26: unable to receive magic message: -121
[Thu Mar 19 11:10:53 2026] input input26: unable to receive magic message: -121
[Thu Mar 19 11:10:53 2026] input input26: unable to receive magic message: -121

@NTMan I did more testing. two 8bitdo controllers, steam horipad, dualsense and xbox series x. Neither controller worked with steam input, dualsense also didn't work with steam input disabled. I swapped to windows and saw even worse results as I couldn't get any controller to work with the game, and after searching around it seems other users are also having the same issue. Seems like this game is temperamental about controllers in general, in your case I suggest trying to disable steam input for this game

Just to clarify: Steam Input is already disabled on my side.

My Flydigi Vader 5 Pro is connected via its 2.4 GHz USB dongle and is detected by Steam as a "Generic X-Box pad".

The controller layout page for this game says:
"This controller is not using Steam Input" and "Using the game's built-in support".

Also, in Steam's global controller settings, "Enable Steam Input for Xbox controllers" is disabled.

So in this case, the game is relying on its built-in controller support, but it still does not respond to any gamepad input, either on the main menu or during gameplay.