View Full Version : ModelConverterX alpha 02 release
Here is an new build of the ModelConverterX tool. Please refer to the announcement (http://www.fsdeveloper.com/forum/showthread.php?t=6591) of alpha 01 for some more background information on how to use it.
In this new version the following things have been changed:
Better error handling, so a more useful error message should be produced now (or at least useful for me during debugging the problem).
Fixed a problem that some API macros got in an endless loop while loading them.
Improved the way texture files are searched for the 3D preview as this could result in crashes as well. The way is still not perfect though, the tool will go a maximum of three levels up from the folder where your API macros is and then search down for the texture file. In future versions I will probably introduce a search path to make this more efficient.
Added more SCASM commands that are now recognised correctly.
Please note I will be on vacation from tomorrow, so it might take a while before I respond to bugs in this version.
Ayrsimming
09 Sep 2007, 08:53
Hi Arno
I now see my test object in 3D preview and have exported to X file but dropping the X file on XtoMDL gives me a MDL file of 0 bytes.
I am having original reported problem with some other objects. Will hold back on fuller report until your return.
Best wishes for a good vacation.
Iain
Scotflight
Hi Iain,
I am still here today :). What error message do you get from XtoMDL? Try to compile from the command prompt, because without the error message I have no idea if the problem is in the conversion or somewhere else.
Also, please continuing posting bugs while I am away. I'll respond once I am back of course.
Here is an new build of the ModelConverterX tool. Please refer to the announcement (http://www.fsdeveloper.com/forum/showthread.php?t=6591) of alpha 01 for some more background information on how to use it.
I
Hi Arno,
I got the same problem as with the former version...:confused:
Regards
Bert
Hi Bert,
Can you give me the API macro you are trying to load in that case? All of the test API macros I received until now do work with the last version, but your macro might contain some different code in that case.
Hi Bert,
Can you give me the API macro you are trying to load in that case? All of the test API macros I received until now do work with the last version, but your macro might contain some different code in that case.
hi Arno,
Here it is!
bye
Bert
I tested with Al Simm's wonderful set of APIs.
Same now with me... API shows up perfectly in the Converter, export to X works ok, but if dragged on XtoMDL it creates a 0 kb mdl file.
Oops, I forgot... the error message reads:
E:\FSX_Design\ModelConverterX\API2>xtomdl boatdhowsailsup.x
OutputFile: boatdhowsailsup.MDL
Output file after modification: boatdhowsailsup.MDL
Creating output MDL file: boatdhowsailsup.MDL
error : Error loading .X file: (E:\FSX_Design\ModelConverterX\API2\boatdhowsails
up.X). Is it a valid FLIGHT SIMULATOR '.X' file?
(0): error : XToMdl.exe Unhandled Application Exception
(0): error : Fehler in der Anwendung.
(0): error : -2005531760 (Unknown)
(0): error : bei Microsoft.FlightSimulator.XToXmlLib.XFileLoader.Lo adFromMode
lFile(ModelFile FileInfo)
(0): error : bei Microsoft.FlightSimulator.XToXmlLib.ModelFile.Load FromXFile(
)
(0): error : bei Microsoft.FlightSimulator.XToXmlLib.XToXmlLib.Load AllFileDat
a()
(0): error : bei Microsoft.FlightSimulator.XToXmlLib.XToXmlLib.Proc ess(ModelF
ile[] InputFiles, Hashtable[] AnimationLinkage, String[] AnimationFileRef, XPart
Dict PartDictionary)
(0): error : bei Microsoft.FlightSimulator.XToMDL.XToMDL.ProcessInp uts()
(0): error : bei Microsoft.FlightSimulator.XToMDL.XToMDL.RealMain(S tring[] ar
gs)
(0): error : bei Microsoft.FlightSimulator.XToMDL.XToMDL.Main(Strin g[] args)
(0): error :
(0): error : Fehler in der Anwendung.
(0): error :
(0): error : Stack Trace:
(0): error : bei Microsoft.FlightSimulator.XToXmlLib.XFileLoader.Lo adFromMode
lFile(ModelFile FileInfo)
(0): error : bei Microsoft.FlightSimulator.XToXmlLib.ModelFile.Load FromXFile(
)
(0): error : bei Microsoft.FlightSimulator.XToXmlLib.XToXmlLib.Load AllFileDat
a()
(0): error : bei Microsoft.FlightSimulator.XToXmlLib.XToXmlLib.Proc ess(ModelF
ile[] InputFiles, Hashtable[] AnimationLinkage, String[] AnimationFileRef, XPart
Dict PartDictionary)
(0): error : bei Microsoft.FlightSimulator.XToMDL.XToMDL.ProcessInp uts()
(0): error : bei Microsoft.FlightSimulator.XToMDL.XToMDL.RealMain(S tring[] ar
gs)
(0): error : bei Microsoft.FlightSimulator.XToMDL.XToMDL.Main(Strin g[] args)
hi Arno,
Here it is!
bye
Bert
Hi Arno,
No reply yet; no time left or was this API not good enough to look at?:confused:
Regards
Bert
Ayrsimming
22 Sep 2007, 09:01
Hi Arno
Hope your trip went well.
I have a big error report when trying to compile my test object with command prompt and couldn't figure out way to copy to send.
There area lot of errors similar to the error report posted earlier.
Iain
Hi Arno,
No reply yet; no time left or was this API not good enough to look at?:confused:
Regards
Bert
Hi Bert,
according to his blog (http://msmvps.com/blogs/arnogerretsen/archive/tags/Tools/default.aspx) Arno is on vacations in Spain. Expect an answer around next week.
Regards,
Volker
I tested with Al Simm's wonderful set of APIs.
Same now with me... API shows up perfectly in the Converter, export to X works ok, but if dragged on XtoMDL it creates a 0 kb mdl file.
Thanks, I'll see if I can reproduce the error here.
Hi Bert,
No reply yet; no time left or was this API not good enough to look at?:confused:
As mentioned in the first post in this thread, I was on vacation. So I will look at the macro later.
Hi Iain,
Hope your trip went well.
I have a big error report when trying to compile my test object with command prompt and couldn't figure out way to copy to send.
There area lot of errors similar to the error report posted earlier.
OK, I'll first test the other object for which the errors have been reported. If I can reproduce that, that might also fix your errors. If not, we'll have to look into them in a little more detail.
Hi Bert,
As mentioned in the first post in this thread, I was on vacation. So I will look at the macro later.
Sorry Arno; take your time!
Bert
ccartmel
23 Sep 2007, 07:04
Arno,
Hope your break went well and you are fully refreshed.
I came across your new tool when researching my SCA conversion problem posted elsewhere on your forums.
I am using Vista and was unable to register your dll, however you intimated that this was for the 3d preview so continued on.
I have old scenery which decompiled to .SCA files so hoped that your tool would progress this to X-file;). I received the error message attached when I tried to import.
May be me but advice would be welcomed.
Best Regards
Charlie
Hi Charlie,
Does your SCASM file contain multiple objects? I guess that could be the reason of this error.
ccartmel
23 Sep 2007, 09:21
Yep,
92 of them to be exact according to the decompiler message.
Hi Charlie,
You could try to edit the SCA file and split it into pieces so that each file only contains one object (one Area - EndA block).
I will see if I can add some support for files with multiple objects in a later version.
ccartmel
23 Sep 2007, 16:26
Arno,
Thanks for the advice. Will do that when the rains keep me indoors. I am only looking for 1 or 2 objects so must be trial and error.
Will try to isolate the larger ones first.
Thanks
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.
Ayrsimming
24 Sep 2007, 18:10
Hi Arno
I can confirm having the dot as my decimal character.
Iain
@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.
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:
http://beli-orel.dyndns.org/lybe/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:
http://beli-orel.dyndns.org/lybe/mcerr.jpg
Running windows xp pro sp2+ .net 2 with all updates.
Hi Iain,
I can confirm having the dot as my decimal character.
In that case, could you submit one of the objects that gives you trouble for debugging to me?
Hi Volker,
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
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,
Under tools/options I wasn't able to select the path to x2mdl.exe, whatever I did, situation always ended with this:
The options dialog is not working yet. Maybe I should have disabled it, but I only mentioned it in the first post.
Then I tried to convert some 6 different API's and I'm ending up with this screen every time:
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.
Ayrsimming
27 Sep 2007, 18:43
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
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 (http://www.fsdeveloper.com/forum/showthread.php?t=6864) for new problems.
vBulletin® v3.8.3, Copyright ©2000-2013, Jelsoft Enterprises Ltd.