• 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.

FSX changing GUID

robystar

robystar

Messages
5,214
Hi,

Unless I am mistaken, the latest development release does not let me change the GUID anymore.
I change the GUID (without changing the name), export and reload the mdl and the new mdl has the same old GUID again. I do not have to change the name each time as well, do I?
 
ModelconverterX has an inbuilt "safety feature" that will not reassign a GUID if one exists in the file you are writing to.

Write to a different filename.

(and yes, I was unaware of this too)
 
Thanks.
In the meantime I found out that changing name and GUID solves the problem.
Did not know about the built in safety feature.
 
But in the end, the problem I encountered was due to something completely different:
- MCX finds the textures where ever you make it look. I had some textures prepared but they were still in the project file and not in the static object library/texture. MCX found them but FSX did not, the object did not show up and I kept wondering how come it did not.
The above just for info.
 
Hi,

Changing both the name and the GUID should not matter, if you export to the same MDL file it will use the GUID found in that MDL file.

However if you change the name, you get another default name when exporting...

Maybe I should make this safety feature on option, but it was build in to prevent changing the GUID by accident.
 
Hi Arno,

No, it is all right. Leave the safety on. It is just that I start to run out of names when experimenting with the textures:).
As I said, the problem was that, although the mdl showed the textures, MCX had, I think, pointed the texture path to the project file texture and did so in the compiled mdl as well. The project file not being in FSX, FSX could not find the textures. Hope you understand what I am trying to explain.
 
Hi,

In the MDL files there is no texture path at all. The MDL files only store the texture filename. They look for these files in the texture folder belonging to the scenery folder where the BGL is and in the main texture folder.
 
Perhaps a little warning box when the "safety" feature is used ... or a Confirm box then.

I don;t think you should be able to switch it off in the options panel.

It is a good idea.
 
Hi again,

Took me a while to digest what you were saying, Arno.
Could it be then that because the object had only one (diffuse) texture sheet in the static object/texture folder and the night texture sheet was not there, might have prevented the object from showing up? In other words, if a night texture is given to the object, but not found, the object does not show?
Sounds improbable but you never know?
(MCX compiled fine, no warnings on export except when importing the MDL again, MCX warned me the night texture could not be loaded. Deleting the night texture entry solved the problem.)
 
Last edited:
Hi,

Yes, if you have a missing texture (for example night texture) that can result in the object not showing in FSX. You always need to make sure all textures are there.
 
arno said:
Hi,

Yes, if you have a missing texture (for example night texture) that can result in the object not showing in FSX. You always need to make sure all textures are there.
Click to expand...

Here's another oddity to note. If you have a "bump map" in the FSX Material, but it is missing in the texture folder...

...in the sim the diffuse color texture will appear, but the shading will be inverted... :yikes:
 
You must log in or register to reply here.
Back
Top