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

ModelConverterX Object format

arno

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,344
Country
netherlands
While debugging an issue in ModelConverterX I had the need to compare the internal representation of the objects in detail. So I decided to write some code so that I can export this representation to a file and then compare those two files.

But since I thought it might be useful for users as well to store the internal representation of the object to file, I have added this functionality now to the development release. You will see a new file format, ModelConverterX Object (MOB), in the import and export dialogues. This format will export the entire internal representation of your object. So if you want to save your work, without exporting to a flight simulator format, you can use this format as well now.

There even is an option to also embed the textures of the object in the same file. This can be useful if you for example used the Drawcall Minimizer to create new textures, but you have not yet saved them to disk afterwards. In the MOB format these new textures can be stored internally.

Two notes of warning:

  1. I do not plan to ensure backward compatibility of the MOB format over different versions. So this file format is really intended to store an object and then import it with the same version of ModelConverterX. You might not be able to import a MOB file that you saved a year later though.
  2. I think I have implemented all attributes of the internal representation to the MOB format, but if you found something that is lost on export or import, please let me know.

Continue reading...
 
You must log in or register to reply here.
Back
Top