- Messages
- 126
- Country
Hi Arno,
I ran into another problem using the material templates in MCX. May it be that something changed in the way how texture file name information is handled in the templates?
In the past, I made a material template from an existing material and if I'm correct, texture files names had not been put into the template?! When I applied a material template, all texture files name of the current object have been kept and only the diverse values changed according to the template, which was perfectly good that way.
Now with the recent MCX versions, when generating a template from an existing material, it also transfers the texture file name(s) into the template. This results in current texture files names being overwritten as soon as one applies the template.
I then deleted the texture filename information within the template (see image), but the result is that this "NULL" value is then being transfered to the object and the diffuse texture filename of the current object is completely gone.
From my perspective it would be perfect if the "texture" properties (Diffuse, Fresnel, Emissive, Bump, etc) would behave like this:
If a texture name is specified within the template, MCX overwrites the corresponding value of the current material the template it is applied to.
If a texture name is blank (NULL) in the template, MCX keeps the given texture name of the material it is applied to.
Hope this makes sense?!
Cheers, Volker
I ran into another problem using the material templates in MCX. May it be that something changed in the way how texture file name information is handled in the templates?
In the past, I made a material template from an existing material and if I'm correct, texture files names had not been put into the template?! When I applied a material template, all texture files name of the current object have been kept and only the diverse values changed according to the template, which was perfectly good that way.
Now with the recent MCX versions, when generating a template from an existing material, it also transfers the texture file name(s) into the template. This results in current texture files names being overwritten as soon as one applies the template.
I then deleted the texture filename information within the template (see image), but the result is that this "NULL" value is then being transfered to the object and the diffuse texture filename of the current object is completely gone.
From my perspective it would be perfect if the "texture" properties (Diffuse, Fresnel, Emissive, Bump, etc) would behave like this:
If a texture name is specified within the template, MCX overwrites the corresponding value of the current material the template it is applied to.
If a texture name is blank (NULL) in the template, MCX keeps the given texture name of the material it is applied to.
Hope this makes sense?!
Cheers, Volker
Last edited: