I don't want to open a new issue so I will post the log here

steam-587620.log

EDIT: the game works in Wine-staging + DXVK + Esync

Computer Information:
    Manufacturer:  Unknown
    Model:  Unknown
    Form Factor: Desktop
    No Touch Input Detected

Processor Information:
    CPU Vendor:  GenuineIntel
    CPU Brand:  Intel(R) Xeon(R) CPU           X5675  @ 3.07GHz
    CPU Family:  0x6
    CPU Model:  0x2c
    CPU Stepping:  0x2
    CPU Type:  0x0
    Speed:  3068 Mhz
    12 logical processors
    6 physical processors
    HyperThreading:  Supported
    FCMOV:  Supported
    SSE2:  Supported
    SSE3:  Supported
    SSSE3:  Supported
    SSE4a:  Unsupported
    SSE41:  Supported
    SSE42:  Supported
    AES:  Supported
    AVX:  Unsupported
    CMPXCHG16B:  Supported
    LAHF/SAHF:  Supported
    PrefetchW:  Unsupported

Operating System Version:
    Linux 4.x (64 bit)
    Kernel Name:  Linux
    Kernel Version:  4.18.5-arch1-1-ARCH
    X Server Vendor:  The X.Org Foundation
    X Server Release:  12001000
    X Window Manager:  KWin
    Steam Runtime Version:  <Runtime disabled>

