• 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 alpha 02 release

Status
Not open for further replies.
Hi guys,

A little status update.

@Bert: I found the problem with your API macro and solved it now.

@Volker/Iain: when you have the compile problems with XtoMDL are you sure that your Windows is set to use the dot as decimal character? XtoMDL does not work correctly if you do not do this. If that is not the problem in your case, please let me know so that I can test further. But I could compile the API provided by Volker without trouble.

I also have an idea on how to implement reading files with multiple objects. I'll try to get that into the next alpha version as well.
 
arno said:
@Volker/Iain: when you have the compile problems with XtoMDL are you sure that your Windows is set to use the dot as decimal character? XtoMDL does not work correctly if you do not do this.
Click to expand...

Aaaargh, now you caught me :D Yes, I had the comma as decimal divider... changed it into the English style and everything worked ok.

BTW: First I ran into troubles since I hadn't recompiled the API files. ModelConverterX had compiled the "." of the API into "," in the XML with the earlier German settings. So in a prospective manual/wiki it should be noted that the regional settings have to be set to English before using ModelConverterX... for jerks like me :D

So, if you excuse me now, I have tons of APIs to convert... :cool:

Then I will betatest LibraryConverter XML, I suspect :D

Thanks for this brilliant tool, Arno

Volker
 
Hello Arno,

today I tried to use your model converter, without a result.

Under tools/options I wasn't able to select the path to x2mdl.exe, whatever I did, situation always ended with this:

mcer.jpg


so I said O.K., let's try to "fool" the proggy and made a folder that it was asking for, so the contents found here:

C:\Program Files\Microsoft Games\Microsoft Flight Simulator X SDK\SDK\Environment Kit\Modeling SDK\FSX_GmaxGamePack\Plugins,

were copied to suggested path - c:\zomaar\ergens\xtomdl.exe

Then I tried to convert some 6 different API's and I'm ending up with this screen every time:
mcerr.jpg


Running windows xp pro sp2+ .net 2 with all updates.
 
Hi Iain,

Ayrsimming said:
I can confirm having the dot as my decimal character.
Click to expand...

In that case, could you submit one of the objects that gives you trouble for debugging to me?
 
Hi Volker,

Vora said:
So in a prospective manual/wiki it should be noted that the regional settings have to be set to English before using ModelConverterX... for jerks like me :D
Click to expand...

Yes, this is something the manual should indeed say once I write one. But I am also looking to see if there is an option that allows me to compile with XtoMDL from my tool and that I can change the decimal setting temporarily only for the compilation. Then the user does not have to change anything. But I am not sure if that is possible.
 
Hi,

adr179 said:
Under tools/options I wasn't able to select the path to x2mdl.exe, whatever I did, situation always ended with this:
Click to expand...

The options dialog is not working yet. Maybe I should have disabled it, but I only mentioned it in the first post.

adr179 said:
Then I tried to convert some 6 different API's and I'm ending up with this screen every time:
Click to expand...

Sounds like the problem reported earlier in this thread with API macros that have multiple Areas. I have fixed this problem for the next version.
 
Hi Arno

I have attached X file for my test object, a simple box. This file, when compiled with XToMDL, produces 0kb .MDL file.

iain
 
Last edited:
Hi Iain,

I can compile your X file here without any trouble, so it seems to me that this might be an issue with how XtoMDL is configured on your PC or something similar to that.
 
I posted a new version that should fix the bugs reported here. So please give that version a try and use the new thread for new problems.
 
Status
Not open for further replies.
Back
Top