search

ValveSoftware / Proton

Compatibility tool for Steam Play based on Wine and additional components
Other
24.4k stars 1.07k forks source link

Okami HD (587620) #756

Open Denommus opened 6 years ago

Denommus commented 6 years ago

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

``` Computer Information: Manufacturer: Unknown Model: Unknown Form Factor: Laptop No Touch Input Detected Processor Information: CPU Vendor: GenuineIntel CPU Brand: Intel(R) Core(TM) i5-6300HQ CPU @ 2.30GHz CPU Family: 0x6 CPU Model: 0x5e CPU Stepping: 0x3 CPU Type: 0x0 Speed: 3200 Mhz 4 logical processors 4 physical processors HyperThreading: Unsupported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Unsupported SSE41: Supported SSE42: Supported AES: Supported AVX: Supported CMPXCHG16B: Supported LAHF/SAHF: Supported PrefetchW: Unsupported Operating System Version: "Arch Linux" (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: steam-runtime-beta-release_2018-06-14 Video Card: Driver: NVIDIA Corporation GeForce GTX 960M/PCIe/SSE2 Driver Version: 4.6.0 NVIDIA 396.54 OpenGL Version: 4.6 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 120 Hz VendorID: 0x10de DeviceID: 0x139b Revision Not Detected Number of Monitors: 1 Number of Logical Video Cards: 1 Primary Display Resolution: 1920 x 1080 Desktop Resolution: 1920 x 1080 Primary Display Size: 13.54" x 7.64" (15.51" diag) 34.4cm x 19.4cm (39.4cm diag) Primary Bus: PCI Express 16x Primary VRAM: 4096 MB Supported MSAA Modes: 2x 4x 8x 16x Sound card: Audio device: Realtek ALC269VC Memory: RAM: 15962 Mb Miscellaneous: UI Language: English LANG: pt_BR.UTF-8 Total Hard Disk Space Available: 783372 Mb Largest Free Hard Disk Block: 121709 Mb VR Headset: None detected Recent Failure Reports: ```

BlazeKl commented 6 years ago

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

system info

``` 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: 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: ```

danny9484 commented 5 years ago

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

shoober420 commented 4 years ago

Whitelist Request

System Information

Works great out of the box!

kisak-valve commented 4 years ago

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

BlazeKl commented 4 years ago

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

tewald commented 4 years ago

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

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:

kisak-valve commented 4 years ago

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

tewald commented 4 years ago

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!

RovkirHexus commented 4 years ago

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.

Specs Computer Information: Manufacturer: Unknown Model: Unknown Form Factor: Desktop No Touch Input Detected Processor Information: CPU Vendor: AuthenticAMD CPU Brand: AMD Ryzen 5 1600 Six-Core Processor CPU Family: 0x17 CPU Model: 0x1 CPU Stepping: 0x1 CPU Type: 0x0 Speed: 3200 Mhz 12 logical processors 6 physical processors HyperThreading: Supported FCMOV: Supported SSE2: Supported SSE3: Supported SSSE3: Supported SSE4a: Supported SSE41: Supported SSE42: Supported AES: Supported AVX: Supported AVX2: Unsupported AVX512F: Unsupported AVX512PF: Unsupported AVX512ER: Unsupported AVX512CD: Unsupported AVX512VNNI: Unsupported SHA: Unsupported CMPXCHG16B: Supported LAHF/SAHF: Supported PrefetchW: Unsupported Operating System Version: "Manjaro Linux" (64 bit) Kernel Name: Linux Kernel Version: 5.5.2-1-MANJARO X Server Vendor: The X.Org Foundation X Server Release: 12007000 X Window Manager: GNOME Shell Steam Runtime Version: steam-runtime_0.20200204.0 Video Card: Driver: X.Org AMD Radeon RX 5700 XT (NAVI10, DRM 3.36.0, 5.5.2-1-MANJARO, LLVM 11.0.0) Driver Version: 4.6 (Compatibility Profile) Mesa 20.1.0-devel (git-740cb3d193) OpenGL Version: 4.6 Desktop Color Depth: 24 bits per pixel Monitor Refresh Rate: 143 Hz VendorID: 0x1002 DeviceID: 0x731f Revision Not Detected Number of Monitors: 2 Number of Logical Video Cards: 1 Primary Display Resolution: 1920 x 1080 Desktop Resolution: 3840 x 1155 Primary Display Size: 23.54" x 13.23" (26.97" diag) 59.8cm x 33.6cm (68.5cm diag) Primary VRAM: 8192 MB Sound card: Audio device: ATI R6xx HDMI Memory: RAM: 16027 Mb VR Hardware: VR Headset: None detected Miscellaneous: UI Language: English LANG: en_US.UTF-8 Total Hard Disk Space Available: 471332 Mb Largest Free Hard Disk Block: 352803 Mb
Zyneris commented 4 years ago

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.

kode54 commented 3 years ago

Compatibility Report

System Information

I confirm:

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.
kode54 commented 3 years ago

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

DanMan commented 3 years ago

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?

kode54 commented 3 years ago

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

dylanmtaylor commented 2 years ago

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

dylanmtaylor commented 2 years ago

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.

Bitwolfies commented 2 years ago

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.

eyeonus commented 1 year ago

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.

evild4ve commented 1 year ago

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)

Bitwolfies commented 1 year ago

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.

evild4ve commented 1 year ago

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.

Bitwolfies commented 1 year ago

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.

eyeonus commented 1 year ago

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.

evild4ve commented 1 year ago

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