Video Card:
    Driver:  X.Org AMD Radeon(TM) HD8800 Series (PITCAIRN, DRM 3.26.0, 4.18.5-arch1-1-ARCH, LLVM 8.0.0)
    Driver Version:  4.4 (Compatibility Profile) Mesa 18.3.0-devel (git-aad501f15e)
    OpenGL Version: 4.4
    Desktop Color Depth: 24 bits per pixel
    Monitor Refresh Rate: 59 Hz
    VendorID:  0x1002
    DeviceID:  0x6811
    Revision Not Detected
    Number of Monitors:  2
    Number of Logical Video Cards:  1
    Primary Display Resolution:  1680 x 1050
    Desktop Resolution: 3046 x 1050
    Primary Display Size: 18.66" x 11.65" (21.97" diag)
                                            47.4cm x 29.6cm (55.8cm diag)
    Primary VRAM: 2048 MB

Sound card:
    Audio device: Realtek ALC662 rev3

Memory:
    RAM:  7970 Mb

Miscellaneous:
    UI Language:  English
    LANG:  en_US.UTF-8
    Total Hard Disk Space Available:  440864 Mb
    Largest Free Hard Disk Block:  86312 Mb
    VR Headset: None detected

Recent Failure Reports:

it's working for me now with Proton 4.2-3

Whitelist Request

• Name of the game to be whitelisted: OKAMI HD / 大神 絶景版
• Steam AppID of the game: https://steamdb.info/app/587620/

System Information

• GPU: GTX 760
• Driver/LLVM version: NVIDIA 440.44
• Distro version: Arch
• https://github.com/shoober420/linux-scripts/blob/main/home/shoober420/sysinfonvidia
• Proton version: 4.11-11

Works great out of the box!

Completed the game some time ago playing only on linux and it never crashed, both KB+M and Controller worked perfectly. Tested the game again on my System with Arch and my Laptop with Pop! OS and on both systems ran perfectly

The game is rated platinum on ProtonDB and the few crashing reports are probably related to low file descriptors on their distribution

On Proton 5.0-2 my controller is not detected.
It's a generic XBox controller, by PowerA.

Steam, and many other games, detects the controller just fine.
Will try on Proton 4.11 later on.
Apart from controller support, everything else just works.

If this is not the right place to report this problem, please correct me here, as this is my first time contributing to the Proton project. :sweat_smile:

Hello @tewald, that may be a general PowerA xbox controller + Steam Input issue (ValveSoftware/steam-for-linux#5353).

The controller is detected by steam client and big screen mode.
Native linux steam games work just fine too.
I'll try other Windows games and Proton versions and try to pinpoint the problem and open an issue on the correct project.

Thanks for the quick reply!

Tried running Okami HD with default settings in windowed mode using a Steam controller, whole system froze upon loding a new game, requiring a restart. Using the launch option PROTON_NO_ESYNC=1 %command% resulted in the same error. Specifying Proton 4.11-12 didn't help, nor did Proton 5.0-3.

Originally tested this game in 4.11.11, still working flawlessly in 5.0.4. Disable ESYNC still needs to exist to prevent crashing. All proton versions played using an Xbox controller. Probably worth a whitelist at this point.

Compatibility Report

• Name of the game with compatibility issues: Okami HD
• Steam AppID of the game: 587620

System Information

• GPU: RX 480 8GB
• Driver/LLVM version: Mesa 21.2.1-1 / LLVM 12.0.1-1
• Kernel version: 5.13.14-xanmod1-1
• Link to full system information report as Gist: https://gist.github.com/kode54/3ff952f39b407d6f806a6779838f5335
• Proton version: 6.3-6

I confirm:

• [ ] 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.

steam-587620.log

Symptoms

Game fails to start, crashing on startup. It never displays a window at all, and takes several minutes to finally crash.

Reproduction

1. Install game.
2. Configure system to use Proton 6.3-6.
3. Start game.

Further report, it doesn't accept any controller input whatsoever.

Originally tested this game in 4.11.11, still working flawlessly in 5.0.4. Disable ESYNC still needs to exist to prevent crashing. All proton versions played using an Xbox controller.

@kode54 Have you tried what was suggested a year ago?

It was apparently a kernel that was missing fsync support, and it was falling back on the broken esync.

This is working flawlessly on the Steam Deck, would be nice to have it whitelisted.

Hello, is anyone seeing an issue with this game and Proton 4.11 which would block it from being whitelisted?

Tested on Linux laptop (Nvidia graphics) and Steam Deck (AMD graphics). No issues at all without messing with the configuration.

On the deck, touch input causes the game to absolutely freak out its camera, and shove the brush in the bottom left corner. While not supporting touch natively compared to the switch release, emulating the mouse should work in theory, and yet it doesnt. Unsure if this is a deck issue, or a game issue.

I can't get controller input to work on this game on my Deck. I've tried both the DS4 and Steam Controller official configs, a regular gamepad (i.e., not a "Steam Input") config, and a number of community configs specifically for the Deck, and none of them work.

The game only responds to keyboard & mouse input for me.

I have the same issue as eyeonus - on Heroic (=Proton 7.0) under Ubuntu 22.04.
Is it that the game assumed its PC version would always use keyboard+mouse and the Steam compatibility layer is solving it for some users by translating joypad commands into kbm? And as such there is no controller setup menu inside the game? Heroic and Proton are not fantastic for that situation so I might try the Switch version instead. (update: Switch version works fine via yuzu with no other hw configuration changes - therefore I think it is that the PC version just lacks controller support)

I have the same issue as eyeonus - on Heroic (=Proton 7.0) under Ubuntu 22.04. Is it that the game assumed its PC version would always use keyboard+mouse and the Steam compatibility layer is solving it for some users by translating joypad commands into kbm? And as such there is no controller setup menu inside the game? Heroic and Proton are not fantastic for that situation so I might try the Switch version instead. (update: Switch version works fine via yuzu with no other hw configuration changes - therefore I think it is that the PC version just lacks controller support)

The game only has steam input native controller support, and was only released on steam, so I'm not sure what your issue is beyond you pirated the game or are trying to force it through heroic for some reason.

The game only has steam input native controller support, and was only released on steam, so I'm not sure what your issue is beyond you pirated the game or are trying to force it through heroic for some reason because heroic is Open Source.

I can't remember if Steam input is more complex than translating to kbm (in which case iirc this can be replicated in one of the older linux tools for xbox controllers - might just be xboxdrv). But I see this to be overreach since a retail outlet is also being a hidden software dependency, whilst in the process not actually functioning as expected (it seems) for many users. But that is philosophical. I suppose sometimes a Linux Proton problem might cast light on a Steam Deck Proton problem, but here it seems it's the original code (of a Windows release?) and not Linux's or the Steam Deck's emulation that is to blame.

I don't have this problem on most other Steam games, nearly always they pick up at least one of xbox, ps4 dualshock, or Steam Controller. So I wonder if the game's use of steam input for controller support has a bug - in which case it seems likely to be inaccessible to both Proton and what settings the end-user can change.

edit: PS3 version (2012) doesn't have this problem. Windows/Steam version (2017) does. Switch version (2019) doesn't.

Replying to https://github.com/ValveSoftware/Proton/issues/756#issuecomment-1777983564

The game uses steam input native and does not have fallback, it was never implemented. You must use steam input with this game. Steam input native is far more complex than the kbm to controller version you're thinking of. It's not a bug, it's functioning as intended. Someone would have to make a steam input native emulator for it to work without steam. It's also not overreach since Capcom chose to make it steam input only, not valve.

Launching the game in desktop mode has fixed the issue for me, I no longer have this issue in desktop scope or gamescope.

Hope that helps.

I've also got it working now using antimicrox - a simple controller-to-kbm translator