• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Another MCX Material Template Issue/Question

Messages
122
Country
germany
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.

2019-04-27.png


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:

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
30,632
Country
netherlands
Hi,

The handling of texture files changed a few months ago, so probably this is a result of that. I'll have a look and see what I can do to make it work.
 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
30,632
Country
netherlands
Hi,

The next development release will contain a change where the textures are excluded again when you make a new material template from an existing material.

With the current build all you have to do is remove the property from the template. Just removing the texture name is not enough, you need to select the entire property and then press the "remove property" button to remove it from the template. Then the texture is not affected.
 
Top