Morning guys,
at the moment I’m experiencing strange issues with Maxscript:
I wrote a kind of batch importer for a special file format (animation data) that saves the imported data in a Max file.
Everything is cool but when I take a closer look at the file size it happens that the size of every newly saved file (yes there can be more than one file) increases by 10 to 1000 kB randomly per Max-file. When I close Max and restart it, the file size is small again for the first Max-files then blows up again. That’s normally not a big deal, but when it comes to 100 files I end up pretty fast with Max files consisting of more than 100 MB. That’s stupid.
At first I thought the problem is not having the scene reset but that didn’t change anything. So my questions are:
- Is the problem know and does there exist a workaround ( in this case restarting max is no option)?
- Can Maxscript start other Max-instances that might contain the data I want to export?
Any help would be appreciated.
Thanks in advance kogen
I’ve done batch loading and saving in max, importing data, loading, exporting etc… with no strangeness.
Do you have some code we can look at?
Unfortunetaly not now. The code lies save in the company
Hmmm very strange, maybe it’s a Max 8 bug? The problem is not the opening or saving itself it’s more the kind of what happens to the files. Besides that scripted stuff I experienced the same problem when doing this by hand. If I open one instance of 3DS Max and I load and save a bunch of different files one after another the files get larger even if I don’t change something. That’s weird.
I’ve found in the Maxhelp that there is the DOSCOMMAND which allows me to open a new instance of 3DS Max but than there is still one problem that I need to tell the first instance of Max that opened the second one when the file in the second one is ready or even better, when the second instance has been closed… I hate those kind of thread-problems.
Are you using Biped in these particular files? I remember a few years back seeing a similar bug where Max files were constantly increasing in size. I thought it had something to do with the Biped pose library within the file… but I’m not 100% certain on that. It was definitely Biped related though.
Good point lostfilez I’ve forgotton to say something about the data in the file.
Actually there is the character geometry + its morphtargets. The bone-data was converted to “helpers” since the import of the base-rig file was done in COLLADA and Collada / OpenCollada always converts maya bones or max bones to Helpers. So we’ve got the character-geometry + the dummy objects + the morphdata, that’s all.
Don’t be confused when I’m talking about a COLLADA import. There is a base file that was created by an import/export from Maya to Max via collada (not autodesk collada since this produced many errors). Every newly imported animation is then loaded onto this base-file and gets saved afterwards.