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

MDL Objects

Thanks for you fast answer

Hi Arno
Hi Marcello,

That is new to me. As far as I know nothing inside the MDL controls the geo-locking. So I don't think that you can control it from within GMax.

Where can I find this GMax option? I don't think I have needed to use it.

Thanks for you fast answer to my question.

If i use a different GUID for my MDL that i have already used with the original GUID, then i could place the Object in a XML-File that contains <ModelData> and <SceneryObject> ?

This is my last question

Greets
Marcel
 
Hi,

If i use a different GUID for my MDL that i have already used with the original GUID, then i could place the Object in a XML-File that contains <ModelData> and <SceneryObject> ?

I am not sure if I understand the question.

Normally if you have already assigned a GUID to an object, there is no need to assign another one to it with another ModelData command. Only if the origional ModelData command was placed in a XML file that also contains placement code the object is geo-locked. In that case you can only call that GUID from the same area, else you can just reuse the old GUID without trouble.

You can also call this GUID from a file that contains ModelData commands, that will not make the origional object geo-locked. It is only geo-locked when it's own ModelData command is mixed with placement in the same file.

Assigning a new GUID to the same object is not a very good idea in general (see the discussions earlier in this thread).
 
Back
Top