<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - switching vsync on and off in vkquake breaks TearFree"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109364#c24">Comment # 24</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - switching vsync on and off in vkquake breaks TearFree"
href="https://bugs.freedesktop.org/show_bug.cgi?id=109364">bug 109364</a>
from <span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
<pre>(In reply to tempel.julian from <a href="show_bug.cgi?id=109364#c22">comment #22</a>)
<span class="quote">> If we can't manage to find the root of the problem, perhaps automatically
> re-initializing TearFree after it detects failure would be a viable
> workaround?</span >
I'd like to get to the bottom of these issues first, then I'll think about
possible mitigation of similar issues in the future.
Please attach a log file from reproducing the problem with amdgpu.dc=0.
<span class="quote">> Btw: It may be "helpful" to switch the vsync setting several times in
> vkquake to provoke the problem, not just once.</span >
I've tried it several times.
<span class="quote">> The game also limits the fps by default to 72, I suggest using a value well
> above refresh rate (e.g. at least "host_maxfps 80" via the game's console or
> config for 75Hz).</span >
Are you saying you can't reproduce the problem with lower values?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>