.x File Compilation so slow. Why?

[Paul Domingue]

Thanks. Could be? Not really sure what my next step would be. I was considering one possible reason. My SDK / modeldef.xml is on my sim drive. But I operate Blender on my windows drive. Both drives are healthy. But I wonder if there's a hiccup someplace in between?

You keep jumping from model to system in your search. You need to verify which one through an independent source as I mentioned before. That could save you a lot of time figuring out the problem.

 

[fsxar177]

Thanks Paul. I did test through another independent source and he had the same results as me. So You're right, it must not be a system thing.

I guess the biggest reason why I'm confused at all is that it would be much a different scenario, if I was exporting via .x for direct x, or Collada, or .3ds, I'd be exporting as much as 800% more in virtually a blink of an eye, compared to what would be a stand-still with the toolset. (.x for FSX, or .x for P3D).

In the meantime, it doesn't hinder my progress. The complete project does eventually make it out. I'm just trying to identify why the hang-up. Try to save some time.

- Joseph

 

[Paul Domingue]

Now that you verified it with someone else can you export a different model with better export time? If you can isolate the problem to just one model than you could break it down exporting small sections until you find the offending object which maybe all it is.

 

[fsxar177]

There isn't any offending object. I can create a new scene from scratch, add a simple mesh, subdivide to simulate some detail, and export. Same problem persists. We're not talking about giant exports either, file-sizes of 8-20mb.

Paul, when you're exporting mesh from 3ds max, how much faster is it to export an object to a standard file-type such as .3ds, or .obj, compared to exporting an .x file for FSX/P3D? (without going through xtomdl to generate the .mdl).

- Joseph

 

[Paul Domingue]

There isn't any offending object. I can create a new scene from scratch, add a simple mesh, subdivide to simulate some detail, and export. Same problem persists. We're not talking about giant exports either, file-sizes of 8-20mb.

Paul, when you're exporting mesh from 3ds max, how much faster is it to export an object to a standard file-type such as .3ds, or .obj, compared to exporting an .x file for FSX/P3D? (without going through xtomdl to generate the .mdl).

- Joseph

I ran a test with my Defiant model.

Model Specs,
Polys: 89,556
Tris: 176,400
Verts: 92,478

Export time in seconds / resulting file size
----------------------------------------------
X 12.67 / 24,012KB
FBX 5.39 / 61,350KB
3DS 1.32 / 5,899KB
OBJ 21.26 / 14,012KB

It's interesting that the shortest export time created the smallest file while FBX only a couple of seconds different created the largest file.

 

[n4gix]

Joseph, thank you for using the proper process name export. There are two steps to FSX/P3D model creation:

1. export from modeling program to .x and .xanim files
2. compile .x and .xanim files via xtomdl.exe to .mdl file

I have noticed that whenever I first export from Max or GMax, it takes longer to reach the .x and .xanim files because the export module has to parse the modeldef.xml file as well.

The second and subsequent exports are faster since -if no changes have been made to the modeldef.xml file - the export module will skip having to re-parse the modeldef.xml file during export. If I make any changes to modeldef.xml at all, then it again takes much longer to complete.

Even so, my most complex project to date which is around 300,000 polys takes about seven minutes for the initial export to complete.

Once upon a time I used to export/compile across my LAN since my main sim computer is in another room (my library). It took me quite awhile to notice that it was so slow (up to an hour!) because one of my LAN devices was the bottleneck being limited to 10 MBS data transfer! When I replaced it with a 100 MBS device it sped things up considerably!

Now however, I export/compile to my local development computer and test in a minimalist FSX/P3D environment, only copy/pasting to my sim computer infrequently for stress testing when I think I have everything done...

 

[fsxar177]

Thank-you for the valuable input gentleman. And Paul, for doing those tests. Really helps in understanding this all.

Above Paul has a model with 176k+ tris. The Basic test-platform that I'm experimenting with is about 60k tris with similar tri to vert/face ratio. With a resulting .x file of 19,696KB. This is the one that takes 5+ minutes when exported as one object. And Only about 1 minute when exporting as 4 separate objects. Still a long way from 12 seconds!!!

I also get similar results with the other formats. I think Collada (.dae) is the fastest at about .3 seconds, and resulting in a file size very close to the file size of the .x file.

At this point I am suspecting the blender related .py scripts and or modeldef.xml. (Even though I have tried a basic version of the modeldef with no improvement). In Blender we "initialize" the toolset. I'm not sure if that is the same as having it parsed or not, I would think so? It doesn't seem to make a difference if it's the first, or second export.

Testing continues.
- Joseph