• 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

Messages
468
Country
ca-ontario
I am getting close to completing my project (finally!) but have run into a major issue that's become a show stopper for now.

I have my project split into two models (external and internal) and the internal model exports fine but the external model has started throwing 'out of memory' export errors. Whenever I try to export I invariably get the following message:

gmax_error_zpsa27e9627.jpg


I have numerous 'named selection sets' and if I select 'external' which contains all the external parts I can export with no problem. Likewise with the 'internal' selection set which contains all the internal (VC) parts. It's only when I try to export the entire model that I run into the OOM issues.

I have tried the usual tricks of switching to wireframe view, hiding all the parts, saving then closing GMAX then re-opening and going directly to 'File/Export' but it still throws the OOM error.

If I'm lucky I can maybe get one good export for every 12-15 export attempts (I close GMAX and re-start before each export) but for the most part it chokes on export.

Has anyone seen this before or maybe have some suggestions for a cure?
 
I think this is the typical limit hit on a Material, which is 65,000 Polys on one Material.

Try this. Select a hard hit Material, then select all parts using the Material (use the 'select parts by Material script), then click the Poly Counter tool and see what you have. If over 65K Polys, then go to the Material Editor, click Copy on that Material, and change one slider, rename it like 'xxx_2' and then deselect half of those parts and click Apply in Material Editor. Reboot Gmax, Rexport and see what happens.

If it happens again, check again for another hot Material useage.


Bill
 
I've been down that road Bill and split a couple of materials already but I still get the OOM error when trying a full export.
 
I wonder then if you have hit the 'grim' 1/2 million Poly level... To prove this theory, try exporting 75% of the model. If it works, then export a different zone of the model, still 75%. If that exports also, then all the parts are exporting fine, and means that you have hit the max level your computer and system can export..

But... You can still export into chunks and fuse them together in MCX. If this is the issue.

NOTE: MCX cannot presently handle VC animations. Arno is working on it.
 
I don't think I've hit the 1/2 million poly limit either Bill. I just selected all the parts in the 'external' model and converted them to 'mesh mode' and took a poly count as shown below:

mesh_mode_zps3c9e7e57.jpg


I then converted them all back to 'poly mode' and took another count:

poly_mode_zps0e35c708.jpg


Both methods show well below 500,000 polys.

Still baffled. :confused:
 
hmmm....


Well... well, two things.

1. Create JPG's at 1024 size of everything in the library (something I really dread) and set all materials to the JPG's. Reboot Gmax and test export. (I personally wouldnt do this if you have a ton of textures. IF you do, do this to a 'special save' in case it does nothing, so you do not lose your base materials 'types'.)

IF that doesnt work;

2. See if someone with a bigger system/computer will try to export it. Perhaps having a later, more powerful computer 'might' be able to export it.

With FSX, the compiler jumbles all three of the model build processes in virtual memory, which you probably know, so if virtual cannot handle the shear size of the process, then see if someone else can do it for you.


In the mean time, you can splice multi exports out via MCX 'if' you can export small chunks at a time.

Did you test to see if it will export smaller portions at a time? Like, leave 25% of the parts off and export the 75% of the model and see if that works?




Bill
 
hmmm....


Well... well, two things.

1. Create JPG's at 1024 size of everything in the library (something I really dread) and set all materials to the JPG's. Reboot Gmax and test export. (I personally wouldnt do this if you have a ton of textures. IF you do, do this to a 'special save' in case it does nothing, so you do not lose your base materials 'types'.)

If nothing else works I will have to give that a try but it's going to be a big task. :eek:

IF that doesnt work;

2. See if someone with a bigger system/computer will try to export it. Perhaps having a later, more powerful computer 'might' be able to export it.

With FSX, the compiler jumbles all three of the model build processes in virtual memory, which you probably know, so if virtual cannot handle the shear size of the process, then see if someone else can do it for you.

This computer is an i5-2500k quad-core running at 3.30 Ghz on Win 7/64 with 8 Gb of DDR3 RAM so it should have enough oomph to do the job I would have thought.

In the mean time, you can splice multi exports out via MCX 'if' you can export small chunks at a time.

Did you test to see if it will export smaller portions at a time? Like, leave 25% of the parts off and export the 75% of the model and see if that works?

In the first post I said:

I have numerous 'named selection sets' and if I select 'external' which contains all the external parts I can export with no problem. Likewise with the 'internal' selection set which contains all the internal (VC) parts. It's only when I try to export the entire model that I run into the OOM issues.

I appreciate all the time you are putting in on this issue Bill.
 
One question, Larry - you do have one single parent called exterior which has all your exterior parts, and one single parent called interior which has all your interior parts, and no (none, zero) parts not attached to either of the two?
 
Last edited by a moderator:
One question, Larry - you do have one single parent called exterior which has all your exterior parts, and one single parent called interior which has all your interior parts, and no (none, zero) parts not attached to either of the two?
If you mean is it set up like a FS2004 GMAX model then no it is not.

I have multiple parents containing external parts and multiple parents containing interior parts plus a whole bunch of parts that are not associated with anything else.

The parts which do have a parent/child relationship are either parts that form a complex animation (like the gear parts for example) or parts in the VC that are animated. The are also other sub-sets like all the parts that make up the pilot(s) etc.
 
Yes I meant that, sorry, overlooked the FSXA tag.

Have you tried separating the two sets into two gmax files?

If your Windows display is on Aero design (or whatever it is called) try going back to Classic. I have heard that this has caused errors with Gmax in the past.
 
Last edited by a moderator:
Larry,

Combined, in a single export, thats like nearly 490,000 Polygons. Even though your computer has pretty good specs, I think it might be near the limit.
 
Yes I meant that, sorry, overlooked the FSXA tag.

Have you tried separating the two sets into two gmax files?

I already have it split into two gmax files. The 'interior' model exports with no problems it is the 'exterior' model that is crashing on export. The 'exterior' model also contains interior parts that you can see from the exterior. I can export just the exterior parts or just the interior parts of the 'exterior' model with no problems, it's only when I try to export the entire 'exterior' model (all exterior and interior parts) that I hit the OOM issue'

If your Windows display is on Aero design (or whatever it is called) try going back to Classic. I have heard that this has caused errors with Gmax in the past.

My system automatically switches to Classic mode whenever I start GMAX, it does the same whenever I start FSX too. It detects when programs cannot run with 'Aero' and makes the changes before starting the program.
 
Larry,

Combined, in a single export, thats like nearly 490,000 Polygons. Even though your computer has pretty good specs, I think it might be near the limit.

I think you may be misunderstanding the screenshots I posted in post #5 Bill. Those screenshots show the entire 'exterior' model as selected items (both interior and exterior parts) and one was taken with all parts in 'mesh mode' and the other with all parts in 'poly mode'. The two 'modes' are never 'combined' in any way and I always export the entire model in 'wireframe mode' with all the parts hidden so that all I see is a blank GMAX modelling area before exporting. Robert (N2056) tipped me off about that trick when running into export problems as having textured parts displayed when exporting ties up resources GMAX can better use for exporting.
 
Roger that. My apologies.
No apologies need Bill. :)

