XtoMDL UI

#21
Thank you for your input! :)

I'll investigate the crashing. Strangely enough, I've been using the 1.4 exporter for quite some time throughout my development and I've not had it crash. Could you perhaps provide me with the error report from Windows Event Viewer?

I plan on revisiting the UI at some point and adding a sort of profile system to let the user create and select preset compilation configurations. As someone who quite often works on multiple projects, I definitely agree that there needs to be an easier way to switch. In the short term, what I've been doing is keeping multiple copies of the Config.xml located at %localappdata%\XtoMDL UI\ and changing the paths/options in each, then I manually rename the config I want prior to launching the program. Whenever I implement the profile system, I'll add an option to compile both the exterior and interior at the same time, as I think this would be quite helpful.

1.0.3.0 is the latest. There is an update notification system built in (unless you have unchecked it in the options, of course). If you are not notified upon starting XtoMDL UI that there is an update, then you are running the latest build.
 

Paul Domingue

Resource contributor
#22
I'll try it again with a different export in v1.4 and see what occurs. I'll check if the update is unchecked since I just went with the default settings.
 

Paul Domingue

Resource contributor
#23
Brandon, I now have XtoMDLUI working for P3D SDK 1.4. I don't know what has changed since my first tests, some glitch on my system maybe but it is working properly now.
Another suggestion for any version update would be an overwrite warning and/or an incremental save of the previous MDL build as a selectable checkbox.
Love the program and it is now my compiling interface of choice.
 
#24
Glad it's working. I still would have liked to see the error report. I'd at least like to get an idea of what the problem could have been.

I can certainly look in to adding an overwrite warning or incremental save feature.
 

Paul Domingue

Resource contributor
#25
I'm not sure how to get the error report. When it crashed Windows left me with two choices terminate or let Windows search for a solution. I guess there's a way to dump a report and if it happens again I'll attempt to do this.
Keep up the good work it's a great utility as it stands.
 
#26
If you go to Start and type in "Event Viewer," you can bring up the Windows Event Viewer window. I've included a screenshot below to note a couple of things.



1. Expand the Windows Logs category and select Application.
2. This is a list of events. If you scroll down far enough (June 7 looks to be when it crashed based on the date of your post), you'll likely be able to find it. It should show up as "Error" under the Level column.
3. There might be multiple XtoMDL UI items that show in the list (#2). I need the details from the item that has many lines that begin with the word "at" in the box labeled #3. You can simply select all of the text and copy it (has to be with Ctrl+C - there's no menu for it).
 
#28
Hi,

Where this wonderfull tool can be downloaded ?
The shortcut on the first page isn't valid and I don't see it in the WiKi Ressources.

Thanks very much.
 
#29
Hi,

Where this wonderfull tool can be downloaded ?
The shortcut on the first page isn't valid and I don't see it in the WiKi Ressources.

Thanks very much.
Thanks for the heads up! It's fixed now. We had recently implemented a new firewall on the website it's hosted on and it broke the redirect.
 
#33
Update 1.0.4.0
  • Fix potential crash when a new file fails to compile (likely resolves this issue)
  • Open/Save File Dialogs now open to the existing file path specified in the appropriate textboxes (if paths are already selected)
  • Adjusted size of close button

An update prompt will be shown at application launch (if enabled).
 
Last edited:
#34
hello! what is?
(0): error : XToMdl.exe Unhandled Application Exception
(0): error :
(0): error : SlimDX.Direct3D9.Direct3D9Exception
(0): error :
(0): error : D3DXFERR_PARSEERROR: Parse error (-2005531760)

everything was going good
until i instaled FSXS

edit: compiled (slower but compiled) an old .X file before the 4.0 sp2 update :scratchch its the .X exporter i guess? related to some change in Direct X?

then i tried to X export a simple BOX and compiled right... there must be something on the model file
 
Last edited:
#35
Can I / we, have auto detect on modeldef.xml?
it would be make easier if Xtomdl UI always detect modeldef.xml in his folder. so I can placed xtomdl.exe, modeldef.xml and model.x/xanim file in 1 folder then xtomdl can detect it.
ace tool (from P3D v3 I think) already have auto detect modeldef.xml if file model folder have it.
 

Paul Domingue

Resource contributor
#38
Can I / we, have auto detect on modeldef.xml?
it would be make easier if Xtomdl UI always detect modeldef.xml in his folder. so I can placed xtomdl.exe, modeldef.xml and model.x/xanim file in 1 folder then xtomdl can detect it.
ace tool (from P3D v3 I think) already have auto detect modeldef.xml if file model folder have it.
XtoMDL doesn't care where the modeldef.xml file is located providing you state a path but the export module requires it to be in the bin folder of the SDK.
 
#39
that true Paul, I just have 2-3 project that I do base on my mood :rotfl:, each time compiling, I need to change the path, modeldef and x/xanim file. more over if I use bin folder on SDK, I need to rename too on modeldef that belong to other project.
I made new modeldef.xml from scratch to make it tidy and easy to manage
 
Top