LuxCoreRender Forums

I did not get around to implement IOR support for the glossy node yet. However, as far as I know the IOR is just an alternative way of specifying the specular color (or rather, brightness). In both cases, when you use specular color or IOR to specify the reflection brightness, the material will simu...

Dade wrote: ↑Tue Feb 13, 2018 11:40 am Camera invisible objects are another possible solution to the problem (probably better than non-intersectible area light).

If possible this would be enough for most use cases I think.
Of course it's a bit of a bad idea to add a new invisible, but very noisy area light

As Dade said.

I'm currently restructuring pyluxcoreforblender a bit so it currently can't be used with BlendLuxCore.
We are not in release phase, so it's perfectly normal for stuff to be broken (temporarily).
If you need a "stable" build, use the latest release.

Where's Fresnel on Glossy and/or node for mixing? Glossy has these options: https://wiki.luxcorerender.org/LuxCore_SDL_Reference_Manual_v2.0#Type:_glossy2 What do you mean exactly? A view-dependent mix factor like the Cycles "Blend" node? Currently LuxCore does not offer this, but I think...

Yes, sometimes I also wish we had a non-intersectible area light that is invisible to the camera (and sometimes also invisible in specular/glossy reflections).

They were added after the release of alpha4.

It looks to me like it helped because the error "module 'BlendLuxCore.utils.render' has no attribute 'find_optimal_clamp_value" is gone and the clamp value is computed again.

Dade wrote: ↑Sun Feb 11, 2018 4:27 pm Uh, isn't uvmapping3d what are you looking for ?

Maybe. I forgot it existed.
I'll test it.

Hi,

is there a reason why there's no "rotation" option for 2D mappings?
We can only scale and translate it.

Can this feature be added?

Try to remove the BlendLuxCore addon folder completely and then re-installing it.
It looks like you have some outdated python files in there.