<div dir="ltr">Handling it earlier means we get correct flat ngon normal support.<div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 11 December 2015 at 22:10, Brecht Van Lommel <span dir="ltr"><<a href="mailto:brechtvanlommel@pandora.be" target="_blank">brechtvanlommel@pandora.be</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Fri, Dec 11, 2015 at 9:55 PM, Mike Erwin <<a href="mailto:significant.bit@gmail.com">significant.bit@gmail.com</a>> wrote:<br>
> For the GL_FLAT task do you mean the screen space derivatives in fragment<br>
> stage? I think it's better handled earlier in the pipeline, by using flat<br>
> interpolation and per-primitive normals. There needs to be some agreement<br>
> between a flat shader and the mesh data feeding it to get the right results.<br>
<br>
</span>I think that if we can handle it in the fragment shader with<br>
derivatives, that would be the simplest solution? What would be the<br>
benefit of handling it earlier in the pipeline?<br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
Bf-viewport mailing list<br>
<a href="mailto:Bf-viewport@blender.org">Bf-viewport@blender.org</a><br>
<a href="http://lists.blender.org/mailman/listinfo/bf-viewport" rel="noreferrer" target="_blank">http://lists.blender.org/mailman/listinfo/bf-viewport</a><br>
</div></div></blockquote></div><br></div>