• 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 Part Summary

Hey all --

Just a quick question on the part summary thing --

Is it the Vertices that you see in the part summary that make up the polygons or is it the faces thing that make up the polygons?

Just wondering if there's a way in Gmax to get an actual Polygon count so you can see where you're at and not be so confused.

I know Aerosoft's F-16 said they had close to 500,000 vertices, so I'm FAR from that in that aspect, about 80,000.

Just wondering what's what, so I don't go ewwwwww over my poly count.

Also, I know developing for FSX is different than for media. I know media can handle more, etc, so are two versions best, one for media and one for FSX?
The polygons are made from 3 or more vertices.
You can make airplanes for fsx that look good for media. There are a few tricks, like using the normal map or the texture for small or unnoticeable details intead of modeling them.
Here's how to check...

The game also goes by pure triangles. I 'think' the Polygon counter does triangles, but I dont know this for sure.

Polygons in Gmax are Polys that could have 100 Vertices, but a gaming Poly is 3 sided, only 3 Vertices, which the Compiler will convert the model to, but adds smoothing groups as well to keep the Polys smooth looking in-game.
The game also goes by pure triangles. I 'think' the Polygon counter does triangles, but I dont know this for sure.

If your mesh is Editable Poly you'll get one result from the polygon counter tool, if it's Editable Mesh you'll get another and bigger result; equal to the triangle count in E. Mesh afaik. The important thing is not to exceed 64K vertices per texture (iirc) for FSX.
Last edited:
Since I mostly work in E-Poly mode, I take the report from the Polygon Counter, and multiply by 1.5 for a "ball park estimate."

In GMax's Polygon Counter, what is reported for an E-Poly part is the total number of rectangle polys consisting of the two triangles. A rectangle has four vertices, two triangles have six vertices, which is a 1.5:1 ratio!
Thanks everyone for the answers. N2056, I thought that was it when I stumbled on it before, but just seemed, "too easy?" for some reason? LOL.

How did Aerosoft get away with close to 500,000 then for their F-16 in FSX? I'm confused on that one....:confused:

I have to start trusting my instincts it looks like....:)
Two of us have now found 'limits' to the FSX compiler.

As it seems, the first known limit was 65,000 Polygons per material. But then we found a new limit that triggers a Max Memory crash on the compiler for FSX. My model had a Poly count of 413,000. Thats not Vertices but Polys via the Polygon counter, and half are Mesh objects, half Poly objects.

We also found a realization that perhaps 'layers' in a FSX material might also effect the memory, as like the Vertice count limits.

Also, something Phil, formerly with Aces, noted that smoothing groups effect Vertice counts. For instance, if a square box is smoothed, it has 8 Vertices. But if you unsmooth it, having 6 sides (12 faces or pure triangles), then you have 24 Vertices, 4 vertices per side or Poly. This means that the computer has to detach 'faces' in smoothing groups for their own unique shading groups.

It kinda gets crazy.....

You almost have to just go for it, and hope you dont hit the limit like we did. So many things to count, but what really is the limit(s)?


We also found a realization that perhaps 'layers' in a FSX material might also affect the memory, as like the Vertice count limits.

Bill .. can you explain what you mean by "layers" in FSX materials. Are you referring to the number of maps associated with a material or something different?

Another tip:

Download the latest development release of Arno's modelconverterX ... run your compiled mdl through it and look at the object properties dialog (triangle and tvert count per material). Then you will grasp what X2Mdl has done to your geometry. It also gives you an idea of a) how efficiently you've used your materials and b) how much headroom you have.

For a scenery point of view, i use the max tvert / material count to work out how many placements of the object will saturate a drawcall buffer. This isn;t a practical issue for aircraft .. becasue you can only compile 65535 tverts for any given material.
Last edited: