On 5/13/19 1:56 PM, Norbert Kern wrote:
> "Jasper" <nomail@nomail> wrote:
> OK, this doesn't have anything to do with radiosity - so I agree on floating
> point precision issues as cause...
Is this still true for you with recent v38 releases?
I'd captured the case(s) you posted a couple years back - my notes say
in 2016. I wasn't able to run what you posted directly on my little
machine, but a cut down scene was fixed when I tested a v3.71 branch
March 17, of 2017.
Post a reply to this message