• 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.

Makemdl error OOM

Deltasierra2004

Deltasierra2004

Messages
142
Country
ca-ontario
I am trying to export my Firefly model into FS9 to see how my animations look. A couple of days ago, I was able to export without a problem. After I animated the wingfold sequence, I get an error now which states, " application has run out of memory and will now close, do you wish to attempt to save the scene?"

Then Gmax crashes taking MakeMdl with it. I'm stumped, can anyone help?
What else do you need to know about this situation? Could it be I have too much going on?

Doug

Win xp
AMD Athlon XP 2800
2.08 GHz
1.25GB RAM
 

Attachments

  • makemdl error.jpg
    makemdl error.jpg
    37.1 KB · Views: 480
Last edited:
Hi,

How complex is your model? Do you have many vertices, polygons or animations?
 
Yes, I believe so.

95 objects
25472 vertices
22687 faces

Memory usage
Physical 487.8/1279.4M
Virtual 379.4/ 3054.4M

Animations
Canopy
2 folding windows
flaps
rudder
prop
spinner
landing gear
wing fold
 
Last edited:
I think those numbers don't sound so high for aircraft, I am surprised by this error. Hopefully some other aircraft design has experience with this error, I have not seen it before.
 
1st suggestion -

create a new scene.

MERGE the firefly model into the new scene

TRy to compile.

IF it still crashes,

Then merge the FIrefly by part - leaving out the most recent parts modified after your last good compile (or if this was your first compile, leave out the most recent part).

Then try to compile.

Once you find the offending part(s), do a scale reset, to see if that helps.




I think.
 
ALSO...

...be certain to close any other programs running in the background to free up memory for GMax & the compiler.

Sometimes you have to reboot the computer while threatning it with a raw chicken's foot and mumbling some ancient voodoo curses... :rotfl:
 
Hi there,

can you export something else? Start a new scence, create a box, set the guid/friendly name and export. Does that work alright?

Vitus
 
Ok I found the culprit!!
I made two polygons to fill in a section of wing ( endcap) which would only be visible when the wings were folded. There is a section of my wing where the polygon goes from curved, to straight. Gmax had a problem with this, or maybe I missed a vertice when I was creating the poly. For some strange reason 1 single vertice was about 500 miles out ( well, far anyway), and the poly was flipped so I didn't see it. Therefore, the scene was too large to compile. I found it by selecting display selection brackets in viewport configuration. I remade the offending polygon, and now exporting is as easy as 1-2-3 :)

Thanks for your suggestions guys.
 
Last edited:
Been there; done that. One diagnostic step I forgot to mention would be to set the Viewport in Max/GMax to display "Bounding boxes," then do a Zoom Extents on the scene.

Your rogue vertex would have made a HUGE "Bounding box" :D
 
You must log in or register to reply here.
Back
Top