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

XML: What locks an object?

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,432
Country
netherlands
In the first version of the tree library I made, I had by accident included a few lines of placement code in my library. These stayed there after some testing. With this library it was impossible to call the objects using an API for example. I have now removed the placement lines (I never wanted them to be there).

But this also leads to an interesting question. Does including placement code in your library BGL cause FS to lock your objects for internal use in that BGL only? Is this maybe why some of the MS objects are locked?

Could somebody try to reproduce what I am saying here with his own library, to see if this theory is true? I would certainly gives us more understanding of how the XML libraries work.
 
Hi Arno.

I haven't looked at this in a while, but when we first examined the BGL code of the default objects, it appeared that MS did something similar to restrict objects to defined areas. I don't know if it is simply the placement, or if there is a bounding code that isn't included in our XML schema.

Dick
 
Hi Dick,

Good questions. Let's try to find out what it is.

From what I experienced with my library it seems only the placement code is to blame for locking them. But I would be very happy if someone else could reproduce these conclusions with his own library.
 
Back
Top