On Montag, 17. Juli 2017 16:26:18 CEST Henri Verbeet wrote:
Quite frankly, I think those bug reports are questionable to begin with. The level of analysis seems to be "I saw a FIXME", without any reasoning how that's related to any negative effect in the application.
There are some bugs, blocked by the missing opcodes right now. It also sound reasonable that, if the interpolation for shaders is not working as expected, it results in graphical artifacts.
There are many other bugs, much more critical with more effect, yes. But: The wine source is something new to me. Implementing this two opcodes is a task where i know what the opcodes should do, and how to do that. As there is a very straight forward translation to GLSL, it is not much afford to write high performance translation functions. So, that's the reason why i decided to pick these two bugs.
You could use shader_glsl_nop() as handler to make the FIXME go away, but WINEDEBUG=-all would do that without having to touch any source code.
An what is the idea behind that? It does not fix the problem, it is only hidden.
Phrased differently, what is the problem you're *really* trying to solve? The FIXME may not have anything to do with it.
First of all, i want to find my way in this pile of code called wined3d ;) An if the graphical glitches i encounter in some games with this fixme messages could be fixed, great! If not: Also great.
--- Thomas