Comment # 32
on bug 99418
from Michel Dänzer
(In reply to lei.pero from comment #31) > It's still odd behaviour, in both cases Chrome caps FPS to refresh rate (this > case 85FPS), Sounds like Chrome just has its own framerate throttling which works independently from sync-to-vblank. > but using DRI3 using mutter/clutter, for some reason it creates > continuous stutters, even tho FPS is the same and all other parameters are > equal. It really looks (when viewed live) as if FPS is not equal to refresh > rate. It's possible that the mutter framerate doesn't match the refresh rate (you can check by setting GALLIUM_HUD=fps for the mutter process), but it's also possible it's simply due to unfortunate interaction between the Chrome and mutter frame timings. > [...] it is still probably mutter/clutter configuration problem in the code > (since it happens only there), it doesn't follow configuration in .drirc as > other WM's. Not really. By setting vblank_mode=0, you're forcing mutter to run in a way it doesn't intend. If doing so breaks something, that can hardly be considered a mutter bug, and you get to keep all the pieces. :)
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
