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

P3D v4 Creating LODs

Messages
29
Country
unitedkingdom
Hi Again

I apologise for the number of threads I've added today. I guess I've gotten as far as I can with what I can do and now need to find answers before I can finish up. Everybody here has been really generous with taking time to reply and help out though. Currently, I have a model, with gear, wheel and propeller animations working and tagged (I haven't bothered with flaps/rudder as I am using it for AI and to reduce complexity for my first model). The model is fully textured including specular/LM/bump.

My next challenge is creating LODs. I understand what they are and why they are required. I have played with the LOD tool and tried generating a second LOD by cloning my whole existing model as a new LOD and renaming it to _75 instead of _150. So far so good. However, I have a couple of questions:

1. Is cloning my existing model and then reducing it's complexity the best method to generate further LODs?

2. I know 3DS Max has its own LOD tool for adding LODs. Should I be using this, or simply using the P3D Plug-in LOD tool?

3. When I add new 'LODs' I am simply copying the existing model and changing the name of the objects to _75 rather than _150..... is this correct - the LOD Tool adds text which always seems to read 100, which does not correlate with the _150 or _75 names I have given my LODs. Do I need to do anything to make the model into a LOD other than making sure it is correctly named? (I haven't so far, but the LOD Tool DOES recognise the model in the LODs window).

4. I have completed my animations and tags in my existing model which I have named for LOD 150. If I clone the existing model objects for a new LOD, do I have to retag the animations? And if so they just use the same tags as before?

5. I have already textured the aircraft using unwrap UVW... I am unsure what will happen to this as I delete vortices... I assume it will just be a case of possibly having to realign the texture with the aircraft as small changes in its shape take place? Currently my Unwrap UVW is a distinct modifier in the stack for the model... should I collapse this before changing the vortices (or what is the best way to handle this, as clicking the editable poly modifier brings up an error message about the dependant unwrap uvw)? I'm thinking possibly the answer is I shouldn't have textured it yet... but alas, too late!

6. Finally, any tips on the best way to reduce complexity? I'm planning to simply delete vertices to reduce the number of faces whilst retaining the general shape with varying degrees of accuracy for each LOD. Does this sound about right?

If anybody has any thoughts on the above - even if it only relates to one of the above - I am, as ever, always grateful! When my next pay packet comes in I'll be making a donation to the site - I've learnt loads from here... Not only from my own posts but also from countless older posts.

Cheers

Adam
 
1. Clone and reduce complexity.

2. I wouldn't suggest using Max's LOD tool.

5. Either collapse the stack or add an Edit Poly modifier to the stack, then you can use Max's Remove tool in Vertex or Edge sub-object. Don't just delete vertices/edges or you will bork the mapping as well as the modelling.

6. Remove loops or rings of vertices as you think appropriate, but as the complexity gets to really simple, building the lowest LODs from scratch might be quicker: they're not going to be seen close up and model and mapping accuracy are much less important.
 
Hello Adam.

Maybe this video could be useful for you. In the video I created a long time ago for a friendly developer, it is about the creation of LOD's and the reduction of polygons. The use of the Modifier ProOptimizer is shown. The ProOptimizer can be used for very complex geometries, for example for persons or for airplanes.

Unfortunately, the video is under German text. But the video is actually self-explanatory.

 
The lowest LOD is literally no more nor less than a cruciform "paper airplane"... :rotfl:
 
Hello All!

Christian - The video was great - saved me a lot of time, thanks!

Everybody - I'm now finding the verification tool isn't liking my LODs due to open edges (non-manifold geometry)... This occurs where I have used single planes for textures such as propeller blurs or the 2d rendition of the aircraft at LOD 5. Is it okay to ignore these 'broken items' or do they need to be addressed... and if so, how, when the object is 2d?

There don't appear to be any problems in MCX when I preview it there and LODs work there too.

The other thing I noticed is that I have a LOD 100 in MCX which I don't have in Max... How do I go about removing that? Or do I HAVE to have a LOD 100? The P3D SDK documentation lists 5, 15, 35, 75, 150 and 400... no 100... (I have only gone as far as 150 as it is an AI aircraft). I am beginning to learn to take the SDK documentation with a pinch of salt though :-)

Thanks

Adam
 
Last edited:
In my case, I only created lods 5, 75 and 200. LOD_200 is the full helicopter. What you will see when the camera is near it. To make LOD 75
y copied the helicopter and renamed by hand the parts. I deletted the interior parts (seats, pilots...) and the small exterior parts which are
not visible in the distance (for instance, many parts of the rotor head, parts of the landing gear, some small antennas...). Generally, I do
not reduce complexity of the parts, but I think that for some basic parts it is a good idea (gear tires for instance, will look the same and the
textures will suit well without further corrections; have in mind that those parts will be visible only from a long distance, so texture fit is
not that important).

A way to see how it goes is exporting to FSX. Then switching to tower view. Zoom out till the point the model "changes" (it has changed
to a lower lod) and see which parts you can see and what others you can't. Then return to your modelling application and delete from the
lower lod those parts you couln't see. Then repeat for the next lod.

Finally, my LOD 5 is a enclosed shape similar to a helicopter fuselage. I made it with a cube, scaled to the same length, width and height
of the helicopter, and then a loop cut and slide (blender) to make 6 rings. Then I scaled these rings as appropriate to adjust to the fuselage
shape. Finally, I textured it just for fun. It really does not matter because you will never see it in the sim.

If you create more lods the visual change when changing from a lod to another will be less noticeable (fewer changes, more noticeables). In this matter there are many opinions. I think that vertex are not a problem in the PCs of today. My helicopter has 165.000 total vertex, probably 90-10k in the LOD_200. My PC has not a dedicated video card and it handles the model without any problem. Virtual cokpit gauges such as screens, autopilots, etc, impact 100 times more on performance than the 3D model complexity. So, be generous. This is my opinion, of course.

This is my lod 5 (details are due to the bump map):

upload_2017-9-18_16-33-29.png
 
Last edited:
This is my lod 5 (details are due to the bump map):
View attachment 36934

To my knowledge, your LOD_5 model must always be without textures. And it must be flat, so a simple polygon. In short, your LOD_5 is a simple polygon without textures. So it is documented in the fsx/p3D-SDK
And you must have set "Double Sided".

sdk_lod_5a00e8.jpg

Source: P3Dv4-SDK


airplane_lod_5edc00.jpg

Picture: This is LOD_5 model of the p3dv4 standard mooney bravo
 
Hi All

Thanks for everybody's responses - I really appreciate the knowledge.

I am still having the issue with LOD 100 appearing in MCX even though I don't want a LOD 100 and don't have one set up in Max (and don't have one showing in the aces LOD tool). LOD 100 only seems to show the 0,0,0 Centre point dummy cube I added as the top level of the hierarchy.

Any thoughts anybody?

Thanks

Adam
 
So have you found a good recipe for you to create a working light for p3D?

Assuming you meant LOD and not light, yes I have have them working... Used the tool you suggested Christian - really useful, thanks.

I have a new post on here now as I'm having issues getting the animations to run in P3D!

Again - appreciate the support!

Adam

PS if you meant light... I added them today through the aircraft.cfg today... But Max in meters (as per the P3D SDK guidance) and cfg in feet??? What a nightmare!
 
Back
Top