cspear opened this issue on May 10, 2008 ยท 59 posts
cspear posted Mon, 12 May 2008 at 10:22 AM
I've spent around half an hour digging around in the Material Room and I can't see any reason for the inconsistency described in previous posts, nor any way to fix the problem.
My conclusion is that SmithMicro have made a simple, probably unintended change to something in the way shaders are calculated that has a drastic effect on renders.
In other words, they screwed this up, and for reasons I can't begin to fathom this wasn't picked up during testing.
I am desperately disappointed.
Windows 10 x64 Pro - Intel Xeon E5450 @ 3.00GHz (x2)
PoserPro 11 - Units: Metres
Adobe CC 2017