search

ValveSoftware / Proton

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

Pharaoh Rebirth+ (441280) #7487

Open williamjcm opened 7 months ago

williamjcm commented 7 months ago

Compatibility Report

System Information

I confirm:

steam-441280.log

Symptoms

Game performance is lower than expected, with many framerate drops that slow the game down. Framerate rarely stays at 60 FPS, and can go as low as 25 FPS. Whenever a framerate drop occurs, it's sustained for several seconds, and will usually fluctuate between 30-ish and 50-ish.

Reproduction

Just get into the game and play.

simifor commented 6 months ago

@williamjcm this game should run better with the current proton experimental bleeding edge.

williamjcm commented 6 months ago

I tried the bleeding edge branch of Experimental, and while there seems to have been an improvement, it might also just be some random chance in regard to the framerate issues.

During the first boss fight of the game, which is just after the last save point I interacted with, I saw Steam's FPS counter hover around 40 FPS for most of the fight, with some very short (less than a second) jumps to 60 FPS here and there.

simifor commented 6 months ago

@williamjcm I didn't get sharp drops during the boss fight, the only one I saw in my limited testing was when using the healing station, but this also happened on windows. Could you say if setting echo high | sudo tee /sys/class/drm/card0/device/power_dpm_force_performance_level akes a difference for you?

williamjcm commented 6 months ago

Before I run that command, does it require a reboot to apply the change ?

simifor commented 6 months ago

Before I run that command, does it require a reboot to apply the change ?

It applies immediately, and you can set it back to auto with echo auto | sudo tee /sys/class/drm/card0/device/power_dpm_force_performance_level Lastly, if that still doesn't work, I also noticed that wined3d was working better on this game than the dxvk version from stable, which you can enable by adding PROTON_USE_WINED3D=1 before %command% (add it if you don't have it) in the game's launch parameters in steam's properties.

williamjcm commented 6 months ago

I tried both the power setting and forcing WineD3D, separately then together, and I didn't notice any improvement either.

joshas commented 1 month ago

Versions after Proton 7.0-6 introduced new regression, where not only game lags more, loading times (from main menu to in-game) take much longer. It seems that game actually freezes, as running game with wine-9.0 displays "application is not responding" message. Tested with various graphics settings, Radeon and integrated Intel GPU - same issues everywhere, so this probably not related to particular GPU.

kisak-valve commented 1 month ago

Hello @joshas, please add PROTON_LOG=1 %command% to the game's launch options, reproduce the regression, and attach the generated $HOME/steam-$APPID.log to this issue report as a file. (Proton logs compress well if needed.) Also, please copy your system information from Steam (Steam -> Help -> System Information) and the contents of Steam Runtime Diagnostics from Steam (Steam -> Help -> Steam Runtime Diagnostics) and put them in a gist, then include a link to the gist in this issue report.

joshas commented 1 month ago

Logs: steam-441280.zip System information: https://gist.github.com/joshas/56d0d666722643130ee27cf243ce7241 Steam Runtime Diagnostics: https://gist.github.com/joshas/52ccf31f0dfcc462f69e143bd113441e

Two other issues to note:

  1. There's a peculiar issue with gamepad: in configuration window selecting DPAD ("POV-ray" option) instead of analog stick for movement controls, seems to be working, as can be easily tested in preview window. But starting the game with DPAD enabled will end up sending continuous "UP" press to game, making it unplayable. Older Proton versions were displaying same behavior in settings, where DPAD would only point up. Probably some niche issue how game engine handles input and uses DirectInput libraries?
  2. After getting a game over game is taking screenshot of last screen and saving to disk in game directory /data/config/back.bmp . On Proton it fails and screenshot is always black. Could be related to Wayland limitations?

Both issues are occurring in other game, "Action Mogura", by same developer, built using same "Clickteam Multimedia Fusion 2 engine (referred to as "Mogura engine"). I already reported them to WineHQ Bugzilla: https://bugs.winehq.org/show_bug.cgi?id=53470 https://bugs.winehq.org/show_bug.cgi?id=53473

Note, that more recent games from same developers, built on newer versions of Clickteam Fusion engine ("Mogura Engine 2"), are working without any issues with Proton 9.0-2: