• 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 I want a generic building with a white roof

  • Thread starter Thread starter flytiti
  • Start date Start date
This wandered off-topic a bit...

Generally, you would not place an identical MDL, with an identical GUID, 3 times in a scenery using 'inline' model referencing. You would instead make a library object, and reference that GUID 3 times. (The problem could also be avoided by using a different GUID for each instance.)

In this case, the GUID was already used in OBX16150.bgl, so why make a new object usage with the same GUID in the first place?

Having the MDL referenced in the BGLComp code is usually reserved for one-usage objects. Multi-usage objects are properly put in a library. You should never re-use a GUID.


Dick
 
rhumbaflappy said:
This wandered off-topic a bit...
Click to expand...
To continue the wander...

rhumbaflappy said:
In this case, the GUID was already used in OBX16150.bgl, so why make a new object usage with the same GUID in the first place?
Click to expand...
The object might be geo-locked (here comes Jim) and need to be extracted from that file for use elsewhere.

IMO, the proper procedure would then be to issue the object a new GUID and place in whichever manor works best.

cheers,
Lane
 
Lane Street said:
The object might be geo-locked (here comes Jim) and need to be extracted from that file for use elsewhere.
Click to expand...

Actually that particular object isn't geolocked and could have been used straight away from OBX16150.bgl. In fact I placed the exported .mdl from the XML in my last post and checked with IS2 - OBX16150.bgl trumps the LEFL test .bgl and IS2 reports the library name as OBX16150.bgl. The buildings also appear correctly at KCOE with both bgls active.

I considered the duplicate GUID problem of course, I've been preaching duplicate GUIDs for 10 years, the problem is they don't always cause problems and that causes the casual developer to question the validity of the argument, "well I've done that before and it didn't cause the problem you're suggesting it will", this is a perfect example, see above. I thought half a page of explanation was enough, any more than that and a reply starts to sound suspiciously like the help files and becomes nearly as effective. I thought it easier and more effective to cross the duplicate GUID bridge when we got to it rather than try to ram it all down in one post.
 
You must log in or register to reply here.
Back
Top