https://bugs.freedesktop.org/show_bug.cgi?id=90513
GitLab Migration User changed:
What|Removed |Added
Resolution|--- |MOVED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=90513
--- Comment #16 from Ilia Mirkin ---
Trying to replay this, I see the green splotches in other frames, while the
ones that were bad during my retracediff work out just fine. That will make the
remaining misrenders much
https://bugs.freedesktop.org/show_bug.cgi?id=90513
--- Comment #15 from Ilia Mirkin ---
And here are the diffs. src = gk208, ref = gt215.
https://people.freedesktop.org/~imirkin/traces/talos-diffs.tar
--
You are receiving this mail because:
You are the QA Contact for the
https://bugs.freedesktop.org/show_bug.cgi?id=90513
--- Comment #14 from Ilia Mirkin ---
Created attachment 124613
--> https://bugs.freedesktop.org/attachment.cgi?id=124613=edit
list of draws with bad results
I ran a diff (with retracediff.py) against nv50 (after fixing
https://bugs.freedesktop.org/show_bug.cgi?id=90513
--- Comment #13 from Ilia Mirkin ---
The shadow/brightness flicker should be helped by
https://cgit.freedesktop.org/mesa/mesa/commit/?id=154c0a42a23187c61ea0a1307198fae667398eba
Moving on to the red/green flickering...
https://bugs.freedesktop.org/show_bug.cgi?id=90513
--- Comment #11 from Ilia Mirkin ---
Interesting... same issues don't occur on nv50 (GT215). Need to try to disable
features one-by-one until we find which ext is causing some difference to be
happening.
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=90513
--- Comment #12 from Ilia Mirkin ---
Actually talos doesn't use any "new" features. So it must be something that's
just plain broken on nvc0... The trace replays fine on nv50.
--
You are receiving this mail because:
You
https://bugs.freedesktop.org/show_bug.cgi?id=90513
--- Comment #9 from Karol Herbst freedesk...@karolherbst.de ---
yeah I can confirm this.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=90513
--- Comment #8 from Ilia Mirkin imir...@alum.mit.edu ---
I got the demo, and even with GPU set to the lowest level, I see
lighting/texture mapping/_something_ errors. At the very first level in the
demo, if you walk towards the castle, and stand
https://bugs.freedesktop.org/show_bug.cgi?id=90513
--- Comment #4 from Gediminas Jakutis gedimi...@varciai.lt ---
(In reply to Karol Herbst from comment #3)
does enabling No Dynamic Lightning helps with the issue even on very high
gpu settings Like Ultra? Its a customize options for the gpu
https://bugs.freedesktop.org/show_bug.cgi?id=90513
--- Comment #5 from Ilia Mirkin imir...@alum.mit.edu ---
I've made no progress on this bug BTW; perhaps an avenue would be to generate a
super-low-resolution trace (i.e. minimum supported by the game... 320x200 or
640x480 or something) so that it
https://bugs.freedesktop.org/show_bug.cgi?id=90513
--- Comment #2 from Ilia Mirkin imir...@alum.mit.edu ---
Confirmed that I get redness coming in on that draw on my GK208, whereas it's
fine on i965.
There are a few awkward things, but nothing completely ridiculous:
1. 4096x4096 srgb dxt1/5
https://bugs.freedesktop.org/show_bug.cgi?id=90513
--- Comment #1 from Gediminas Jakutis gedimi...@varciai.lt ---
In the trace in the OP, as an example of an offending call:
on frame 1950, on call #2160519 the ground gets painted red.
--
You are receiving this mail because:
You are the QA
13 matches
Mail list logo