<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Rendering errors when running dolphin-emu with Vulkan backend, radv (Super Smash Bros. Melee)" href="https://bugs.freedesktop.org/show_bug.cgi?id=103852#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Rendering errors when running dolphin-emu with Vulkan backend, radv (Super Smash Bros. Melee)" href="https://bugs.freedesktop.org/show_bug.cgi?id=103852">bug 103852</a> from <a class="email" href="mailto:benclapp55@gmail.com" title="Ben Clapp <benclapp55@gmail.com>"> Ben Clapp</a> <pre>It's worth noting that since originally reporting this bug, I've switched from GNOME3 to using Cinnamon for my desktop environment. While the GNOME3 bug I mentioned in the aside clearly went away after this change (the screen stopped freezing for 1-2s every time I opened a right-click menu, which simply should not be happening on a TR 1950X CPU), the issue with unusual frame drops to around 30FPS that are not reflected by a drop in the FPS indicator in dolphin persists nonetheless. It seems like this is an issue related to frame presentation, but where exactly the issue lies is unclear. That the issue occurs on both GNOME3 with Wayland and Cinnamon with X suggests the issue may be unrelated to the display server and/or compositor. I don't observe this problem when using other (3D/non-3D) applications (in a game engine I wrote myself in OpenGL, I can get a smooth 120FPS, nor do I see this frame presentation issue when using citra-emu or other applications), so it seems this frame presentation issue is unrelated to radv, and thus it might be worth opening a separate ticket to further investigate. The fact that the issue seems to occur suggests an issue with dolphin itself rather than a mesa/graphics driver issue, however the issue isn't present when using NVIDIA closed-source drivers, so it's hard to determine where the problem lies just looking at the symptoms.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>