LuxCoreRender Forums

Makes sense. Thanks, guys.

Thanks, Dade. I saw that -- a very nice feature, but not what I'm driving at. There are certain simulation workflows (e.g. calculating annual daylight levels near dynamic facades) in which it's useful to capture explicit intersection data. I imagine this would involve significant surgery on your end ...

True, end-of-path outputs are useless for compositing, which I assume to be the intent of LuxCore's AOVs. But they're quite valuable in certain types of non-image-forming analysis, for which Radiance is often used ( https://floyd.lbl.gov/radiance/rtrace.1.html ). It's atypical for high-level ...

Quick question about film outputs. Can AOVs like POSITION, OBJECT_ID, etc., be reported for the end of an eye path, or only for its first intersection?

Perfect. Thanks, Dade.

Ah, got it, thanks. I'd assumed the default value (1.5) would take effect.

Follow up question: What's the physical meaning of kr and kt? I assume kr is a multiplier that acts on the specular-reflection component (which is determined by IORs)? And kt acts on the non-reflected remainder? Just want to ...

Hi All,

Just started playing with LuxCore ... it's amazing :D. Thanks to the development team for all the hard work!

Quick question about glass. I tried creating a simple glass material and applying it to a sphere (foreground) and, well, I failed.
denoised.png

Material is defined as:
scene ...