<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - vsync in Vulkan applications doesn't work correctly with both radv and amdvlk" href="https://bugs.freedesktop.org/show_bug.cgi?id=105316#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED WONTFIX - vsync in Vulkan applications doesn't work correctly with both radv and amdvlk" href="https://bugs.freedesktop.org/show_bug.cgi?id=105316">bug 105316</a> from <a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> Michel Dänzer</a> <pre>(In reply to tempel.julian from <a href="show_bug.cgi?id=105316#c4">comment #4</a>) I'm sorry, but you're just getting lucky with radeonsi. With Firefox, maybe the tearing could only occur in the title bar / toolbar area. If you can't find a satisfactory compositor setup, try TearFree. Those are your options for avoiding tearing with any reliability. > Would it be an option to suggest that amdvlk/radv explicitly make use of > page flipping instead? They can't do that. They can only not explicitly prevent page flipping, but radv already doesn't do that AFAIK. It can only make a difference in fullscreen anyway. Another possible reason that Vulkan might work less well is if the Vulkan drivers use MSC targets which have already passed, and/or use the PresentOptionAsync flag for PresentPixmap requests. That would have to be addressed in the Vulkan drivers or possibly the applications themselves; the Xorg driver is just doing what it's asked.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>