Various avionics inconsistencies

[Bestandskraft]

In the course of this report, I will be referring to the book "MiG-21 Pilot's Operating Instructions", a .pdf of which can be found at http://forums.eagle.ru/showthread.php?t=138880. Page numbers referring to that manual always refer to the hardcopy page number, not the .pdf page number.

 

1. Page 50 of the game manual describes gauge 59 as the "Pilot's O2 pressure gauge", which is consistent which the MiG-21 manual, Fig. 33. However, IMHO the pressure gauge actually is element 39, erroneously described on page 49 of the game manual as "Pilot O2 level gauge", since this element is scaled in kg/cm2, which is not a measurement of quantity, but of pressure. On the other hand, during flight gauge 59 seems to behave like a cabin altimeter, not like a quantity indicator of anything.

 

2. Page 76 of the game manual states that when cold starting the aircraft, with only the battery and the two PO-750 converters on, all red lights are illuminated. In fact, 4 red lights are NOT illuminated (Marker, Fire, 450 l remaining and Switch off ignition). Also, the list of illuminated lights is not complete, since also the AC generator off warning light and the No 1/3 TK GP Pump lights are illuminated.

 

3. Page 72 of the MiG-21 manual implies that the fuel quantity is indicated on the fuel indicator even when electrical power has not yet been applied to the jet. In the game this is not the case. Instead, the fuel quantity is only indicated when switching on the battery. However, once the battery is switched off again, the fuel quantity remains indicated.

 

4. Page 76 of the MiG-21 manual states that when checking the wheel brakes, one should expect a brake pressure of 9-10 kgf/cm² both with the nosewheel brake engaged or disengaged. In the game, the indicated pressure is 11-12 kgf/cm².

 

5. Page 76 of the MiG-21 manual states that when performing a lamps test, the No. 1/3 TK GP empty (1/3 ГР. ВАКОВ) lights illuminate only with the No. 1/3 TK GP Pump circuit breakers turned on, and the No. 1-4 RKT Zero PSN (НУЛЬ. ПОЛОЖ. РС НО. 1-4) lights illuminate depending on the external loads carried (which implies that there are cases in which they do not illuminate when performing a lamps test). In the game, when performing a lamps test, both groups of lights illuminate regardless of the status of the No. 1/3 TK GP Pump circuit breakers and external loads carried. Is this a case of a bad translation of the manual or does the in-game behavior not correspond to the real jet?

 

6. Page 77 of the MiG-21 manual states that when the ДА-200 Comb. Instr., Sig. of vert. gyro of HSI, AFCS, RDR (ДА-200, СИГНАЛ. ГИРОД. КСИ, САУ, РЛС) switch is set to ON, both the gyro horizon indicator (ADI) warning light and the Caging of vert. gyros of HSI, AFCS, RDR (АРРЕТИР. ГИРОД. КСИ, САУ, РЛС) light are supposed to illuminate. It is implied they illuminate continuously until the Vert. gyro of HSI, AFCS, RDR, gyro hor. sig. (ГИРОД. КСИ, САУ, РЛС, СИГНАЛ. АГД) switch is set to ON, after which the warning lights extinguish within 15 seconds. However, in-game, only the Caging of vert. gyros of HSI, AFCS, RDR (АРРЕТИР. ГИРОД. КСИ, САУ, РЛС) illuminates, but extinguishes after about 2 seconds without the Vert. gyro of HSI, AFCS, RDR, gyro hor. sig. (ГИРОД. КСИ, САУ, РЛС, СИГНАЛ. АГД) switch being on. Once this switch is on, both warning lights illuminate, and extinguish within about 3 seconds. Also, the entire process only works when the engine is running and the DC generator is on, even though the MiG-21 manual implies that it should work without a running engine and only external power connected.

 

7. The RSBN/ARC check described on page 79 of the MiG-21 manual cannot be performed when the engine is not running and the DC generator is off in-game, even though the manual implies such a check is possible with only external power connected.

 

