That is usually caused by the exporter calling the splitmesh code, for some reason on the first loading of the tool in each max session it dosn't like any sub-calls to other files for some reason... I don't know why. I could never fix that...

He really should have called the splitmesh then passed the data to the exporter struct in the button handler, I guess?

My tool dosn't have that problem as far as I have tested it but it has only been tested on one machine so far.

hmm. I wonder if this is related to the minidump issues im getting with the game now. I got the exporter to work by using v1.1, and it seemed to work fine, it spit out a file and everything, but when i load the game i get a minidump error. The weird thing is that its looking for a mesh that doesnt exist. I dont know how it came up with it. All I did was delete some of the hardpoints to see if I could limit the number of missiles something fired, as a test, and then linked the remaining hardpoints to the model. Exported back to .mesh, limited the missile fire in the entity file to just 1 every 15 s, and then tried to load entrenchment. Minidump occured.

ya, i actually found out i was missing a mesh, heh. I have however, run into a new problem. I deleted some of the hardpoints, like i said, but the ship is still firing out of those hardpoints. that makes no sense.

lol