Jump to content

Recommended Posts

Posted

Hi , I was trying an ILS approach to Kobuleti last night in poor visibility and could not get it to work as expected.

 

I set the freq 110.30MHz in the ILS and made sure it was powered on, Set the course bug for 70deg (I zoomed in on the f10 view and used the ruler to determine the exact runway orientation.) I switched on the ILS mode on the NAV mode select panel, and flew towards the steerpoint marking the Runway. After a while I picked up the ILS signal and got steering cues on the ADI, I flew down the glide slope following the cues. Feeling really pleased with myself.... Until I clear the cloud base and I am not aligned with the runway at all. I am heading for the threshold but offset about 5 degrees to the stbd. This resulted in a missed approach, I found I had to adjust the course knob to 65 on the HSI to compensate.

 

I found the steering cues to be very different to what I am used to, the vertical cue was Ok once I realized that that changes with Roll angle rather than heading, but the Horizontal cue seemed pegged out of sight until the glide slope indicator (GSI) was very close to being lined up. Then it flashed into view and as soon as I was very slightly off the GS it vanished again, It seems slightly over sensitive, The small GSI tick on the left of the ADI was much more useful.

 

Cheers

Tom

Windows 10 Pro 64bit, Gigabyte EX58-UD5, Intel i7 920 Corsair H70 water cooled @4GHz), Corsair XMS3 12GB (6x2GB) DDR3 PC3-12800C8 (1600MHz) Tri-Channel, Nvidia GTX780, OCZ Vertex 256GB SSD (for OS+DCS), TrackIR 5, TM Warthog HOTAS + Saitek Rudder

Posted

I have not tried the ILS in this yet but the real world version has nothing to do with what your course setting is, the needle will just prob not point straight up but the localizer and glideslope should work normally.

 

In your example, was there some deviation on the localizer or did it show you lined up correctly?

 

I'll try it tonight in the A10 ans see what happens. Remember, the localizer needle covers 5 degrees deviation on each side only so they will only get active in that zone. The further you are away the less sensitive the needles will be for deviation. As you get closer they will get more sensitive.

With the price of ammunition these days do not expect a warning shot.

Posted

I have tried an ILS approach and I too felt the sensitivity in general, for both the localizer and the glideslope were a lot more sensitive than they would be in real life. Also the OBS knob in real life has no effect on the CDI indication of the localizer it simply helps the pilot with situational awareness to align the CDI with the extended centerline of the landing runway (you are correct RogueRunner) but in the game it was affecting the CDI's deviation which it should not do. I had to fly the approach visually the first time to "find the best" OBS setting that would give me reliable localizer cues to compensate for this issue. Once I had that dialed in it was ok, other than the extremely over sensitive glideslope and mildly over sensative localizer.

All in all it was do-able to get the plane on the ground, but not 100% correct or realistic in my opinion, but maybe military ILSs are slightly different than civilian hardware, although I doubt it.

Posted (edited)

I noticed this the other night whilst performing an ILS approach in to Kobuleti. If you follow the ILS localiser to the needle, you'll end up approx 5 deg off course (equates to about a plane width to the right of the runway). I even took a screen shot as I was quite surprised (will post later).

 

The localiser sensitivity of the needles seems about right, so I don't think there is anything wrong there however the GS does seem a bit tetchy. Could be WIP so I'll await the next beta before I make any decisions on it.

 

I love how you can pick up the localiser back course, particularly when you circle around after a 'touch and go'. Awesome.

Edited by CrashEd
Posted
I but in the game it was affecting the CDI's deviation which it should not do.

 

Ahh thanx SinandGrin,

 

Yeah, that most certainly is not correct. WIP I guess then :music_whistling:

With the price of ammunition these days do not expect a warning shot.

Posted

Incidentally, has anyone got the outer/inner marker beacons to annunciate? I tried enabling/turning up the volume on the intercom panel, but no joy as yet. Could also be WIP...

Posted

Sounds like the ILS is directing same as TCN.

For TCN it makes sense, because the TCN beacon is between the runway and taxiway and you get a 5° deviation in respect to the runway.

ILS should direct you to runway though, must be the beta gods.

Spoiler

AMD Ryzen 9 5900X, MSI MEG X570 UNIFY (AM4, AMD X570, ATX), Noctua NH-DH14, EVGA GeForce RTX 3070 Ti XC3 ULTRA, Seasonic Focus PX (850W), Kingston HyperX 240GB, Samsung 970 EVO Plus (1000GB, M.2 2280), 32GB G.Skill Trident Z Neo DDR4-3600 DIMM CL16, Cooler Master 932 HAF, Samsung Odyssey G5; 34", Win 10 X64 Pro, Track IR, TM Warthog, TM MFDs, Saitek Pro Flight Rudders

 

Posted
Sounds like the ILS is directing same as TCN.

For TCN it makes sense, because the TCN beacon is between the runway and taxiway and you get a 5° deviation in respect to the runway.

ILS should direct you to runway though, must be the beta gods.

 

You may well be on to something here. Lets hope it's fixed in the next beta (assuming it's not something stupid that I'm doing ;))

Posted

Page 459 of the manual has the freq

Windows 10 Pro 64bit, Gigabyte EX58-UD5, Intel i7 920 Corsair H70 water cooled @4GHz), Corsair XMS3 12GB (6x2GB) DDR3 PC3-12800C8 (1600MHz) Tri-Channel, Nvidia GTX780, OCZ Vertex 256GB SSD (for OS+DCS), TrackIR 5, TM Warthog HOTAS + Saitek Rudder

