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

PAPI lights with Separation plane

Hi,

No, I would not expect that the lights change color if you move from left to right. If should only happen if your glide slope angle changes. So this could mean that the normal vector you are using is not 100% correct.

The vector should have the heading of the runway (and you need to hardcode that, as the command does not rotate with the heading you give it in the XML file). After that you need to pitch the seperation plane up so that you get the correct glide slope (usually 3 degrees).
 
Where i should pitch the sep plane? In the xml? I have already done this in the asm code for each light as suggested in post #27. Could you look it somebody please? It seems to me ok but i don't find the error in my code :( Thanks! Runway heading is 310 but i considered that the sep plane doesnt rotate with the model so i think its good.
 
Last edited:
Hi,

The command that you posted before does not contain any heading, only a pitch up (this pitching should all be in the ASM code, nothing needed in the XML file). Here is the code you posted, this command seems to be for a glide slope of 2.50 degrees.

Code: 
SEPARATION_PLANE nolgt_2, 0,32736,1429, 32767

To add the heading to it, you would have to do something like this. First I will only rotate the vector to the runway heading (so a glide slope of 0.00 degrees).

Code: 
SEPARATION_PLANE nolgt_2, 25102,0,-21063, 32767

If we know use that to scale the horizontal component of your first vector we can this:

Code: 
SEPARATION_PLANE nolgt_2, 1095,32736,-918, 32767

Btw, I think you can also set the last parameter to 0 instead of 32767, because you want to detect this plane directly and not with an offset of 1 meter (as 32767 is the length of the unit vector).
 
I rotated that part to the correct heading of the runway.

1095 = 1429 * sin( 130 )
-918 = 1429 * sin( 130 )

I did use 130 and not 310 degrees as a heading, because that is the direction the vector is pointing at (from the runway to the aircraft, so 180 degrees difference).
 
arno said:
I rotated that part to the correct heading of the runway.

1095 = 1429 * sin( 130 )
-918 = 1429 * sin( 130 )

I did use 130 and not 310 degrees as a heading, because that is the direction the vector is pointing at (from the runway to the aircraft, so 180 degrees difference).
Click to expand...


I think you wanted to write -918 = 1429 * cos(130)

Thanks arno! It works now, but you commuted the calculated values. You wrote:

Code: 
SEPARATION_PLANE nolgt_2, 1095,32736,-918, 32767

The correct is:

Code: 
SEPARATION_PLANE nolgt_2, -918,32736,1095, 32767

Otherwise the lights are always white.
 
Ok, I did not test the code, so it could be that I mixed that up :). Good to hear it is working now. Can you now also use the same vector for both sides of the runway?
 
Hi to all,
finally I was successfull by making a custom papi. But I still have a problem. Here's the code:
Code: 
SEPARATION_PLANE nolgt_2, -32000,0,0, 32767

	SEPARATION_PLANE quartoPezzo, 0, 1429, 0, 32767
	    BGL_LIGHT LIGHT_NAV, -1.320, 1.275, 10.985, 20, 0.60, 0.40, 0FFFAFCCEh, 0.000000, 0.000000, 1.000000 ; source poly num = 244
	BGL_JUMP_32 NOquartoPezzo
	quartoPezzo label BGLCODE
	    BGL_LIGHT LIGHT_NAV, -1.320, 1.275, 10.985, 20, 0.60, 0.40, 000FF0000h, 0.000000, 0.000000, 1.000000 ; source poly num = 244
	NOquartoPezzo label BGLCODE

	SEPARATION_PLANE terzoPezzo, 0, 1618, 0, 32767
	    BGL_LIGHT LIGHT_NAV, -1.320, 1.275, 3.673, 20, 0.60, 0.40, 0FFFAFCCEh, 0.000000, 0.000000, 1.000000 ; source poly num = 183
	BGL_JUMP_32 NOterzoPezzo
	terzoPezzo label BGLCODE
	    BGL_LIGHT LIGHT_NAV, -1.320, 1.275, 3.673, 20, 0.60, 0.40, 000FF0000h, 0.000000, 0.000000, 1.000000 ; source poly num = 183
	NOterzoPezzo label BGLCODE

	SEPARATION_PLANE secondoPezzo, 0, 1812, 0, 32767
	    BGL_LIGHT LIGHT_NAV, -1.320, 1.275, -3.632, 20, 0.60, 0.40, 0FFFAFCCEh, 0.000000, 0.000000, 1.000000 ; source poly num = 122
	BGL_JUMP_32 NOsecondoPezzo
	secondoPezzo label BGLCODE
	    BGL_LIGHT LIGHT_NAV, -1.320, 1.275, -3.632, 20, 0.60, 0.40, 000FF0000h, 0.000000, 0.000000, 1.000000 ; source poly num = 122
	NOsecondoPezzo label BGLCODE

	SEPARATION_PLANE primoPezzo, 0, 2000, 0, 32767
	    BGL_LIGHT LIGHT_NAV, -1.320, 1.275, -10.923, 20, 0.60, 0.40, 0FFFAFCCEh, 0.000000, 0.000000, 1.000000 ; source poly num = 61
	BGL_JUMP_32 NOprimoPezzo
	primoPezzo label BGLCODE
	    BGL_LIGHT LIGHT_NAV, -1.320, 1.275, -10.923, 20, 0.60, 0.40, 000FF0000h, 0.000000, 0.000000, 1.000000 ; source poly num = 61
	NOprimoPezzo label BGLCODE

nolgt_2 label BGLCODE

Seems that this papi work great within a certain distance from it, I mean, approaching my airport (about 2miles from papi) the lights are all white even If I'm on the right gp (which is 3°). I've made some tests: I slew up and let papi switch to 2-white & 2-red, right. If now I slew away from them, f.e 5-6 miles, the papi is still 2w-2r. This should not happens since I'm under the glidepath...

thanks!
 
Last edited:
GREAT!!! It works, I've forgot to calculate the vector's components with my runway heading.
 
Last edited:
ras78 said:
GREAT!!! It works, I've forgot to calculate the vector's components with my runway heading.
Click to expand...

Nice to hear that. But how can you use your papi lights? I gave it up because the BGL lights visibility range at daytime is very low and unrealistic. Do you know a method to increase it? Or how do you use it?
 
lambda said:
Nice to hear that. But how can you use your papi lights? I gave it up because the BGL lights visibility range at daytime is very low and unrealistic. Do you know a method to increase it? Or how do you use it?
Click to expand...

Hi Lambda, sincerly I dunno how to increase light visibility. However somebody did that, I've red some posts here in the forum, try to search.
bye!
 
ras78 said:
Hi Lambda, sincerly I dunno how to increase light visibility. However somebody did that, I've red some posts here in the forum, try to search.
bye!
Click to expand...

A lot of designer try it but without results. Unfortunately, the visibility can not be increased.
 
PAPI Problem

Has anyone asked the designers at UK2000? Here they have custom made PAPI and Runway Lights (not afcad overlay). I shall try, but they may not want to give away secrets!
 
Oh, well, making runway lights without any AfW or similia is easy, just work on nav_light object. I've made my LFRK's lights in that way and also a working PAPI. The most important part, imho, is place the lights with correct postition & distance...just to make them as real as possible.
 
You must log in or register to reply here.
Back
Top