- Messages
- 468
- Country

I just tried both of those suggestions and it threw the OOM error each time.If it's a true OOM prob then two suggestions:
1) One step further than Bill suggested, but ultra-simple: temporarily rename your textures directory so that Gmax can't see any of them (except maybe the $VC stuff which it probably must have as it's baked into the mdl?).
2) A bit of an experiment, exert ultra caution here: in Customize > Preferences > Maxscript you have an option "Memory: Initial heap allocation (MBytes): 7.5" (default). Reduce a bit, reload, export, and reset later. At your own risk though!!
For step 2 I reduced the heap allocation to 7.0 and it failed with an OOM error. I then reduced it to 6.5 and GMAX failed to load the model file giving a script memory error. By trial and error I found 6.7 to be the smallest heap allocation which will allow the model to open but then it throws the OOM error on export.



). Very annoying. And the problem had nothing to do with materials because I checked every single material and did a polygon/vertex count on it, which came out as less than a third of the vertex limit.