Hi,
I was trying to convert a scene done with the old addon to the new one, and noticed that it did not work as expected, i.e. the same nodes produce a different output.
I was wondering if this is something to be expected because of internal differences between the old an new addon...
Btw this how I realized what described here, then fixed:
viewtopic.php?f=5&t=9&p=982#p982
Applying rotation in the two cases also leads to totally different results, and in my opinion the old one is what one would intuitively expect.
Here is the output obtained with two test scenes (if needed, I can attach .blend files).
Different texture / 3dmap behaviour between old and new addon
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: Different texture / 3dmap behaviour between old and new addon
Please don't mind about this: I looked again and realized that it is just the scale that is applied inversely...
Re: Different texture / 3dmap behaviour between old and new addon
But what is the right scale? Old or new?
If I raise the scale value I'd expect the texture to get larger, so the LuxBlend way is correct and the new addon is wrong.
I'll correct it.
If I raise the scale value I'd expect the texture to get larger, so the LuxBlend way is correct and the new addon is wrong.
I'll correct it.
Re: Different texture / 3dmap behaviour between old and new addon
I also think so... but if I'm not misunderstanding something else, the standard behaviour in blender is the new one, i.e. increasing scale shows more of the texture on the object.
EDIT: it turns out that Blender has several scale values and mapping types, and using scale in each of them has different effects.
When "Texture" is selected and scale is increased, behaviour is like in Luxblend.
On the other hand, when "Point" is selected, behaviour is like in BlendLuxCore.
Also, using the scale value that appear directly in texture properties (not in mapping) is like in BlendLuxCore.
Sorry if this is a bit misleading, actually I have almost always used Blender with Lux, so I don't know so much about Cycles for instance...
EDIT: it turns out that Blender has several scale values and mapping types, and using scale in each of them has different effects.
When "Texture" is selected and scale is increased, behaviour is like in Luxblend.
On the other hand, when "Point" is selected, behaviour is like in BlendLuxCore.
Also, using the scale value that appear directly in texture properties (not in mapping) is like in BlendLuxCore.
Sorry if this is a bit misleading, actually I have almost always used Blender with Lux, so I don't know so much about Cycles for instance...