Posted

I am going to go home tonight and play with this. The theory for ILS and tacan being merged is wrong. two completely different systems. The steering data is derived differently too.

 

Reading the theory in the manual has left me just a little befuzzled.

Now where is that speed brakes control again?

 

[sIGPIC][/sIGPIC]

Posted

Nellis:

 

Twr - 132.55 VHF / 327.0 UHF

 

Gnd - 121.80 VHF / 275.8 UHF

 

TACAN Ch. 12 "LSV"

 

ILS Rwy 21L 109.1 "IDIQ"

 

Don't think Nellis is operational wrt to nav aids yet though.

Posted
Nellis:

 

Twr - 132.55 VHF / 327.0 UHF

 

Gnd - 121.80 VHF / 275.8 UHF

 

TACAN Ch. 12 "LSV"

 

ILS Rwy 21L 109.1 "IDIQ"

 

Don't think Nellis is operational wrt to nav aids yet though.

 

Cheers fella :thumbup: Hopefully it will be operational in beta2.

Posted

on the nellis tacan. CH 12? so 012 and X or Y.

 

Tacan is 126 channels. R and TR are matched mode and channel. Mode being X or Y.

 

A/A and A/A TR are 63 channels apart. So one aircraft is 63 and the other is 126.

Now where is that speed brakes control again?

 

[sIGPIC][/sIGPIC]

Posted (edited)
on the nellis tacan. CH 12? so 012 and X or Y.

 

Nellis TACAN is 012X.

 

EDIT: Added quote for clarity.

Edited by BlueRidgeDx

"They've got us surrounded again - those poor bastards!" - Lt. Col. Creighton Abrams

Posted
The theory for ILS and tacan being merged is wrong. two completely different systems. The steering data is derived differently too.

 

I didn't say ILS and TCN are the same system, I thought of an explanation for the bug nothing more.

Spoiler

AMD Ryzen 9 5900X, MSI MEG X570 UNIFY (AM4, AMD X570, ATX), Noctua NH-DH14, EVGA GeForce RTX 3070 Ti XC3 ULTRA, Seasonic Focus PX (850W), Kingston HyperX 240GB, Samsung 970 EVO Plus (1000GB, M.2 2280), 32GB G.Skill Trident Z Neo DDR4-3600 DIMM CL16, Cooler Master 932 HAF, Samsung Odyssey G5; 34", Win 10 X64 Pro, Track IR, TM Warthog, TM MFDs, Saitek Pro Flight Rudders

 

Posted
I didn't say ILS and TCN are the same system, I thought of an explanation for the bug nothing more.

 

My quote was more on the manual theory. and the fact that i was curious to see how it was modeled.

 

This is a system I am very intimate with in my job.

Now where is that speed brakes control again?

 

[sIGPIC][/sIGPIC]

Posted
Nellis

 

Twr - 132.55 VHF / 327.0 UHF

 

Gnd - 121.80 VHF / 275.8 UHF

 

TACAN Ch. 12 "LSV"

 

ILS Rwy 21L 109.1 "IDIQ"

 

Don't think Nellis is operational wrt to nav aids yet though.

 

 

Airport Communications

 

ATIS: 270.1

 

NELLIS GROUND: 121.8 275.8

 

NELLIS TOWER: 132.55 327.0

 

NELLIS APPROACH: 118.125 291.725



 

NELLIS DEPARTURE: 135.1 385.4

CLEARANCE DELIVERY: 120.9 289.4


ACC COMD POST - (HAVE QUICK TIMING A: 320.0

ACC COMD POST-(RAYMOND 22): 381.3

AF OPNS: 340.2

CLASS B (NORTH): 124.95 273.55

EMERG: 121.5 243.0

PMSV: 344.6

PMSV METRO: 323.9

PTD: 139.3 372.2

SFA: 321.1 326.2 385.5 397.2

SOF (CALL BULLSEYE SOF): 305.6

WX ASOS at VGT (8 nm W): 118.05 (702-648-6633)

WX ASOS at LAS (11 nm SW): PHONE 702-736-1416

WX ASOS at HND (17 nm S): 120.775 (702-614-4537)

WX AWOS-3 at BVU (19 nm SE): 118.475 (702-293-1532)

 

 

 

 

LA Center - 124.2 / 134.65 / 307.9 / 343.6

 

Nellis ILS:

 

Type: TACAN

 

Class: L-TACAN



 

Frequency: TACAN channel: 012X

Use at high altitude: yes


Hours of operation: 24

Morse ID: .-.. ... ...-

NOTAM facility: RNO (Reno)

FSS:

FSS hours of operation:

 

 

 

 

24TACAN AZIMUTH AND DME UNUSABLE:

 

020-035 beyond 30 NM below 8,000 FT,

 

035-080 beyond 20 NM,



 

080- 155 beyond 5 NM below 10,000 FT,

080-155 beyond 15 NM,


285-350 beyond 20 NM below 11,000 FT,

285-350 beyond 26 NM below 15,000 FT,

285-350 beyond 33 NM,

350-360 beyond 20 NM below 9,000 FT,

350-360 beyond 26 NM below 15,000 FT,

360-020 BYD 20 NM below 8,000 FT,

360-020 BYD 26 NM below 12,000 FT.

[sIGPIC][/sIGPIC]

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...