8. According to page 80 of the MiG-21 manual, pressing the IDENT button while the SOD transponder is set to LANDING, SINGLE should cause the SOD ATC RESP. lamp to illuminate. This does not seem to work in the game.

 

9. Page 82 of the MiG-21 manual describes the engine warm-up procedure. At an LP rotor speed of 88-90%, oil pressure should be 3.5-4.5 kgf/cm². When doing the test in-game, the oil pressure is about 5 kgf/cm².

 

10. Pages 148-149 of the MiG-21 manual describe the radar check. In the game, the check seems to be generally implemented, but it does not function exactly as described on these pages. Is the radar check supposed to be fully implemented and working as described in the MiG-21 manual?

 

11. Page 160 of the MiG-21 manual seems to imply that when performing turns, the sight reticle drifts to the side opposite the turn only in GYRO mode, since the manual specifically advises one to switch from MSL to GYRO mode temporarily to check this behavior. In the game I cannot see a difference in reticle movement between MSL and GYRO modes.

 

12. Page 163 of the MiG-21 manual seems to imply that for the ПОДВЕШЕН 1-4 ВНЕШН lights to illuminate, ground power has to be connected, the battery and DC generator as well as the MSL, RGM, CG Heat (ОБОГР. СС. РНС; ФКП), PWR to RKT pods 1-2 (ПИТАН 1-2 УБ; ПБД) and/or PWR to Ext. Stores 3-4 (ПИТАН ПОДВ 3-4) circuit breakers have to be on. In the game, the only requirement is that the battery switch be on.

 

13. Likewise, page 167 of the MiG-21 manual seems to imply that the MSL, RGM, RKT LCH (ПУСК СС. РС. РНС) and PWR to RKT pods 1-2 (ПИТАН 1-2 УБ; ПБД) circuit breakers must be on while external power is connected in order to check the ПОДВЕШЕН 1-4 ВНЕШН lights when rockets are carried. Again, in the game, the only requirement is that the battery switch be on. Related real-world question: Assuming the real plane works as described on page 167, why is it enough to switch on the PWR to RKT pods 1-2 (ПИТАН 1-2 УБ; ПБД) in order to see the No. 3 and 4 station lights illuminate with rockets carried, while for missiles one also has to switch on the PWR to Ext. Stores 3 – 4 (ПИТАН ПОДВ 3-4)?

 

14. Page 170 of the MiG-21 manual states that when ground power is connected, enabling the GUN switch is sufficient for the GUN READY light to illuminate. In the game, a RELOAD button additionally has to be pressed to get the green light. Is the manual or the in-game implementation wrong?

Edited April 25, 2015 by Bestandskraft
Paragraph 1) updated

[Bestandskraft]

15. It does not seem to be possible to perform a sight check as described on pp. 68-69 of the MiG-21 manual. Beside various actions described there not causing the expected result, for the sight to even work it seems to be necessary to switch on the ДА-200 Comb. Instr., Sig. of vert. gyro of HSI, AFCS, RDR, the Vert. gyro of HSI, AFCS, RDR, gyro hor. sig and the DC generator in addition to the battery, the AC generator and the No. 2 PO-750 inverter, which, according to page 68, in combination with external power are supposedly the only requirements for the sight to work.

 

16. Page 70 of the MiG-21 manual states that in order to check the SPO-10 RWR for serviceability, the pilot has to depress the test button on the SPO-10 equipment indicator, his own aircraft radar operating at this time. In the game, the check works even with the radar switched off.

 

17. Since in the game, pressing and holding CV50 causes the nose cone to extend, it is not possible to check the БОВ-21 unit as described on page 84 of the MiG-21 manual. Of course, since there is no ground technician in the game, one could not perform the check anyway, I'm just wondering how this check is performed in the real jet when doing so would cause a compressor stall.

 

18. According to page 161 of the MiG-21 manual, the air relight system automatically gets engaged for 6 seconds when launching missiles, indicated by the "Switch off ignition!" warning light. This does not seem to happen in-game.

Edited May 1, 2015 by Bestandskraft

[Bestandskraft]

19. In the game, it is impossible to jettison the drag chute or to drop chaff/flares if the respective button cap is closed, even with the appropriate keystrokes, but weapons and the SPRDs can be released without first manually opening the guard. It would be nice to have a consistent solution here, my preference being that first unguarding the switches is always necessary.

 

20. According to page 56 of the MiG-21 manual, the radar range gate is only controlled by the throttle grip in MSL-AUTO mode. In the game, it always moves when the throttle grip is turned. When Continuous anti-jam mode is selected, the throttle grip should change receiver sentitivity (see also page 153 of the MiG-21 manual). In the game, enabling Continuous mode just lets strobes disappear; adjusting sensitivity with the throttle grip is not possible.

 

21. In the game, the position of the throttle grip and thereby the range gate has an influence on whether a target can be successfully locked in fixed-beam mode, even though the range gate cannot be seen in this case. Neither the game manual nor the MiG-21 manual indicate that this is supposed to work that way.

 

22. Page 56 of the MiG-21 manual also states that the Lock-on/Damp button is used to change the radar to narrow search to attempt a lock and to dampen the reticle, and indicates that to unlock a target, the CANCEL button has to be pressed (e.g. page 157). Page 138 of the game manual confirms that to unlock a target, the CANCEL button is used. However, in the game, beside dampening the reticle, the Lock-on/Damp button is used to lock AND unlock a target. That's a major reason why performing gun and rocket attacks in the game does not work as described on page 64 and pages 168-172 of the MiG-21 manual.

 

23. According to page 158 of the MiG-21 manual, the 300-m fixed range gun mode is enabled by switching to GYRO-MAN and rotating the hand grip all the way backward. Page 146 of the game manual states that to enable 300-m fixed range mode, the correct setting is GYRO-AUTO.

 

24. Various statements on pp. 159-175 of the MiG-21 manual seem to indicate that in the real aircraft, switching on the power to external stations 1 - 2 switches on all rocket pods, also those on stations 3 and 4 (this is not true for bombs and missiles). In the game, the switch to power stations 3 and 4 has to be on in order to launch rockets from these stations. This might explain the discrepancy described in paragraph 13.

 

25. Pages 162-163 of the MiG-21 manual can be read to indicate that when carrying several missiles of one type (SARH/IR), with 1, 2, 3 or 4 selected, one does not necessarily have to manually select the next missile after firing the previous one, but that the system automatically selects the next missile to fire based on a preset logic. This does not work in the game.

 

26. Page 172 of the MiG-21 manual states that a gun stoppage is indicated by the gun failing to fire with the READY light on. Page 129 of the game manual states that the light is off when the gun is jammed. Assuming the real manual is correct, this would be consistent with page 170 of the MiG-21 manual, which states that the green light is illuminated even if a reload button has not been pressed, as described in paragraph 14. above.

Edited May 13, 2015 by Bestandskraft
Paragraph 22 modified

[finger]

Nice report,nice comparison.I will be comment only last paragraph about

gun operation Both manuals are right,but describing operation is

slightly confused.Green light "GUN READY" always mean,that movable

gun part are in their extreme position.Simply -gun is ready for loading,

reloading or firing.When this light is "OFF" gun is dead because of it in

"BETWEEN" position.

[finger]

[finger]

[finger]

[finger]

[Bestandskraft]

27. According to pages 78-80 of the MiG-21 manual, various systems seem to require a warm-up time, neither of which is implemented in the game:

 

Radio: 90 - 120 seconds

SRZO: 2 - 3 minutes

ATC Transponder: 2 - 3 minutes

ARC/RSBN: 3 - 5 minutes

 

28. Page 77 of the game manual states that the NOZZLE OPEN (СОПЛО ОТКРЫТО) light goes out once the engine is started. In the game this does not happen.

 

29. Page 83 of the MiG-21 manual implies that vigorous stick movements cause a temporary main and booster hydraulic pressure drop. In the game, stick movements do not affect hydraulic pressure.

Edited May 11, 2015 by Bestandskraft
Added new paragraphs

[Bestandskraft]

30. Pages 100-106 of the MiG-21 manual imply that it is possible to set the RSBN-ARC switch to ARC while on a PRMG approach in order to have the pointer point to the outer or inner marker for monitoring approach accuracy while still receiving PRMG glide path and azimuth information. In the game this is not possible unless enabling Automatic SAU mode before switching to ARC. In this case, the aircraft remains on the glide path and localizer even though the azimuth and glide path indicators are incorrect.

 

31. Pages 100-102 also seem to imply that the Automatic SAU mode will not intercept a glide slope from below as aggressively as it does in the game. In the manual, the approach is described as the aircraft remaining level even though Automatic mode is already engaged, only intercepting the localizer, while the aircraft starts its descent only when intercepting the glide slope at 12 - 14 km. In the game, as soon as the glide slope is recognized by the aircraft, the aircraft will perform a hard pull-up to intercept the glide slope once engaging Automatic mode. The "by the book" approach of flying 600 m AGL, then enabling Auto mode and waiting for the aircraft to descend therefore does not work.

 

32. I'm not sure if this problem is limited to the MiG-21 module or affects all of DCS World, but the game does not seem to differentiate true altitude and barometric altitude. As an experiment, set the temperature to -50° C and fly level above the sea. When evaluating the flight in TacEdit (or by referencing the radar altimeter), it becomes clear that when flying at a barometric altitude of e.g. 450 m, your true altitude as indicated by the radar altimeter or via TacEdit is also exactly 450 m, even though at -50° C the altitude difference should be 135 m (see e.g. ICAO Doc 8168 Vol 1). While the fact that this is not simulated is not a bug per se, the problem is that the QFE reported by ATC does take non-standard temperatures into account. One can easily verify that the "QNH" you can set in the mission editor is not really QNH, but the actual pressure at sea level. The game then calculates QFE using the standard pressure reduction formula to arrive at the QFE reported by ATC. However, since this formula takes into account temperature, and the game's altimetry modelling does not, the QFE reported is correct only if the temperature is set to 15° C. Since it is probably not easy to introduce a true altitude modelling into the game, it would be nice if ATC did not pretend one was implemented, but always reported QFE assuming ISA.

 

