Quote:Mmm.o.k...May be you are right,then explain me such a thing:
When you export,say from 3D studio max to x.file it takes some time(a good few seconds depends on how model compicated is)And then you load x file into makemdl wich compiles it.When you export from Gmax to mdl right after clicking on word "export" mdl compiling process starts.So the questions is when gmax creates x file?Is gmax so fast that it creates x file in less then a second and you even dont see it?
When the Export option is selected in Gmax, watch the progression bar at the bottom of the Gmax GUI. This is the time when Gmax is talking to FSModelEXP.dle and converting the *.gmax source to X file format. Depending on the complexity of the *.gmax source will determine how long it takes the progression bar to complete ( this will be typical as to what you see in 3D Max ). When the *.gmax source has been fully converted to an X file, the plugin, FSModelEXP.dle will call MakeMDL.exe and automatically force it to run without any further input form the user.
Quote:Anyway,lets say gmax really creates x file before compiling(although I dont think so).
Although you don’t think gmax creates an X file would be right to a certain degree. As pointed out already. Gmax communicates down to FSModelEXP.del and it’s at this point the X file is created.
Quote: So If you have gamepack installed do you need to deal with x files?
No,you dont,right?
You should never need to deal with the X file. Infect it was meant for you not too. That’s why you never see it or have a record of it after it has been used.
Quote:So if somebody has gmax and makemdl and dont have gamepack he cant create x file using gmax to load it into makemdl.But if he has gamepack he never need to deal with x files,so what's the point?
I am not sure where you are going with this statment.
Quote:When you put middlman into the picture you can capture and save the x file. There may be instances (especially for FS2002) where some direct manipulation of the x file may be useful.
Hi Felix,
Middleman alone can’t capture the X file. What Middleman does is provide the user with an interface that allows certain options to be selected in MDLCommander. MDLCommander is the utility that is doing the work to capture the X file. It does so by copying the X file to a *.txt file for editing or to be used at a later time for compile. When MDLCommander was first developed it was intended as a scenery placement aid. By this I mean you could build a scenery object and compile to X format and offer this format to developers/end users instead of the *.gmax source. The end user couldn’t change the model a great deal and call it his/her own, but they could make slight mods and compile to *.bgl and change the placement coordinates at the time of running the X file through MakeMDL.exe. If you were to use just MDLCommander in the export pipe you would need to open the associated config file and edit it by hand for what you would like MDLCommander to do. That’s why Middleman is used in conjunction with MDLCommander so you never have to manually edit MDLCommanders config file.
FSEdge
Pages: 1
