ILS on HUD broken?

[SpecteRED]

I cant see any ILS symbology on HUD. No synthetic runway. I caught the ILS siglalnull

[Ramsay]

1 hour ago, SpecteRED said:

I cant see any ILS symbology on HUD. No synthetic runway. I caught the ILS signal

Do you have a waypoint (but) selected with the runway's (true) direction and glide slope programmed ?

Details

Assuming the ILS is transmitting.

1. If the landing waypoint was setup in the ME

• Select the landing waypoint (CP/PD will already have the Runway Heading and Glide Slope filled in)
• Contact ATC or check the mission briefing for the QFE and set the altimeter accordingly
• Set the ILS frequency (adjust ILS volume / check audio ID / HSI flags)*
• Set APP mode on the PCA
• Land using the ILS and HUD

HUD localiser guidance will appear with localiser signal and aircraft heading is within +/- 6° of Runway Heading

The HUD's Synthetic Runway will appear when BOTH localiser and glide slope signals are being received.

* if the runway's ILS is not working you will not have the HUD localiser/synthetic runway symbology

2. If the landing airport has not been set up in the ME

• Contact ATC and check which runway is active and it's QFE
• Set the ILS frequency (adjust ILS volume / check audio ID / HSI flags)*
• set the altimeter to QFE (ATC usually gives it in inHg, so you'll need a table to convert to mbar/hPa)
• Select the active waypoint you are going to use to land (1-20), it's co-ordinates are unimportant (say waypoint 19).
• PREP the waypoint runway info on the PCN (PREP 19 INS)
  • turn the PCN selector to CP/PD (RH/DS in the English cockpit)
  • enter the runway's true heading in the left field i.e. 179.0°T
  • enter the desired glide slope in the right field i.e. 3.0°
• Set APP mode on the PCA
• Land using ILS and the HUD

This is covered in Chuck's M-2000C Guide (Part 13 - Navigation & ILS Landing, Page 318)

https://drive.google.com/file/d/1jmp9ueZo9xOPyGzo3YO0AnFYEH-5Iotr/view

Edited April 10 by Ramsay

[SpecteRED]

thx, the runway's true heading was incorrect

[SpecteRED]

16 часов назад, Ramsay сказал:

https://drive.google.com/file/d/1jmp9ueZo9xOPyGzo3YO0AnFYEH-5Iotr/view

Is there any way not to use the waypoint at the airfield, but to use TACAN instead? for example, I want to land at another airport not from my plan. and can I display the distances to TACAN on HUD?

[Ramsay]

17 hours ago, SpecteRED said:

Is there any way not to use the waypoint at the airfield, but to use TACAN instead?

The synthetic runway is drawn and scaled on the HUD using the height above the airfield (QFE), Glide Slope (PCN waypoint info), runway/ILS bearing (PCN waypoint info) AND that you are "on" the LOCALISER and/or GLIDE SLOPE signal.

It does not reference or use the waypoint's coordinates i.e. when landing at Vaziani (1500 ft MSL) if your altimeter isn't adjusted to QFE, the synthetic runway will be drawn smaller and further away as higher in glide slope --> greater distance from landing point.

 

17 hours ago, SpecteRED said:

[Can I... } use TACAN instead?

No, TACAN does not have the Glide Slope and Runway Direction required or generate an ILS beam.

 

17 hours ago, SpecteRED said:

... can I display the distances to TACAN on HUD?

No, the radio navigation used in the M-2000C is backward compatible with earlier models - so can provide steering guidance to TACAN Offsets (VADs), etc. but these are limited to being functions of the HSI.

 

 

 

Edited April 12 by Ramsay

[Galinette]

All good responses!

When approach symbols are missing, also check if you did not press the Palette SNA (Magic Slave, Designate, etc...) which in ILS approach mode declutters the HUD. Press again to get ILS back.

Edited April 12 by Galinette

[Amarok_73]

Recently I observe the issue with approach autopilot and synthetic runway symbology.
It is like something is really messed-up as the approach dashed line and synthetic runway are totaly not at the correct places, and the square that should show correct approach path is just pointing directly to the airport instead of leading to the localizer/glideslope path. 
Is it something with my game, or it's confirmed that there's such problem now with the module?

[BJ55]

It's something on your side, check procedures or remove mods.

[Amarok_73]

On 10/25/2025 at 6:48 PM, BJ55 said:

It's something on your side, check procedures or remove mods.

I ran a test under controlled conditions, after a full repair, without any mods, and it turns out the problem is with the module and the game.
It seems that the further away from the airport, the more the autopilot's target point appears to be somewhere outside the airport. As you approach, this point moves towards the actual airport position. However, if you engage the approach autopilot early on, and additionally, with a larger deviation from the approach course, the square marking the approach path for the localizer and glideslope will not follow the actual approach path, but rather to the one marked to the incorrectly indicated point, which also draws a synthetic image of the runway.
I suspect there's no way to correct this behavior without digging into the software sources associated with the aircraft module, so until the dispute between ED and Razbam is resolved, we can't hope to fix this.

EDIT: Sorry for mistake with track file. I sent the correct one in the recent reply to this topic.

 

Edited 1 hour ago by Amarok_73

[Ramsay]

On 10/25/2025 at 12:56 PM, Amarok_73 said:

Recently I observe the issue with approach autopilot and synthetic runway symbology.
It is like something is really messed-up as the approach dashed line and synthetic runway are totaly not at the correct places, and the square that should show correct approach path is just pointing directly to the airport instead of leading to the localizer/glideslope path. 
Is it something with my game, or it's confirmed that there's such problem now with the module?

Your picture of the APP HUD with a misplace ILS Localiser Line and Synthetic Runway is typical when using a PCN "Landing" waypoint that has an incorrect Runway direction i.e. the runway heading entered should be it's TRUE heading.

I'm currently reinstalling the Sinai Map to view your posted track before providing further feedback. 

Additional Info
Here is an example of what happens when the runway heading is set incorrectly

Edited 10 hours ago by Ramsay
Add example screenshot

[Ramsay]

20 hours ago, Amarok_73 said:

I ran a test under controlled conditions, after a full repair, without any mods, and it turns out the problem is with the module and the game.
...
M2K ILS and app autopilot problem.trk 3.2 MB · 4 downloads

Unfortunately your example track file doesn't make assisting you easy, as it starts in the F10 map and switches between simulation speeds and viewed aircraft, before you even enter the Mirage 2K (not sure if you do as I quit the replay after 5 min of watching). Is it the track file you intended to upload ?

Can you submit a shorter track demonstrating the problem (perhaps using the default Caucasus map so more people can view / help) ?

Edited 8 hours ago by Ramsay

[Amarok_73]

Sorry, it seems the track I shared was from other mission. 
Here's the correct one,that shows pretty clearly what I am talking about.
 

M2K ILS and app autopilot problem Caucasus.trk