Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Severe lag during tutorial in Armored Core 4 when WCB is enabled on Fedora #16044

Open
karmazogs opened this issue Sep 4, 2024 · 8 comments
Open
Assignees

Comments

@karmazogs
Copy link

Quick summary

When "Write Color Buffers" is enabled, upon reaching the second phase of the tutorial and turning around after the first test, the game drops from ~60 fps to ~20-30 fps. This doesn't seem to be a bottleneck as CPU usage is normal during the frame drops.

Details

No response

Attach a log file

RPCS3.log.gz

Attach capture files for visual issues

ac4 tutorial lag.tar.gz

rpcs3 performance monitor ac4

System configuration

OS: Fedora 40
CPU: AMD Ryzen 5 5600X
GPU: AMD Radeon RX 6700 XT
RAM: 16 GB

Other details

No response

@AniLeo
Copy link
Member

AniLeo commented Sep 4, 2024

Can you post the full performance overlay from both Write Color Buffers ON and OFF on the same scene? To have a proper performance comparison. As well as using uncapped FPS, to not be limited at 60.

@karmazogs
Copy link
Author

karmazogs commented Sep 4, 2024

Can you post the full performance overlay from both Write Color Buffers ON and OFF on the same scene? To have a proper performance comparison. As well as using uncapped FPS, to not be limited at 60.

The game does not like uncapped framerates one bit

WCB on
performance overlay wcb on

WCB off
performance overlay wcb off

@kd-11
Copy link
Contributor

kd-11 commented Sep 5, 2024

Enable the full dev overlay in the config file by setting "Debug Overlay" option to true. You can also find this on the debug tab if you have it enabled. A lot of text will appear on the top left of the screen with some internal stats.
That said, poor WCB performance on linux is expected though I've never seen it this severe. The real root cause is this: https://gitlab.freedesktop.org/mesa/drm/-/issues/89

@karmazogs
Copy link
Author

Enable the full dev overlay in the config file by setting "Debug Overlay" option to true. You can also find this on the debug tab if you have it enabled. A lot of text will appear on the top left of the screen with some internal stats. That said, poor WCB performance on linux is expected though I've never seen it this severe. The real root cause is this: https://gitlab.freedesktop.org/mesa/drm/-/issues/89

WCB on
image

WCB off, framelimit 60
image

WCB off, framelimit off
image

@kd-11
Copy link
Contributor

kd-11 commented Sep 5, 2024

While I see WCB introducing overhead it really shouldn't be this bad. Are you using the GPU for anything else in parallel? I can capture some RGP profiles later but that will take time as I'm busy with other tasks.

@kd-11 kd-11 self-assigned this Sep 5, 2024
@karmazogs
Copy link
Author

While I see WCB introducing overhead it really shouldn't be this bad. Are you using the GPU for anything else in parallel? I can capture some RGP profiles later but that will take time as I'm busy with other tasks.

Usually just Youtube and Discord I think.

@karmazogs
Copy link
Author

Also I should've specified I'm on the KDE Plasma spin of Fedora 40 if that's relevant at all. Asking around in other places someone mentioned offhand that it could be Wayland causing the issue? I'm not smart enough to figure any of this out on my own and I just want to know if it's something I did or something I can fix.

@atlrvrse
Copy link

I'm experiencing the same problems in For Answer too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants