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.
Any time. I have a suspicion that anything coming from an OSL map doesn’t work in a CoronaMtl bump slot either, but I gotta test this some more and see if it may be easily circumvented somehow.
Bump should work in general, I’ve tested this. At some point OSL bump was way weaker than other standard maps, so you may have to crank up bump to see it. then again, I couldn’t see it happen later when 2019 was rolled out.
So… By default something IS wrong with the bump. It works with BumpConverter though.
This is just a sphere with the default OSL_Rivets shader, with the Bump output plugged into the material’s bump slot.
(Never mind the lighting differences, couldn’t be bothered so rendered Arnold with default lights… )
Well… It does work with Vray. And even with other plugins with pluggable maps like ForestPack. So I wouldn’t just outright assume it’s an ADSK problem by default.
I have a suspicion that anything coming from an OSL map doesn’t work in a CoronaMtl bump slot either, but I gotta test this some more and see if it may be easily circumvented somehow.
)