<br><br>Since we are naturally going for a complete workflow that is node related I don't see usefull the shader at rendertime but... When we don't use any kind of real life plate we would still use the distortion to feel our picture more real. in that case would be cool to store somewhere some preset of distortion data to use it.<br>
<br><br>Il giorno martedì 4 ottobre 2011, Matt Ebb <<a href="mailto:matt@mke3.net">matt@mke3.net</a>> ha scritto:<br>><br>><br>> On Wed, Oct 5, 2011 at 7:55 AM, François T. <<a href="mailto:francoistarlier@gmail.com">francoistarlier@gmail.com</a>> wrote:<br>
>><br>>> Gray flow : <br>>> it could be use when you are not planning on doing much compositing at the end or very thigh schedules :p. <br>>> I guess this would use some sort of Lens Shader in the render engine (pretty much like did LaMaison porting 3DEqualizer lens model to MentalRay for XSI <a href="http://www.alamaison.fr/3d/lmWarpDistort/lmWarpDistort.htm">http://www.alamaison.fr/3d/lmWarpDistort/lmWarpDistort.htm</a>)<br>
><br>> Honestly, I wouldn't even bother talking about this case. Lens distortion should be done in comp - coding resources will be better spent on implementing reliable overscan rendering with proper implementation of separated display windows/data windows throughout the pipeline.<br>
><br>> Matt<br>><br><br>-- <br>Francesco Paglia<div>Vfx and Production Supervisor</div><div><br></div><div>mobile +39 347.82.12.473</div><div><div>e-mail <a href="mailto:f.paglia.80@gmail.com" target="_blank">f.paglia.80@gmail.com</a></div>
</div><div><br></div><br>