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

How to integrate two tools?

arno

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,536
Country
netherlands
On the forums it has often been mentioned that Library Creator XML and ModelConverterX should be merged. I agree that it would make sense to integrate these two tools, since they are often used together.

But then the next question is how would you do that? I have been thinking about this a bit and I am not sure yet what the best approach would be. So therefore I am starting this thread to see what YOUR expectations of such an integration are.

So please let me know how you imagine that these two tools will work together in the future!
 
To get the discussion started, let me post some of my own ideas:

  • It should remain possible to use Library Creator XML stand alone to make a library of MDL files you made with another tool
  • From ModelConverterX it should be possible to export objects directly into a library BGL file
  • It would be nice if the tool could also load libraries directly from BGL files, in case you have lost the XML source

Let me know what your thoughts are. Did I miss something important? Or do you disagree with something?
 
I find the use of both programs separately very easy.

In fact, I also use MCX in parallel with SAMM.
 
Upside down?

Hi Arno,

thank you very much for requesting our ideas. Yes, it would be perfect to have these great tools working together more closely.

I even would think about a Library Manager to be the "main" application containing more global project information with different objects inside and MC as some kind of an internal object editor. MC could be called by double clicking an object to get a closer view of an object or to create a new one.

Well, to be honest I get a bit dizzy, when I think about the time it would need to be implemented and I'm not sure, if it would be worth finally, but that could be a long-term target to have in mind.

Also, it would be great to have a internal (macro) recorder, which could record action(s) on one object to be easily transferred to an other objects.

Would be nice to hear your feedback on this....

Thanks again for these great tools. I like working with them very much as they are. We have talked about it often times. Both applications are well designed and very helpful and effective in practice. They offer the most valuable tools for daily work ....

Markus
 
Arno,...

I can see how integrating the two would be a nice idea and all... but I would still like the flexibility... of when the mdls get placed into a library or not... with ADE were able to use the mdl files (not in a Library) as is. Maybe, give the option upon exporting:

1) a choosen Library being added/created to or mdl replaced within the Library(mdl file still created and placed in the chosen folder).

2) same as above,... but no mdl file created separately.

3) library bgl file not created or edited... just a mdl file exported (as currently done).

Just my thoughts :D.
 
I can't think of any advantage (for me) in combining the two. It's easy enough using them both seperately and I'm happy to keep doing that.
 
In terms of work flow, there seem to be two main scenarios.

1. Editing existing models, altering attachpoints / materials etc prior to compiling. (Library creator --> Modelconverter --> Library Creator)

2 Using ModelconverterX as a conduit ("Sketchup" or similar --> ModelConverter --> Library CreatorX

It would seem adequate integration would be achieved if the following functions were implemented:

A. In Library Creator ---> "Open in ModelconverterX" Button (This would open the mdl file for the selected entry in MCX, allowing changes and saving) Once saved, you would return to the Library Creator Window.

B. In ModelconverterX --) "Send to Library Creator XML...." Button opens list of Library Creator's last 5 opened xmls. Once a target library is chosen from the recent list the MDL is added to the selected xml, and Library Creator GUI is opened.

(other functions, since we're on the topic!)
c. Shell extension for Library Creator, to right-click a MDL file in the windows file explorer and add to (5 most recent) Library Creator libraries ... in a similar vein to the proposed "Send to ..." function

d. Immedite flagging / detection of duplicate GUIDs in the list when a model is added to a library in Library Creator, and a slightly more "friendly" message than the Bglcompiler gives - explaining which entries are in conflict.

e. Some sort of thumbnail / preview in Library creator itself (nice but not necessary)

It would seem that the two programs could "integrate" without things becoming two messy, just with A and B above.
 
Last edited:
Hi,
I think both of them are great and useful tools. We are very lucky to have them now and you can keep them separate. I'm sure you'd prefer spend your time on new projects.
 
I think you will find that people have a preferred work flow that they feel comfortable with and that combining the two to the satisfaction of all will be difficult to say the least.

With SAMM being recently added to the mix combining Library Converter XML with ModelConverterX and having it work easily with SAMM could be asking a little too much.

Perhaps, as stated earlier, a button that jumps from one program to the other (as in the old Photoshop to ImageReady button) might represent the best solution.

Regards, Mike Mann
 
Hi,

Thanks for all the input until now.

I agree with the general opinion that the tools should remain flexible. The tools should fit your workflow, not force you to use a different workflow. So if I make changes I will make sure that the end result remains flexible.

I like the idea to make links between the two programs by allowing one to start the other with some arguments.

The idea of integrating the tools would mainly be to make it easier for new users. Now you have to learn loads of tools to be able to make some simple scenery. If in that workflow the amount of steps could be reduced I think it would be better.
 
Hi Arno:

Many thanks for all the wonderful functionality you have built into MCX thus far. :o


I posted some additional ideas related to batch conversion of multiple objects / legacy object libraries and mapped textures with output to scenery object libraries or single 'geo-locked' BGLs (which you may already have considered, perhaps) ...in the context of this thread: :idea:

http://www.fsdeveloper.com/forum/showthread.php?p=147963#post147963


Hope these ideas help make MCX even more outstanding ! :)

Regards,

GaryGB
 
Last edited:
You must log in or register to reply here.
Back
Top