clipka <ano### [at] anonymousorg> wrote:
> Am 07.07.2017 um 20:10 schrieb omniverse:
> > Cousin Ricky <ric### [at] yahoocom> wrote:
> >> See thread in p.b.i.  The scene uses two light sources, one to trace a
> >> cylindrical parallel beam through two prisms and across a room, and
> >> another, with media interaction turned off, to light the scene.  The
> >> latter light has a looks_like for what reason I don't remember.  (This
> >> was 12 years ago!)
> >>
> >> When the scene is rendered as an animation, the looks_like is omitted in
> >> frame 2.
> >
> > Don't know the reason behind it but simply making the looks_like sphere hollow
> > allows the photons to show.
>
> Well, /I/ know the reason behind it now ;)
>
> During refactoring for 3.7.0, a bug was introduced that may cause
> objects in the same CSG group to mess with each others' `hollow` flag,
> with the last object winning. In this case that happened to be the
> non-hollow `looks_like` object.

Much appreciation to you for finding that.

I hadn't thought of the looks_like being part of CSG if a lone object is used.

Wow, code reading is fun and confusing. Just before you answered to that I was
finally getting a look at both the 3.7 and 3.62 source for comparisons of what
might have changed, in particular the parse.cpp file, and I sure get lost fast.

I just wanted to see what parts looks_like dealt with, although I guessed it was
probably the object or hollow causing the trouble when conveyed to the parser
somewhere. I was thinking about the "children" parts and if that might be the
reason.
Please ignore me for my lack of certainty, clarity and definition there. I'm way
out of my league!

Anyway, thanks again for checking on that... both of you Christoph and Richard.

Bob

Post a reply to this message