1
[Max] Resolved Bugs / Corona can't interpret OSL 'screen' space properly
« on: 2018-09-01, 22:42:42 »
So, in 3dsmax 2019 (obviously) when you're using OSL shaders, you have several spaces available such as 'raster', 'world', 'object' and 'screen'.
I was trying to write a shader which maps an image from edge to edge in screen space and couldn't seem to do it, until I tried a different renderer and realized my shader was good all along, and it was Corona mishandling it.
To reproduce: Plug a named space node into a bitmap lookup, and set the space to 'screen'. Plug the bitmap into any kind of material and render with Corona VS any other renderer. I tested Arnold, Scanline and Vray, which all render it correctly.
Test video with Arnold:
https://drive.google.com/open?id=11prmlt8SAwfL0-S5S4K41saW4pUlp2jg
Test with Corona:
https://drive.google.com/open?id=1naitThKPvlPSSk6R1mwUES0gwxZ6bRfv
I was trying to write a shader which maps an image from edge to edge in screen space and couldn't seem to do it, until I tried a different renderer and realized my shader was good all along, and it was Corona mishandling it.
To reproduce: Plug a named space node into a bitmap lookup, and set the space to 'screen'. Plug the bitmap into any kind of material and render with Corona VS any other renderer. I tested Arnold, Scanline and Vray, which all render it correctly.
Test video with Arnold:
https://drive.google.com/open?id=11prmlt8SAwfL0-S5S4K41saW4pUlp2jg
Test with Corona:
https://drive.google.com/open?id=1naitThKPvlPSSk6R1mwUES0gwxZ6bRfv