Comment=
# 2
on bug 96622<=
/a>
from Kai
(In reply to Nicolai H=C3=A4hnle from comment #1)
> Thanks for opening the separate report.
No need to thank me for that. It's easier for everybody this way. ;-) (Btw,=
I
marked bug 96602 as resolved yesterday, ev=
en though
<http://reviews.llvm.org/D215=
51> is not commited yet. That might have been a
bit rash. In case you need it open for tracking/remembering to ping D21551 =
if
needed, let me know and I reopen it.)
> Can you create an apitrace that shows the visual=
corruption?
Sure. You can find the trace in compressed form at
<http://dev.carbon-project.org/debian/mesa.bugs/96622/dfc.trace.xz>. Please
note, that you will need a password and user name to access the trace, since
it's ~ 1.2 GB in size even in compressed form (~ 2.6 GB uncompressed) and I
want to prevent needless downloads. According to my records you should alre=
ady
have working login credentials from a prior report/trace. If you need me to
reset the password, just let me know (other known Mesa developers wanting to
have a look at the file, can contact me for credentials by private e-mail).
The trace shows my graphics settings for the game at the beginning to allow=
you
to recreate the setup, should you gain/have access to the game.
The first sequence after the loading screen doesn't show a glitch in the tr=
ace,
even though I saw some white pixels on the balcony while recording.
The corruption from attachment 124647 [details] can be see=
n after the second loading
screen.
The trace was recorded with the same stack and game version as described in
comment #0.
Let me know, if you need anything else.