F4 Phantom ILS Question - How to?

[Oesau]

Sorry @Bailey - late night post so wasn't very clear.

I'm spawning on the runway at Batumi, runway 31 (despite the wind its spawned me facing downwind), as you track down the runway the lateral bar is actually offset. Once you get airborne tracking out over the ocean for approx 3nm then the localizer signal is lost. Turning around to runway 13 doesn't change it, no signal is received. I've attached the mission file here 

Now I tried a mission spawning in the air and approaching Batumi, the ILS signal is detected however again, the lateral bar is offset to the right.

Happy to be pointed out that I am doing something completely wrong but I just don't think I am (again the F-1 CE works fine)

 

F-4E ILS Test Batumi.miz

[Bailey]

3 hours ago, Oesau said:

Sorry @Bailey - late night post so wasn't very clear.

I'm spawning on the runway at Batumi, runway 31 (despite the wind its spawned me facing downwind), as you track down the runway the lateral bar is actually offset. Once you get airborne tracking out over the ocean for approx 3nm then the localizer signal is lost. Turning around to runway 13 doesn't change it, no signal is received. I've attached the mission file here 

Now I tried a mission spawning in the air and approaching Batumi, the ILS signal is detected however again, the lateral bar is offset to the right.

Happy to be pointed out that I am doing something completely wrong but I just don't think I am (again the F-1 CE works fine)

 

F-4E ILS Test Batumi.miz 12.74 kB · 1 download

That mission is working for me. I took off and executed an ILS approach to landing.
1. Turn on your NAV volume so you know if the aircraft actually lost the signal.
2. Ensure the correct freq for the navaid is in. In this case 110.30. (Hear the beeps)
2a. TURN ON THE FLIGHT DIRECTOR!!! It is off by default (for some reason, idk. I typically forget this step and realize it when I don't get steering).
3. Typically I don't use ILS/LOC for takeoffs. The use of the ADI steering bars is a legit use for low visibility takeoffs, but I would not recommend it. Use the heading bug. (This can also be a good time to dial in your ILS course, which is 120 here.)
4. After takeoff maneuver for a ILS landing for RWY13. I like to turn north and then hang a long left coming inbound.
5. Make sure you have the magnetic course of the runway in the HSI course window. The HSI deviation bar will handle itself, but the HSI course window commands the ADI steering bars.
6. Fly TO the ILS/LOC and you will be able to intercept the ILS with the ADI steering bars. 
7. Follow the ILS down.

If you are still having issues, feel free to post a full length video (or track, I guess) and we can check it out.

Edited June 4, 2024 by Bailey

[XCNuse]

ILS has been super spotty for me.

On NTTR for example I might pick up the ILS once, and then it might never come back despite coming back onto profile.

Last time I tried for example I was on a back course for 21L ILS, and it connected; flags dropped and all was displaying. However, once I turned final, the flags came up, and being within profile, it never came back online.

 

Something is absolutely bugged; it shouldn't be that despite making several attempts now on 21L at Nellis on NTTR, I've only had it work one time, despite doing everything correctly each time.

 

But the example I gave is evidence something is bugging out; it shouldn't be that if you pick up an ILS on a back course, and turn inbound, and it not functioning again despite no changes.

[Oesau]

7 hours ago, Bailey said:

That mission is working for me. I took off and executed an ILS approach to landing.
1. Turn on your NAV volume so you know if the aircraft actually lost the signal.
2. Ensure the correct freq for the navaid is in. In this case 110.30. (Hear the beeps)
2a. TURN ON THE FLIGHT DIRECTOR!!! It is off by default (for some reason, idk. I typically forget this step and realize it when I don't get steering).
3. Typically I don't use ILS/LOC for takeoffs. The use of the ADI steering bars is a legit use for low visibility takeoffs, but I would not recommend it. Use the heading bug. (This can also be a good time to dial in your ILS course, which is 120 here.)
4. After takeoff maneuver for a ILS landing for RWY13. I like to turn north and then hang a long left coming inbound.
5. Make sure you have the magnetic course of the runway in the HSI course window. The HSI deviation bar will handle itself, but the HSI course window commands the ADI steering bars.
6. Fly TO the ILS/LOC and you will be able to intercept the ILS with the ADI steering bars. 
7. Follow the ILS down.

If you are still having issues, feel free to post a full length video (or track, I guess) and we can check it out.

 

@Baileythanks for the reply, will post a video & track later on in the day but confirm I have setup it up as per your steps (note on 3 - no I don't use ILS for takeoffs, it was just that I had 110.30 setup in the ME so noted it was active [morse code received and confirmed] when I spawned on the runway).

[Dominik96]

Hey!
Thanks you @Hawkeye_UK for the tracks. I found 2 bugs- one causing VOR/ILS problems when flying AWAY from the course selected (reason why you could not get proper steering to fly over the VOR station and possible the reason for your problem @Oesau) and another one- causing problems at some frequencies when switching between VOR and ILS (reason why the ILS did not work in the 2nd track). Will be in the patch, hopefully that fixes most VOR/ILS issues (besides that known DCS wind problem).
And many thanks again for the tracks- without them it would be much harder to track these issues.

[Hawkeye_UK]

On 6/20/2024 at 1:08 PM, Dominik96 said:

Hey!
Thanks you @Hawkeye_UK for the tracks. I found 2 bugs- one causing VOR/ILS problems when flying AWAY from the course selected (reason why you could not get proper steering to fly over the VOR station and possible the reason for your problem @Oesau) and another one- causing problems at some frequencies when switching between VOR and ILS (reason why the ILS did not work in the 2nd track). Will be in the patch, hopefully that fixes most VOR/ILS issues (besides that known DCS wind problem).
And many thanks again for the tracks- without them it would be much harder to track these issues.

No problem - it was clear straight away after repeated testing there was a problem and not map specific.  Good to hear the bug is fixed, look forward to that although alas my phantom time has been low these last few weeks, will be putting alot more time into it again this month all being well.

Fantastic module, really excellent release.

[Predator-78]

I also encountered this problem on the Caucasus map and I came across this discussion by doing a Google search. Apparently the problem has not been solved yet, because for me too the red flags appeared on the ADI on Kutaisi airport. In the editor I had to add the wind higher than 6 knots and the opposite direction on the landing strip.

[Zabuzard]

I also encountered this problem on the Caucasus map and I came across this discussion by doing a Google search. Apparently the problem has not been solved yet, because for me too the red flags appeared on the ADI on Kutaisi airport. In the editor I had to add the wind higher than 6 knots and the opposite direction on the landing strip.

As Dom explained, the wind thing is a DCS engine problem.

Can you produce a short working track, then we can see if there is more we can fix from our side. Cheers

[Predator-78]

11 ore fa, Zabuzard ha scritto:

Come ha spiegato Dom, la questione del vento è un problema del motore DCS.

Puoi produrre una breve traccia di lavoro, così possiamo vedere se c'è altro che possiamo sistemare da parte nostra. Saluti

Thanks for your reply, I can only attach the mission editor file but I think it would be useless. I guess your team has already reported it to DCS...