[Bug 37424] Path of Exile: Graphical Glitches with GLSL Disabled

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=37424

--- Comment #12 from Sovyn <teddy5978 at gmail.com> ---
(In reply to Stefan Dösinger from comment #11)
> Nothing ARB shader related in that log. If the bug is what I suspect it is I
> don't expect it to show up in a FIXME log.
> 
> You may be able to see it in a +d3d,+d3d_shader,+d3d_draw,d3d_constants log.
> Check for wined3d_device_set_pixel_shader(NULL), followed by
> wined3d_device_set_pixel_shader(shader != NULL) calls that are not followed
> by "Loading constants" before the "done all GL drawing" line.

Stefan, thank you for the clues. I did a log file with the switches you
suggested. The output is very verbose at around 50MB output per second. There
are 33000 instances of the "wined3d_device_set_pixel_shader". I did not see
anything offhand with the not equal to (!=) pattern. I did look for a while but
nothing is apparent as the output is very extensive as mentioned. I'm probably
just too new at this.

Looking at the various sections in between the "Done all gl drawing" lines, I
do see some variation. Most sections do have the constants you mentioned.

Could you elaborate on what the "wined3d_device_set_pixel_shader(shader !=
NULL)" call line would look like in an actual log? For example, the
"wined3d_device_set_pixel_shader(NULL)" line you mentioned is actually
expressed thus in the log:

trace:d3d:wined3d_device_set_pixel_shader device 0x19a698, shader (nil).

All additional guidance is welcome and appreciated.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.