Comment # 2
on bug 102885
from Thomas J. Moore
(In reply to Samuel Pitoiset from comment #1) > Can you record a trace with apitrace that reproduces the issue? I could, I guess. I've never used the tool before, though, and have no idea how to trim it to the relevant part. I can't attach a 179MB trace file (109M compressed). I tried trimming to just the relevant region(s), but it's screwy at best, and mostly garbage in the replay, I doubt it's useful. > If not, which games are affected? What Wine version? Is CSMT enabled? I dunno. I erased my notes after I discovered at least 4 broken games; at that point, I realized that these problems only started around the later tests, where Mesa had been auto-updated to 17.2-some rc by my regular system updates, so I stopped blaming wine and tried reverting Mesa instead. The only ones I still remember are KOTOR (because it was worst) and Chains of Satinav. The attached picture is from the former; I test the presence of the bug using the latter, because KOTOR often has (unrelated) trouble starting up. Note that neither game shows this problem all the time: Satinav only shows it in the cursor when the cursor is over a selectable area, and KOTOR only shows it at certain viewing angles (I don't really know what the difference is). Both, and others that had issues, displayed brief flashes of dot grids at various other times as well. I currently use Wine 2.0.2, 2.15, 2.15-staging, and with/without gallium-d3d9. I can assure you that I tried all combinations of the above when I discovered it didn't work normally. 2.0.2 doesn't use csmt by default, and 2.15 does, so apparently csmt doesn't make a difference.
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
