Jump to content

Recommended Posts

Posted

I'm trouble with a few of the instrument navigation tools and despite checking the manual and youtube I just can't figure out what I'm doing wrong.

Issue #1 (F1CE & F1EE) - VOR/ILS

I can tune in a VOR/ILS station (correct frequency and VOR to Marche). I can hear the morse code from the station (TACAN volume is turned off so it has to be the VOR/ILS station) but I can't get the VOR station bearing to show up on the IDN (in the CE I've selected VT mode and in the EE I've selected RNAV-N and switched the Narrow needle selector to VOR).

Despite this, in both the CE and EE the VOR needle stays stuck to N indicating it's not picking up a signal (despite me hearing the morse code from the station). As a result I can't intercept the glidescope for an ILS approach. It's driving me nuts. What am I doing wrong?

I've got no problem tuning and navigating off TACAN stations (including course/omnibearing and using the Autopilot to "catch" the omnibearing course)

Issue #2 (F1EE only) - TACAN offset

I can configure TACAN offsets in the CE fine but in the EE no matter what i enter for distance and angle, when I switch to RNAV-VA it doesn't seem to reflect the offset distance and angle in the IDN. Not as annoying as the above issue because in the EE I can always configure an INS waypoint for the offset position but i don't understand how I'm doing it correctly on the CE but same thing on the EE doesn't work. Any ideas?

Posted
22 minutes ago, drPhibes said:

Is the "VOR-ILS/OFF/TACAN and OMNIBEARING" selector (switch 21 on p.19 in the manual) set correctly?

Yes because when I'm using TACAN for navigation the ADI is showing the yellow course line correctly (selector is "up" for TACAN). When I want to switch to VOR or  ILS I move that selector to the bottom VOR/ILS position

Posted (edited)
1 hour ago, omohat said:

VOR needle stays stuck to N indicating it's not picking up a signal (despite me hearing the morse code from the station). As a result I can't intercept the glidescope for an ILS approach. It's driving me nuts. What am I doing wrong?

ILS does not transmit bearing to station, only localizer and glideslope deviation. So the bearing needle won't show the direction when tuned to ILS frequency. It may keep showing bearing to TACAN depending on how the aircraft is wired.

ILS also does not transmit DME by itself, but most real world installations combine it with DME beacon. But last time I checked, DCS still does not simulate ILS/DME stations so you won't get DME on ILS frequency either.

Edited by some1
  • Like 1

Hardware: VPForce Rhino, FSSB R3 Ultra, Virpil WarBRD, Hotas Warthog, Winwing F15EX, Slaw Rudder, GVL224 Trio Throttle, Thrustmaster MFDs, Saitek Trim wheel, Trackir 5, Quest Pro

Posted

Ok. So then use TACAN (or VOR) to line up with the runway radial, and then ILS (autopilot G mode) to capture the glidescope? I guess the process would look something like this:

  1. Set TACAN channel
  2. Tacan to T/R
  3. Set omnichannel bearing to runway course
  4. Set omnichannel source to TACAN
  5. Autopilot on and R mode armed
  6. Once runway radial is captured and being flown, start descending to capture the glidescope
  7. Configure ILS frequency
  8. ILS On (Marche)
  9. Set omnichannel source to VOR/ILS
  10. Autopilot G mode armed (do I have to turn off R mode or will it be turned off automatically when the glidescope is captured?)
  11. Wait for glidescope to be captured; then manage throttles to control AoA

Is that right?

Posted

Yes, classic ILS approaches in real life (that do not depend on GPS/INS waypoints) are usually oriented in relation to ADF, VOR or TACAN. You would fly some sort of procedure turn, arc, or just be vectored by ATC to intercept ILS localizer. The ILS approach procedure in real life not only gives you ILS parameters, but also tells you how to get to the point where you intercept the ILS needles.

If you don't have the charts or don't want to fly the whole procedure, then an easy to remember aiming point to intercept ILS is a waypoint on runway course, 10 nm before the threshold and 3000 ft above airport elevation. 

https://www.digitalcombatsimulator.com/en/files/3320451/

vdocuments.mx_charts-5584598aefd8e-10.pn

Hardware: VPForce Rhino, FSSB R3 Ultra, Virpil WarBRD, Hotas Warthog, Winwing F15EX, Slaw Rudder, GVL224 Trio Throttle, Thrustmaster MFDs, Saitek Trim wheel, Trackir 5, Quest Pro

Posted (edited)

Ok thanks. I'll try that. Based on what you've said I was probably too high to catch the glideslope.

Anyone have any tips on TACAN offset in the EE? That one is still vexing me.

Edited by omohat
Posted (edited)
5 hours ago, omohat said:

Ok thanks. I'll try that. Based on what you've said I was probably too high to catch the glideslope.

Anyone have any tips on TACAN offset in the EE? That one is still vexing me.

 

Place IDN in the middle positions to set the offset, like on the Radio based offset from the CE. and the mode to RNAV-VA. (va = vector additionel) same as on the CE.

Oficial manual page 208 EE annex.

 image.pngnull

Edited by Coragem
  • Recently Browsing   0 members

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