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

Adding Objects

Flugwerk

Flugwerk

Messages
111
Country
austria
Hi Arno,
It would be great to have the opportunity to import objects and add them to the already loaded list of objects.

Just an idea :idea:

Regards,
Heinrich
 
Hi,

That's a nice idea. I'll add it to the list. It would combine modelconverterx and library creator xml in some way.
 
I was thinking about adding an add and remove object option in the list objects form. Would that make sense?
 
Yes, absolutely, good idea.

The next step would be a tree-view in the main window, showing the object list as seen in the library creator ;-)

Regards,
Heinrich
 
Hi,

I prefer not to clutter the main window with too many addition views. So it will stay in an editor I think :)

The main difference between modelconverterx and library creator XML is that the last tool does not alter the mdl files. Modelconverterx does import the mdl files and when saving writes them again based on the internal representation.
 
Arno, when we can expect the next development release with this new feature?

Regards,
Heinrich
 
Hi,

Great! When adding an FS2004 object, is there the option to use the GUID value that GMAX creates in the accompanying XML file? That would ensure that the GUID values remain as I expect them (when combining objects from different libraries, for example).

Thanks,
 
Flugwerk said:
Arno, when we can expect the next development release with this new feature?
Click to expand...

It's available already. A new development release is made every night, as long as I changed some code the day before.
 
tgibson said:
Great! When adding an FS2004 object, is there the option to use the GUID value that GMAX creates in the accompanying XML file? That would ensure that the GUID values remain as I expect them (when combining objects from different libraries, for example).
Click to expand...

No, modelconverterx doesn't read the xml file. If you want to preserve the guid you would have to read the bgl file.

I don't really see the purpose of reading that xml file. This has been discussed before already. The guid is just a random guid. Just as modelconverterx assigns when you load a fs2004 mdl. So why would you need to use the one from the sample code?

If the object has been used in some library already it makes sense to keep the guid. But just after exporting from gmax I don't see it.
 
Hi,

I use the XML file as my "reference file" for the GUID of any given object.

Yes, I often rearrange or combine existing library BGL files. In those cases I want to keep the same GUID. But I'll just take the extra step of entering it manually, no problem.
 
For existing libraries just import the bgl file. That will keep all the guids as they are.

Maybe i can also add a xml importer. Then you could load the xml file as the basis. That would be a better approach than let the mdl file look for the xml.
 
Yes, with this new function you can. It's probably easier to load the existing bgl library and then add the mdl (not the other way around).
 
As I always have to check the Mdl with MCX (very convenient) I think would be better to add afterwards the object to the library directly. thanks Arno.
 
If you have the mdl loaded you can insert an entire existing library bgl as well. That will merge them. And then save as bgl again.
 
A truly helpful function indeed :)

to extend this topic just a bit, would it be possible to view the materials from all objects in that list? That would be a neat way to spot duplicate materials across many different MDLs.
 
You must log in or register to reply here.
Back
Top