33. Conversely, when setting Dynamic weather, QFE reports seem to be totally off, without any discernible logic (for example, in a random self-made mission with dynamic weather I tried, at 15° C and 180 m field elevation, ATC reports QFE 756.07 mm, to get the altimeter to indicate zero one has to set 729 mm (actual QFE), and to get field elevation one has to set 744 mm (QNH).

Edited June 7, 2015 by Bestandskraft
Old para 32 deleted (solved)

[Toybasher]

34. Page 70 of real mig manual explains the SPO-10 is supposed to flicker a ton and the sounds increase in frequency (Faster? Higher pitched?) when locked on with lights flickering, and only like 3 to 5 KM from enemy fighter radar will all 4 lights turn on.

 

In game, no matter the distance, as soon as you're locked all 4 lights come on, even if it's from a SAM site further away.

[Bestandskraft]

35. Page 44 of the MiG-21 manual implies that it should be possible to receive at least the localizer signal of a PRMG out to 40 km. In the game, reception of both localizer and glide slope starts at 25 km, which is consistent with page 116 of the game manual. Page 44 of the MiG-21 manual further states that Landing mode should be selected at no more than ±10° degrees from the final approach azimuth. Additionally page 100 and 101 imply that the HSI (CCI) localizer channel failure warning flag closes its window (presumably meaning the localizer signal is being received) at 10-12° of azimuth deviation. Assuming the drawing on page 104 of the MiG-21 manual is to scale, the coverage zone displayed there is also approximately ±10°. In the game, according to page 116 of the game manual and verified by in-game behaviour, the localizer is received only within 2° of the centerline.

 

Moreover, Table 11 on page 101 of the MiG-21 manual and page 108 indicate that a proper PRMG glide path is characterised by the altitude in hundreds of meters equaling half the distance to the runway in kilometers. This equates to a 2.86° (thus, approximately 3°) glide path. According to page 116 of the game manual and as easily confirmed by in-game testing, the simulated MiG-21's PRMG glide path is 4°.

 

The manufacturers of the PRMG system (POLYOT) confirm on their web-site that the localizer of at least the most modern version of the PRMG has a minimum range of 45 km and a horizontal coverage zone of ±15°, while the glideslope has an 18 km range as well as a slope angle limit of 2-4°, which might indicate that 3° is the desired average angle. See http://www.polyot.ru/emitent/Eng/PRMG-76UM%20En%20Polet%202012.pdf. The relatively restricted forward visibility in the MiG-21 during landing approach also supports the 3° instead of a 4° glide path theory.

 

36. Page 45 of the MiG-21 manual implies that in Letdown/Proceed mode, the HSI will provide both vertical and horizontal steering information. In the game, only vertical steering is provided; a specific azimuth cannot be selected.

Edited June 20, 2015 by Bestandskraft
Updated 35., merged with 37.

[Jerkzilla]

34. Page 70 of real mig manual explains the SPO-10 is supposed to flicker a ton and the sounds increase in frequency (Faster? Higher pitched?) when locked on with lights flickering, and only like 3 to 5 KM from enemy fighter radar will all 4 lights turn on.

 

In game, no matter the distance, as soon as you're locked all 4 lights come on, even if it's from a SAM site further away.

 

Now that could be really important. Really hope this particular thing gets looked into.

[Toybasher]

Now that could be really important. Really hope this particular thing gets looked into.

 

Agreed. Sorry for the necro, but what I discovered today is a bit concerning.

 

http://www.simhq.com/_air14/air_528a.html

 

In the interview, the old devs supposedly had the correct modeling of the RWR, a fully English cockpit, and (Better?) modeling of ground and cloud clutter, where they appear as actual targets and not simply fuzzy areas on the radar. (I am not sure if this is the correct modeling.)

 

Also the missile locked beam thing couldn't be "Fixated" on a target to fire beam riders like you can in DCS. They also had incendiary bombs. The sorc light also emitted a tone when something went wrong.

 

I am curious leatherneck. What happened? Why did you strip the fully English cockpit? Otherwise the sim is top notch.

[Toybasher]

When locking with radar, the "overlay" disappears. The little thing with the "5, 10, 30" scales on it. I'm not completely sure but I think it's like an actual physical marking on the screen, and shouldn't disappear when you lock. Especially considering the horizontal scales seem to be used for when you get a lock, and the lines are supposed to move along the scales as you get closer.

 

You can only test the SPO-10 when your radar is on. Ingame you can test it even with the radar off.

[Frederf]

Regarding SAU-23ESN and POLYOT-OI:

1. The stabilization AFCS mode selection is independent of AFCS landing modes (command, automatic). It is perfectly possible to approach with PRMG command mode for steering information while using stabilization mode as well.

 

2. A/P Off (Выкл. ал) red button on the stick will disengage all AFCS automatic modes of operation, including either landing mode. The OFF (OTK Л.) button on the AFCS landing panel is for selectively disengaging only the landing mode(s).

 

3. When leveling mode is selected it is required that no more than 1.7-1.9 kgf (17-19N) fore-aft or 1.0-1.2 kgf (10-12N) lateral stick forces be applied by the pilot or the leveling mode light will extinguish and the maneuver will be aborted.

 

4. Danger altitude recovery does not have the restrictions to stick forces mentioned in 3.

 

5. AFCS pitch channel is engaged in leveling or danger alt regardless of right wall AP Pitch switch position.

 

6. AUTO CTL landing mode will maintain constant altitude as existed at the time it was engaged until the glide path beam is crossed. It will not climb to meet the glide path. Because the descent is not begun until the glide path is reached, the pitch command needle will already be below the current pitch. The aircraft may be as much as 4 dots above the glide slope position during this transition.

 

7. The yellow command bars only function in the command or automatic landing modes corresponding to the pitch and roll channel warning flags (FDI) disappearing from view.

 

8. Stabilization mode captures aircraft pitch, bank, and heading values when running when stick forces are relieved and maintains them. When bank is less than 6° heading and pitch are captured and bank is driven to 0°. When bank is higher heading is not captured, pitch is captured, and bank is maintained at current value. Roll or pitch channel stabilization is suspended for that channel when forces in that channel exceed the limits specified in #3. Air aircraft trimmed for level flight at 600 km/h should be able to be accelerated to 900 km/h without touching the pilot stick when engaged in stabilization mode without developing significant pitch and bank changes.

 

9. Pitch maintenance is +-1° when level unaccelerated and +-3° otherwise. Pitch hold limits are +-40°. Roll is not maintained when pitch is within 20° of zenith or nadir.

 

10. The standard PRMG glide slope is 2°40' (2.666...°) and provides a superior landing situation than 4° The localizer signal is available at no less than 45km and glideslope 18km.

 

11. In the landing mode the RSBN equipment is no longer referenced for distance but the PRMG equipment used in stead. The azimuth channel of the RSBN equipment continues to be used. One and a half minutes after the RSBN distance is not updated (landing being selected) the light extinguishes. The azimuth light continues to burn as it is still used for the bearing pointer.

 

12. When stabilization mode pitch channel is active, trim switch does not control elevator trim. Instead it is a pitch selector for the stabilization program to alter the captured pitch value which is being maintained.

Edited October 23, 2015 by Frederf

[slicker55]

This is a very interesting read - thank you.

 

I am hoping someone will know the answer to these questions too.

 

There is a green light labelled 'ARC IBN' just to the left of the SORC.

 

I have yet to see this light come on!

 

What is it for?

 

When does it come on?

 

What is it's correct name?

 

Can this light be 'tested' like all the others?

 

Thanks in advance

[Frederf]

ARK inner beacon. The ARC-10 in this MiG-21 should work in a different way to how it does (I am not sure how exactly).

 

Preparation for flight manual says to "...the radio compass wave remote-control selector is adjusted to the position corresponding to the selected inner beacon button, the button corresponding to the outer beacon of the landing airdrome is depressed, and the radio data of the pretuned homing beacons and broadcasting radio stations are written down on the radio data plate for the APK-10 radio compass;"

 

All pictures of the rotary selector I have seen have been marked 2, 4, 6, 8 and I, II indicating to me that these 8 positions correspond to the pushbuttons on the ARK panel by some logic, perhaps 2I = 1, 2 II = 2, 4 I = 3, 4 II = 4, and so on. I estimate that there are not 9x4x2, 72 possible ARK channels stored but only 9. It makes sense why would an interceptor need so many channels for memory? The rotary knob is the remote selector which only chooses which of the 9 presets is assigned to be the inner NDB. For example if the inner NDB was set as button 5 and the outer NDB is button 2 then you set the ARK-10 as follows: Rotate the remote selector to position 6. I. (5th position) to choose the inner beacon. Push the button 2 to choose the outer beacon. The Roman numeral rotary selector chooses the inner preset and the push-buttons choose the outer preset.

 

The pilot can choose to tune the ARC to either the outer or inner frequency for the channel by the switch to the left of the light or automatically by passing the outer beacon. When the OUTER-INNER switch in the OUTER position the outer frequency will be tuned until automatic selection of the inner frequency if the station is passed. In the INNER position the inner frequency is tuned.

 

The light should "flash up" when the inner beacon is tuned but the switch is in the OUTER position (indicating automatic change). For automatic changeover to occur the following is required:

 

УАП-1 switch (I think this is the inner-outer switch?)

Landing gear extended

МРП-56П marker beacon receives the outer marker signal

 

This prevents the changeover from happening in normal non-landing ARC navigation.

 

You will not see the automatic change from outer to inner in MiG-21 (yet?) because Leatherneck Simulations has not coded the concept of outer and inner beacons. Every ARK station is defined by lat/long and frequency as only a single frequency and very few of those as stations belonging to a landing system (just Sukumi and Guadata) anyway and none of those being both of the beacons.

 

There is also the complication that the 2NDB system consists of 4 stations only two of which are on at one time since they duplicate frequencies. Since all radio navaids are defined within the airplane and not as external facilities which may be on or off there is ambiguity which station the needle should point to.

Edited February 24, 2016 by Frederf

[slicker55]

WOW...

 

Thanks for going into such detail - it is all very complicated - I'll try to set the plane up as per your advice and see if I can get the light to come on.

 

From what I've read so far, I thought the rotary selector enabled you to dial in the correct reference number for a given sector as shown in the kneeboard map followed by pressing the appropriate push button appertaining to the desired station.

 

Thanks again - appreciated.

[Frederf]

I didn't know any of this when I started looking closer at it (so thanks for the Q) and I'm not sure how right I am but it seems as close to the truth as I can get with the manuals and pictures I have.

 

In any case, the DCS one works currently the way you think where the rotary selects the zones and that determines region and each set of 9 pushbuttons is different in each of the region for a bajillion presets in total. You set the dial, push a button and that's the one of the 72 presets (although only a couple dozen are actually defined, just one in the case of NTTR terrain). You can check out the definitions (Notepad.exe) in: \DCS\Mods\aircraft\MIG-21BIS\Cockpit\Systems\

 

R_NAV_data - OLD.lua

R_NAV_data_Caucasus.lua

R_NAV_data_Nevada.lua

 

I'm more trying to explain how the real plane works differently. You won't get the inner beacon automatic tuning light ever until such a time when/if the system gets overhauled.

[slicker55]

HI Frederf,

 

Thanks again - that's thrashed that out!

 

Finally, just to confirm... you're saying the green inner beacon automatic tuner light (as per my OP) never comes on in the game?

 

 

Edited February 25, 2016 by slicker55

[Tarres]

All the navigation system in the LN-21 is far from be accurate to the real one.

 

https://leatherneck-sim.mantishub.com/m/issue_page.php?id=61

 

It's a common "RSBNPRMGNDBILSTACANVORVORTACAN..." in a single file. This approach allow them to use the same system for any kind of projects (modern, old, western, Soviet...)

 

Maybe for the next Viggen project we could have a proper nav system and not this kind of "same approach for all kind of navigation aids".

 

Frederf, yes in that post I changed the inner and outer beacons by mistake.

[Teo]

IIRC, when they developed this system there was no "native" RSBN/PRMG stations on the map, and this was probably the simplest (only?) solution available. ED added those navaids to support the L-39 module, so they are quite new to the map.

 

It will probably be same with Viggen's TILS system, as no such stations exists in Russia/Georgia/Navada/Hormuz.

 

It' would be nice to have those navaids placeable as objects in the ME though, and maybe, as user option to use those "hardcoded" stations defined in the module instead.

[Tarres]

Teo, the rsbn system is in the map and coded in the LUAS from the Blackshark 1 onwards alongside with the VOR, TACAN, ILS and so on...

[Teo]

Teo, the rsbn system is in the map and coded in the LUAS from the Blackshark 1 onwards alongside with the VOR, TACAN, ILS and so on...

 

Ok, good to know. So LN probably did it "their" way to overcome the limitation of the few RSBN stations on the map then, and make stations available in Georgia as well.