• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSXA GMAX export error

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!!
I just tried both of those suggestions and it threw the OOM error each time.

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. :(
 
Sorry to hear it. Must be quite frustrating. Perhaps try exporting with a few interior parts unselected, perhaps there is a specific culprit among the parts constructed most recently?
 
Sorry to hear it. Must be quite frustrating. Perhaps try exporting with a few interior parts unselected, perhaps there is a specific culprit among the parts constructed most recently?
I was trying this method this afternoon and found a very large number of parts/sub-assemblies that will cause the export to fail with the OOM error.

There is some good news however, I tried Bill's suggestion in post #4 and exported all the external parts and all the internal parts as two unique models and then merged them together in MCX. The resulting model works perfectly in FSX. :)
 
How about using "select by material" to get a batch of parts that you then "export selected". That ought to be a way to rule out for certain that you have an over-loaded material. Additionally you should go through your texture mapping looking for ways to knock down the texture vertice count.
 
How about using "select by material" to get a batch of parts that you then "export selected". That ought to be a way to rule out for certain that you have an over-loaded material. Additionally you should go through your texture mapping looking for ways to knock down the texture vertice count.
I did that a few days ago which is when I found some materials with more than the allowed number of verts and I then split the parts between two similar materials. It didn't stop the OOM error on a full export though.
 
Larry, 'just in case' you didnt know, if you 'copy' a material and do not move at least one slider, the material is like a combination of another, so it will not effect the change and still cause the crash. Make sure on the cloned material, you change a slider setting. Just 1% is all that is needed.
 
Larry, 'just in case' you didnt know, if you 'copy' a material and do not move at least one slider, the material is like a combination of another, so it will not effect the change and still cause the crash. Make sure on the cloned material, you change a slider setting. Just 1% is all that is needed.
Yup, I have been reducing the 'reflection' by a value of 1 each time I copied a material.
 
I am having the same problem with my model now. I have followed all the texture tips, and copied and re-copied, so each material only has on average 3 parts on them

But I am now at the position, if I add new parts, even using a new material, I get this error.

I am now near any main poly limit, so no idea what the issue is:confused:
 
Awesome!

I have had times when I would reboot the computer, have all programs off, have the plane saved in wireframe mesh mode, and then open it and compile my planes. That way, I had maximum memory for use for the compilations, nothing dragging down the virtual memory pool.

I also found that I had to reboot Gmax a number of times when doing exports. Rebooting the computer would help also, resetting the memory pool.

Right now, with 3DS Max 32bit, I can only export one chunk of airplane at a time, like panel, exterior, cabin, pilot. Each time, Max has to be rebooted or it crahes during the second export. Sometimes I can export two (when this first all started) and it would make it and then on export 3, crash and it would also ruin the save point, so I had/have to back step and resave the file upwards again.


grim.....

If only our tools were super powerful and incredibly resilient against crashes and capacities and limits...

Yep. That's exactly what used to happen to me in Max 32-bit. It always confused my why it would only crash on the second export (If it hadn't already crashed on the first one :laughing:). 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.

I haven't ever had Gmax crash or give me any export errors besides that "OBED scaling matrix" error.
 
I haven't had time to work on my project for a couple of months due to a number of issues here but the only way I can export the model now is to export all the parts that make up the exterior and then export all the parts that make up the interior (I made named selection sets to make this easier) and then merge the two models in MCX.

The above is for the 'external' model. The 'internal' model exports just fine.

It's a long-winded method but it works.
 
Back
Top