@zwen Yeah I've noticed that. I think it's because the SWL-10's ILS "ended" right at the threshold, and yours "ended" at the opposite end of the runway.

@PlaneFlightX Well full needle deflection is only 5 degrees off course. It will become very sensitive when you get close to the runway (end, indeed). At a few miles from the threshold, you need to be really off-center to observe the indicator move away.

@zwen What I've found is that if I fly parallel to the runway at an offset like you said, the indicator stays where it is.

EDIT: I just tested it myself, and it does get more sensitive, but not as sensitive as I was expecting.

@PlaneFlightX I don't quite get what you mean by the sensitivity of localizer. In theory if you fly parallel to the runway at an offset, the needle should drift away because the course deviant becomes greater when you get closer to the runway.

@zwen Thank you for your response! I haven't tested it but I should be able to do that in an hour or two. Another question, are you aware the sensitivity of the localizer doesn't change? It's as if it's a rectangle or something.

@PlaneFlightX If I can still remember, LOCX and Y are runway ends because localizer antennae are situated there (approximately) and GSX and Y are touch-down zone. RAD is the radial of localizer (aka runway heading) but it is there if you need to offset the signal. ALT is just Altitude-AltitudeAgl. For calculation, I once used GeoGebra (free) to map all coordinates and calculate IAF and FAFs and other navaids. Because the coordinates in SP are projected (ie. in meters not DMS), it is easier to work on it than trying to fit into a GIS system.

@PlaneFlightX Sorry for the late reply. Actually, those numbers are touch-down zone (biggest white block) and runway threshold (piano keys on the other end of runway) coordinates. I literally drove the buggy to that spot and used debug function to take measurements.

Hi again, I'm working on modifying your ILS to suit my systems, and I have a question.
How did you calculate the latitude and longitude values for each runway threshold? I've noticed there are two latitude and two longitude values per runway, and I'm not sure how they were calculated. I'm asking this because I want to add two more airports into the system. I managed to reverse engineer the math and got pretty close, but my glideslope is off a bit.

@Guat3757 Sorry to hear that, unfortunately, however, I have been far away from SP in the past year or so even though I had had a passion to make a very advanced AP system. (And I've been addicted to XP and MSFS😂) What comes down to the basis of these FT codes is just trigonometry, and the glideslope is calculated from the arcsine or arctangent function (△Height divided by horizontal or spatial distance to TDZ). For anyone interested, please feel free to explore the possibilities of the basic algorithm!

@FlightFun Yes

@Guat3757 are all the variables in the right order?

Hi, I tried to install this ILS with the HUD on another plane but for some reason I’m not getting the glideslope. Localizer works great but the glideslope won’t come alive at all, stays at half dot down deflection. Checked the variables several times but can’t find anything.

Ok, thanks!

@FlightFun Hi, IIRC you need to copy a few variables using the lower-right button with an "x" on it. They define the location of the simulated beacon. If ILS still doesn't move, you might be too far away from the runway. I haven't touched SP for a while and don't know if anything has changed.

Hello, I have been playing SP for a wile now, and I saw your ILS system and tried to copy it over to my new aircraft but It did not work, and the ILS doesn't move...

can anyone help me out?

Hi! I cam back to SP (and the long days of staring at code) after a while, and I have a few things to share!

First of all, I have released my SWL-10. This aircraft, among other things, features a fully functional autopilot, and a working ILS (Version 1). A link is included above.

Second of all, I am working on a new plane, the SWL-120. The SWL-120 is a 787-767 hybrid, and will have a redesigned autopilot, and the ILS will be based off yours! I am planning to incorporate your ILS codes (and HUD) into the flight systems.

@PlaneFlightX Hi! Changing the glide slope is fairly simple. You only need to change the variable GlideSlope into 6 - clamp(atan(), 5, 7). And in the display, you need to change the multiplier. If you use the HUD, the code will be voffset={GlideSlope * 2 + 0.5425}.

I think if you want to make it easy to tune in the frequency, 0.5 is fine. You just need to redefine all the frequencies in the variable list (in the activator field). In real life, the NAV frequency often adds by 0.05, and for COM it can be 0.025.

Also, really looking forward to your new design!

Just came back to here to look at something.
.
I too hope SP will someday add a turnable nob. For now, I've used magnets and rotators with buttons to make a similar equivalent.
.
I do have a question - I'm planning on integrating your ILS into the displays in the cockpit of my SWL-120, and I was wondering - how many decimal points does my input system need to be able to be fine-tuned to? Currently it's .5 of a number, but does it need to be any more?
.
Also, is there any way to easily change the glideslope? I really think 5-7 degrees is good for SP, even though 3 is the norm for IRL.

@SnoWFLakE0s I find variables really useful at retaining values! I think my next step is to make a dial input, but I hope SP will someday add the turnable nob button 🙃

Awesome, so you must've understood how the input dialog works!

@edensk It just seems like it's a little shallow.

@PlaneFlightX The most typical glide slope is about 3 degrees

I just tested it at Wright, and it's pretty good! I will say the glideslope is shallow, so I'd recommend changing that to be a bit bigger (5 degrees maybe). I'm not at home right now so I can't fully test it. I would also like to use a slightly modified version of this in my SWL-120.

@PlanariaLab
@PlaneFlightX
@SnoWFLakE0s