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

FSX Double-sided bug

Messages
1,074
Country
ca-ontario
Just a heads-up/warning on a bug in FSX Material "double-sided" option. I'm not sure if this was documented, but I'll post it here just in case someone is tearing their hair out just like I did:

There is a "double-sided" option in FSX material which can be used for creating "thin" 3D objects that need to be visible from both sides. A good example of this would be mesh fences and billboard signs. All you do is create your "thin" geometry, and choose this option to create back side (instead of creating additional geometry for it, doubling the poly count)

The problem with this is that, while the exporter creates the "back side", it "forgets" to flip its normal (or, improperly orders the vertices). The result is: the back side geometry, while visible, is lit improperly. So for instance, during sunrise, one side of your fence should be shiny while the other - dark. Instead, both sides are dark/shiny, which can look very wrong, especially when you have fence segments oriented every which way.

The solution: forget this option. When you create your one-sided fence, simply clone the object, flip its normals and attach it to the original object. the extra geometry you added probably won't matter, as I am guessing the exporter is doing the same thing, but forgetting the proper normal adjustment.

Misho
 
The more conventional solution (if you wish to use ds materials) is to also check "Assume Vertical Normal"
 
Hi,

This may sound weird, but it is not a bug. This is exactly as the feature is supposed to work.

Those FlightsimX material settings are not used by the export, they are just stored in the MDL for the scenery engine. So the exporter just exports one polygon.

When rendering the scenery engine will notice the double sided setting. Based on it all polygons in that drawcall are drawn double sided, instead of the usual single sided. But there is no second polygon for the other side, nor are there any extra vertices created. And the normal is part of the vertex, not of the polygon. So that means the backside gets the same normal as the front. Which gives the shading issues.

So due to that the double sided option is not so useful indeed. Only when used with "assume vertical normal" the result will look OK (for some objects). Or else it is better to model two separate polygons. As long as they have the same material and are thus in the same drawcall, that should not hurt the performance much.
 
Thanks Arno and hcornea (is that the Doom avatar? :D) Can you qualify "for some objects"? I was going to test the "assume normal" option before I comment on it.

For the sake of an argument, wouldn't "double sided" switch make more sense if it did correctly what it advertised? That is, if applied, it would make a one-sided poly have a back side that is properly lit?

Misho
 
Hi,

I mean it will work on flat objects like signs or on cross trees. But a cube will look weird with the vertical normal, since all sides get the same shading.

For the double sided option, well seen from the graphics card it makes sense the way it works. All those material options translate well to call to the graphics card.
 
Hi,

I mean it will work on flat objects like signs or on cross trees. But a cube will look weird with the vertical normal, since all sides get the same shading.

For the double sided option, well seen from the graphics card it makes sense the way it works. All those material options translate well to call to the graphics card.


OK I will test this tonight, but what you are describing is exactly what I do not want : the same shading on both sides (I was describing that in my original post) For instance, a fence, during sunrise, should have side facing the sun bright, while the opposite side dark. What you are saying is that all faces will get the same shading, which is not the proper behavior.

Edit: I see what you are saying: the "equal shading" would indeed make sense for objects like 2-poly cross trees - the different shading of 2 polys would look extremely unnatural. for those objects, that option combined with "up normal" is definitely the way to go. For my fences - duplicate the geometry :( .

Misho
 
Last edited:
Back
Top