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

Vertical Separation Plane

Messages
139
Country
unitedkingdom
Hi Jeffrey

In FS9/ASM I used to be able to do a vertical separation plane for switching runway lights from one colour to another when you passed them. Can SODE do the same thing? I've come across an issue where the edited mipmaps of the textured lights work correctly until you view the plane from the side and FS thinks you are miles away so displays the highest mipmap and so you get a "flare". I was hoping to combat this by limiting the display of the textured plane to 178 degrees either side, so for example the red side would be 1-179 degrees and the white side would be 181 to 365. Is there any way to do this with the current SODE and if not is there any way this functionality could be added in?

Cheers
Will
 
Hi Will,

That was exactly what I have seen when using the mip map technique, the flare phenomenon that is, when viewing from a 90 degrees angle. So it must be considered a limitation of that technique. Or have other developers who employ mip mapped lights been able to tame that flare?

While it would be possible to achieve separation using separation planes (you can set them up in any position), it would come with a performance cost: The computation must be done for each and every lamp (or pair of lamps in case of runway edge lights) and that's not something I'd recommend. However, if it is only for a handful of lights, like threshold lights, using a SODE separation plane for those is fine performance wise.
 
I had tried to tame it by using LODs alongside the mipmaps but that also didn't work correctly, so if someone is using them it'd be good to know how they got around it.

It should only be for a max of 12 lights that will need this. The threshold/ends and papis will be left for now as they are not noticeable when flying. The runway lights are rotate to user so only have 1 plane instead of 2 crossing.

Is the process the same as it would be for the PAPI lights in GMAX? Is there anything in the XML file that I'd need to change (i.e. elevation or azimuth)?
 
Yes, the process is the same as for PAPI's (attaching the visibility tags). You'd need to set the elevation to 90°, azimuth can be left at zero.
 
Back
Top