|
| Max and File Sizes. |
 Dave |
I'm sure this has been posted before, it's also on The Area discussion boards a fair bit, but what works for others doesn't work for some, and in my instance, nothing seems to work!
Max (working in 2010) will spontaneously produce large file sizes, we've had the problem now for a good couple of months in the studio and the only workaround we've found is such a hassle that most people don't even bother to do it.
The problem:
Scenes with not a lot going on, that should be about the 500kb to 2mb range are appearing to just keep doubling over time, even if the only changes in the scene itself are minor. (so I conclude that 'time' is one of the key culprits). Thus far I think we've had file sizes of about 50mb, which isn't a great deal to be fair... but it's a lot more than it should be and the "infected" scenes in question will take forever to load and often crash on saving.
The Details:
We are sourcing most, if not all textures from a location on the network. (ie, not local)
We are also sourcing our own shader files from a location on the network.
Some people are working with max files directly from a location on the network. (I've told them not to do this)
We are not using any biped/CAT rig stuff.
We are just modelling and texturing. Most people aren't even doing that. (just placing pre-made models)
The "Fixes":
Go to File > New and force it to keep all objects, re-save. (doesn't work for us)
Merge scene into new file, re-save. (doesn't work for us)
A script to remove some sort of "mixer" data? (doesn't work us!)
The only thing that does work for us, is to export the entire scene as a .obj (keep UV coords but not materials). CLOSE max down, boot it up again, import the mesh(es) and then re-apply materials. Save. Quite a hassle, and the error seems to come back eventually anyway.
Other:
Once a file is "infected", we can strip it of everything and save it (so it's completely empty) and it still has a large file size (ie, 10mb of absolutely nothing)
Does anybody have any information on this!?
read 296 times
3/9/2010 2:01:33 PM (last edit: 3/9/2010 2:11:12 PM)
|
| Dave |
*cough*bump*cough*
read 194 times
3/16/2010 1:57:31 PM (last edit: 3/16/2010 1:57:31 PM)
|
| advance-software |
Speak to Autodesk about it. You can probably use it as an excuse to blag your way onto the 2011 beta.
read 189 times
3/16/2010 1:58:13 PM (last edit: 3/16/2010 1:59:08 PM)
|
| Dave |
Cheers Steve,
Unfortunately Autodesk are well aware of it, and have released 3 "fixes", one of which includes the clean export option, which is hassle when dealing with scenes with a lot of textures to bring back in. The other 2 options are scripts that wipe track view data and motion mixer stuff, neither work with us.
It seems to be a big issue, threads on both The Area and CGTalk about it (and now Maxforums!), some solutions are just not working for people.
read 171 times
3/16/2010 5:46:33 PM (last edit: 3/16/2010 5:46:33 PM)
|
| advance-software |
All I can suggest is try loading the scene in 2011 then save back out in 2010 format.
I have no idea if it will work, but it's worth a shot. If it doesn't fix it, you could file a 2011 bug report, which *might* get it fixed either before 2011 goes final or in a service pack.
Sorry I can't be more helpful.
read 167 times
3/16/2010 6:08:42 PM (last edit: 3/16/2010 6:08:42 PM)
|
|
|