Just for reference I decided to try an export of the exterior model today and it exported perfectly with no issues! Go figure huh! :rolleyes:

I guess it just depends on how GMAX is feeling on any specific day, some days it give me issues and some days it behaves itself. :banghead:

I can now officially say that all the parts are modelled (barring any last minute, unforeseen, additions) and I just have a couple of animations and visibility items to code and the modelling/coding tasks will be done. I just hope that I will still be able to export as I need to make changes to the modeldef.xml file and then re-export both models again.

I still have some minor work to do on textures, FDE, manual etc. but the release date is getting closer (at long last)! :eek::D
 
Last edited:
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...
 
Well things were too good to be true after all. :mad:

I just made all the changes to the modeldef.xml file for my final animation/visibility items and now it's refusing to export again!

I can't check the coding or finish the 2D gauge which calls 'L:vars' from the modeldef file if I can't do the final model export. :(

Ho hum, I will get a good export eventually I suppose!
 
Wozza taught me a cool trick. Use Microsoft Internet Explorer to open your ModelDef. It should show you any flaws in the code. I think Opera will as well. I cant remember if Safari will show errors.

That might help to get your ModelDef working.
 
I've never been able to get IE to open more than one line of code.

I use the free 'Notepad++' program to edit xml files. It's an excellent tool and helps with formatting as well as syntax.
 
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!!
 
Back
Top