Okami HD (587620) #756
Comments
|
I don't want to open a new issue so I will post the log here EDIT: the game works in Wine-staging + DXVK + Esync system info
|
kisak-valve
added
the
Game compatibility - Unofficial
|
it's working for me now with Proton 4.2-3 |
kisak-valve
changed the title
Whitelist Request
System Information
Works great out of the box! |
|
Hello, is anyone seeing an issue with this game and Proton 4.11 which would block it from being whitelisted? |
|
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 |
kisak-valve
added
Whitelist Request
|
On Proton 5.0-2 my controller is not detected. Steam, and many other games, detects the controller just fine. 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. 😅 |
|
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. 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 SpecsComputer Information: Manufacturer: Unknown Model: Unknown Form Factor: Desktop No Touch Input DetectedProcessor Information: Operating System Version: Video Card: Sound card: Memory: VR Hardware: Miscellaneous: |
|
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
System Information
I confirm:
SymptomsGame fails to start, crashing on startup. It never displays a window at all, and takes several minutes to finally crash. Reproduction
|
|
Further report, it doesn't accept any controller input whatsoever. |
@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. |
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. |
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. |
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. |
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 |
Basic info:
Arch Linux
Kernel 4.18.5
Proton 3.7-3
Intel Core i5-6300HQ @ 4x 3.2GHz [58.0°C]
GeForce GTX 960M
15962MiB RAM
Full info
The text was updated successfully, but these errors were encountered: