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

MDL size

Messages
1
Country
unitedkingdom
I'm currently involved in the development of a complex aircraft for FSX and P3D. The aircraft has hundreds of 3D parts (switches, needles etc) and makes use of 2048 x 2048 textures.

The exterior MDL currently stands at 98 MB and the interior (VC) MDL stands at 108 MB. Due to the level of detail and complexity of the aircraft I would expect the MDLs to be larger than most other payware aircraft on the market, however they seem very large when compared with some other 'high-level' products that also feature large numbers of parts and big textures:

M2M Mirage

EXT: 35 MB
VC: 28 MB

Aerosoft F-14

EXT: 22 MB
VC: 12 MB

CS L-1011

EXT: 31 MB
VC: 12 MB

Our VC certainly contains more switches than any of these, however I wouldn't say for example that our VC MDL contains 9x as much detail as the Aerosoft F14, which is the difference in file sizes.

Does anyone have a list of what contributes to the size of the compiled MDL files? Has anyone else encountered excessively large MDLs? It might just be the case that the sizes are a result of the detail included, but I'd like to rule out the possibility of any errors/inefficiencies.

The models are built in 3DS Max 2014 and we are using the XtoMDL that comes with Prepar3D SDK v1.4.4747.0.

Thanks in advance for any info.
 
From what I have seen, polygon counts and animated parts are the main reason why a model size increases. Try removing some static geometry or an animation switch and you will see noticeable differences.
 
100+ MB for a model file is beyond insane.

Animations do tend to blow up model size pretty well (especially when the animated parts are high poly), so if you have a lot of keyframed parts in there, model file size will balloon.
 
I'm impressed it exports! Does the model work in FSX/P3D with animations at present? And does it work with acceptable framerates if it does?
 
You may well find that whenever you begin scripting the switches, knobs, etc. in the VC that some things previously working will no longer work. This is because there is a limit to the number of scripted animations allowable.

One of my techniques to prevent the problem involves using <Visibility> conditions for simple switches instead of animations. One advantage is that nothing but the <PartInfo> section is required, so no separate <Animation...GUID.../> is necessary.
 
Bump maps is what I found easily doubles file size, at least on my setup they do, wish I knew the reason.
 
Bill, how do you add MouseRect, or can you add MouseRect to a Visibility part?
Bill, neither <Visibility> nor <MouseRect> require any <Animation...guid.../> entry.

Code:
  <PartInfo>
    <Name>C310_Fuel_Low_L</Name>
    <Visibility>
      <Parameter>
        <Code>
          (A:FUEL TANK LEFT MAIN QUANTITY, Gallons) 10 &lt;
          (L:TestFuelLight_Left,number) 1 ==
          or
          (A:ELECTRICAL MASTER BATTERY,bool)
          and
          if{ 1 } els{ 0 }
        </Code>
      </Parameter>
    </Visibility>
    <MouseRect>
      <Cursor>Hand</Cursor>
      <MouseFlags>LeftSingle+LeftRelease</MouseFlags>
      <CallbackCode>
        (M:Event) 'LeftSingle' scmp 0 == if{ 1 (>L:TestFuelLight_Left, enum) }
        (M:Event) 'LeftRelease' scmp 0 == if{ 0 (>L:TestFuelLight_Left, enum) }
        1 (>L:XMLSND3,bool)
      </CallbackCode>
    </MouseRect>
  </PartInfo>
 
Current aircraft is 18MB in size with just a touch over 300,000 triangles.

The x file is 42MB in size and the xanim file is 0.155MB in size.

The mdl file consists of a header (a handful of kilobytes), the texture definitions (another handful of kilobytes), the geometry and texture mapping (the biggest part), the animation keyframes (from the xanim so another handful of kilobytes) and the modeldef animations (another handful of kilobytes).

P3D models will be a bit larger than FSX models (maybe 10%?) as they use 32 bit to store the texture indexes rather than 16 bit used in FSX.

You need to check your triangle and texture vertices count in model converter x.
 
Back
Top