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

LODs.. Do you recommend them?

Messages
629
Country
unitedstates
I know this sounds silly to ask but do you guys recommend LODs to help in performance and stuttering? Also does this increase the memory usage on the fs9/fsx.exe?

Thanks, Ryan
 
Hi,

It depends.

Adding LODs will increase memory usage, since the MDL gets bigger with the additional LODs stored in it as well. So when the object is loaded it uses more memory.

That's why for scenery the advice in general is to use 3 LODS: LOD_100, LOD_040 and LOD_010. Aircraft models will have more LODs in general.

But you also have to look at your object. If it is a relatively simple object you might not gain much. A rule of thumb I have once heard is that each LOD should have 40% less polygons. If you can't do that without "destroying" your object you probably don't need an extra LOD.

For FSX there is something else. You can use drawcall batching to increase the performance. This works if many objects use exactly the same material settings. But when you are using drawcall batching the LODs are not displayed. So for objects you want to do the drawcall batching for you can save the effort to make LODs.

To sum it all up:

  • Simple object, placed once: might not need LOD at all
  • Complex object, placed once: give it LODs
  • Simple object, placed many times: use drawcall batching
  • Complex object, placed many times: probably not a good idea...
 
LODs in FSX

Hi,
On a flight sim conference last year, I have heard a statement, that LODs are not used in FSX. Is that the truth?

Regards
Mike
 
Hi Mike,

No, that is not true. Only when you use drawcall batching the LOD is not used. But that is an exception.
 
Hi,
On a flight sim conference last year, I have heard a statement, that LODs are not used in FSX. Is that the truth?

Regards
Mike

Definitely not true. I use LODs to "switch off 3d light ground splashes" if the user's aircraft is above 2,000' AGL.
 
I made a nice building for a friend. It is rather complex. He wants to place it many, many times. Should I add LOD's. Also- How do I do this in MCX? I can't find a tutorial on it. Bob
 
When I did the Mooney for P3D, I did the LOD's for the aircraft and I was very impressed with how it increased performance. Some day I might take the time to incorporate it into my payware models.

I do not do scenery, but find that if a very sophisticated scenery doesn't have LOD's in it, especially for all the fine detail, then when you are like 50 miles away, the entire airfield structures appear and pulls down frame rates. If I were doing 'scenery' instead of planes, I would definitely have LOD's on all the structures, and if I could, the graphics as well.
 
Hi Bob,

The question is not whether he uses it a lot in different places, but whether he wants to see the details of the building from far off as well and I guess not.
So you use LODs and that is rather simple (once you know how to, that is:D).
Import the building in MCX and on the second task bar from the top you will see a symbol with three 'balls' and when you hover your mouse over it it will tell you it can generate LODs. Clicking on it will show a pop up screen where you'd better (initially) check the 'Autocalculate' and then click 'calculate' and MCX will give you2, 3 or more LODS between 100 and 40 depending on the complexity of the model (I presume). You can check the outcome if you click on the third taskbar (from the top) and change the LOD from 100 to the LOD 70, 60, 40 or whatever MCX produced automatically. If you are not pleased with the outcome, you can always do it yourself by changing the parameters for the LOD creator.

Roby
 
Putting in LODS will not improve performance if the stuttering/fps is due to another factor. A LOD on a 2,500 poly building will not really do anything.

Shadows are much, much worse! Turn them off!

Doing so for my intricate approach light structure and low poly cars gave another 20 fps and stopped the dreadful stuttering it caused.

If you have a big model (like a car park full of cars), turn off shadows and use higher LODS i.e. 400 and just an empty LOD at 100.


Generally I put in empty LOD at 20 for buildings unless they share textures, in which case I use batching.
 
When MS came up with Acceleration/SP2 one of the things they did to accelerate us was to batch most of the default libraries, what they didn't do though was remove the LODs from the models first. We know that drawcall batching breaks LODs, therefore all the LODs in all the default models are being rendered by the sim at the same time regardless of your distance from the object, literally millions of superfluous polys being rendered all at once (which incidentally is why they flicker) - yet performance still improved drastically as a result of batching the models! That's the scoop on LODs, they most definitely aren't worth the trouble if you can batch the model instead.

LODs can be handy though, for example Shaun's runway lights where reverse LODs make them larger and therefore more visible the farther you get away from them...

If you want to place a model "many, many times" then drawcall batching is the way to go without question, many, many placements without many, many drawcalls is the essence of drawcall batching...

Jim
 
I mean, Jim, that I think that drawcalls do not matter so much if you have one complex building in one scenery and want to use that same building in other sceneries. Then the LODs would matter more than the drawcalls (IMHO). Of course everything depends on the kind of complexity Bob is talking about (many textures or many triangles).
 
Roger that Roby, yes really where batching pays off best is in something like a vegetation object for example where hundreds or thousands will be placed within a small area. I assumed Bob was talking about many instances of the same model within a relatively small area (basically within the same scenery). I also note Bob has been building some animated things in another thread so if the object in question is animated drawcall batching will break the animation, in that case adding a non-animated LOD would likely be beneficial to performance - I don't know if that's possible, I've never LODed an animated model, but I assume it would be.
 
Yeah, batching would only work if there's >1 models of the same texture in the field of view at one time.

So it depends on what you're referring to as to whether LODs are right to use.

Multiple instances of the same object/texture... Batch it.


Single complex model (>5,000 Verts) LOD 100, 40 and 10 (empty).

Not complex single model (<5,000) Empty LOD.
 
Of course you can also build 10 different objects for a given scenery that all use the same material/texture if you've got room on the texture sheet, then if you batch them all the sim sees them as a single drawcall (or so I understand). You almost always have a small area on the texture sheet left over after building something so when you build a small item like a dumpster or a park bench you can slip them in under the same drawcall as a large hangar halfway across the field if you use an identical material.
 
I model aircraft for CFS3 and without LODs the creaky old code will stutter appallingly. That is because CFS3 is a combat sim and a number of aircraft in close proximity slows things down eg in a dogfight, also the sim has to track munitions and their impacts too. Not a problem in FSX...
 
Very true. But if you're making a library of objects, which can be used in all airports, I think it's best to put them all onto separate texture sheets. It's a pain re-texturing for another airport if you don't need half the sheet of the last one.

Plus a few 512x512 sheets for a few bins/carts isn't much really.
 
Last edited:
Wow! Many responses and no e-mail notification even though I have that checked. This building I made is a huge commercial chicken barn about 595 ft long and 44 ft wide. trans fence on one side, lights inside - about 6 only- light at night. And a much smaller item which is a large grain feeder for the chicks. This is separate and sits outside anywhere you want.

So the guy write back and likes it but says it might be to intricate since he planes to place "hundreds of these, maybe more." So I thought if he does that maybe LOD would be the answer. I guess not. I started to mess with it in MCX but got the warning window continue or exit, etc and got a big white screen with a red X across it when I tried to do the auto thing or other stuff.

BTW- About draw-call batching........... I had a house I made with chimney smoke and also some small object with blinking lights attached. I noticed one day that the attached lights were offset from the object by about a foot or two. The smoke from the chimney was away from the chimney by about the same amount.

Come to find out at a certain elevation (I do not know where the cut off point is- unless it is gradual) effects will show up in the right place but the objects they are attached to will be offset. This is an inherent FSX anomaly.

The fix? Go to MCX in options..... under export conditions uncheck drawcall batching. Export your mdl and try again. It worked. for lower elevations when draw call batching is needed you can turn it back on again. (You have my permission.) hehehehehe Bob [anyone who laughs at my humor gets a 20 Euro note at the end of the month. ]
 
Back
Top