Hi,
it seems that the pointer of a material didn't work.
The mesh with the pointer is rendered black.
I've attached a simple scene where you can see the problem.
2.5a and pointer a material
Forum rules
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
Please upload a testscene that allows developers to reproduce the problem, and attach some images.
Re: 2.5a and pointer a material
I assume "pointer" is some Blender related material alias stuff. B.Y.O.B. is out of the town for some days: it may be a good idea to open issue on GitHub.
Re: 2.5a and pointer a material
yes..it's the pointer node in Blender.
I've opened an issue on github.
I've opened an issue on github.
Re: 2.5a and pointer a material
Here is an idea for a workaround if you need it:
I had a look at the code to try and find out what happens, but didn't yet fully get to the bottom of it. A third material is exported with the correct settings as per the pointed material, but no name string (only the random number) as well as not used on an object. Instead the material is exported as matte with 0 brightness.
[All places in BlendLuxCore I could find where such a definition is made are not called. Does LuxCore have a matte-black fallback somewhere?] EDIT: Nevermind, I found this fallback in BlendLuxCore.
I had a look at the code to try and find out what happens, but didn't yet fully get to the bottom of it. A third material is exported with the correct settings as per the pointed material, but no name string (only the random number) as well as not used on an object. Instead the material is exported as matte with 0 brightness.
[All places in BlendLuxCore I could find where such a definition is made are not called. Does LuxCore have a matte-black fallback somewhere?] EDIT: Nevermind, I found this fallback in BlendLuxCore.
Re: 2.5a and pointer a material
I'm not sure why you would need such a node setup, but I have pushed a change that makes this possible.
Re: 2.5a and pointer a material
Actually you're right.. it was just for "scene materials organization". I had a material named "A" that had a initial setup and then I'd like to test how it should be using the material "B"...
I should make the same simply assign directly the material "B"...
Sorry for this...anyway..if it's "fixed".... good to know for the next silly material setups
Re: 2.5a and pointer a material
I have reverted the "fix" to this as it was causing other problems (viewtopic.php?f=4&t=2611&start=10#p25569).
The node setup causing problems (pointer straight into material output) is nonsensical anyway, so I will just leave it as non-working like before.
The node setup causing problems (pointer straight into material output) is nonsensical anyway, so I will just leave it as non-working like before.