[Bug 54693] New: Freedom Planet 2 performance is atrocious with near-zero hardware load
https://bugs.winehq.org/show_bug.cgi?id=54693 Bug ID: 54693 Summary: Freedom Planet 2 performance is atrocious with near-zero hardware load Product: Wine Version: 8.3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: virtuousfox(a)gmail.com Distribution: --- Created attachment 74203 --> https://bugs.winehq.org/attachment.cgi?id=74203 wine64 FP2.exe log When running Freedom Planet 2 v1.2.0 on LGA-2011/Xeon E5-2697/AMD RX580 under rolling-release openSUSE Tumbleweed it gets atrocious ~10 fps in levels and ~45 fps in menus with ~1% GPU load, despite being simple low-res 2D game. The executable is 32-bit d3d11 Unity-based app. I actually use wine-staging but I can't test vanilla now to see if its different. However, one interesting part is that enabling WINEESYNC tanks fps more than twice of even that: <5 from 10. With WINEESYNC=0 CPU load is mostly on single core to about 60-80% but with WINEESYNC=1 load is shared among all 24 CPU threads to be almost unnoticeable, yet performance is literal slide-show. Tested with wine's GL rendering and dxvk with same result, wine's vulkan renderer hangs at startup. In comparison, Dishonored 2, pretty visually taxing game, maxed out with same wine/dxvk settings gives buttery-smooth native 72 fps (OC 60 fps panel) with <80% GPU load. There is nothing obvious in what little logs it spews out and there seem to be no audio or visual glitches. I'm quite at a loss to figure out what might be the bottleneck. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54693 Zeb Figura <z.figura12(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12(a)gmail.com Keywords| |performance -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=54693 Predatory QQmber <virtuousfox(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://freedomplanet2.com/ | |demo --- Comment #1 from Predatory QQmber <virtuousfox(a)gmail.com> --- Demo build seems to be also affected. As such, it can be used for testing. I doubt that it's rendering-related since even forcibly running it with CPU rendering only barely increased CPU load while fps and look stayed the same. For fps counting I use either `GALLIUM_HUD_PERIOD=0.07 GALLIUM_HUD="cpu+GPU-load+gallium-thread-busy,.dfps+.dframetime,.dbuffer-wait-time;requested-VRAM+VRAM-vis-usage+mapped-VRAM+requested-GTT+GTT-usage+GFX-IB-size,GPU-shaders-busy+GPU-ta-busy+GPU-vgt-busy+GPU-sx-busy+GPU-wd-busy+GPU-sc-busy+GPU-pa-busy+GPU-db-busy+GPU-cp-busy+GPU-cb-busy;.dprimitives-generated+.dclipper-primitives-generated+.ddraw-calls,.dsamples-passed+.dps-invocations" VK_INSTANCE_LAYERS="VK_LAYER_KHRONOS_validation,VK_LAYER_MESA_overlay"` for Mesa or `DXVK_HUD=devinfo,fps,frametimes,submissions,drawcalls,pipelines,memory,gpuload,api` for dxvk. The FP2.exe should be started with '-popupwindow' option or aspect ratio will be screwy. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla