Tarres

Any chance to have a "mirrors installed" option in the ME in addition of an "on/off" switch?

I wonder if in the medium or long term, ED could add a tab for radio presets in the Mission Editor for the 3 radios of the A-10C like in the other modules. I know that the A-10C has the ability to set this presets when you are in the cockpit or in the "prepare mission" but I think that it could be a useful thing . It´s the only module that doesn´t have this feature. And in the long term, for the A-10C and Ka-50, add connectors to the clickabledata.lua to the HOTAS switches and buttons to be able to export the data of the switches like in the other modules (L-39, P/TF-51, Sabre...) Thanks in advance.

Yes. It´s more a "workaround". As you say the bug is still present for some configurations.

Yesterday tested with no problems with this settings: Tactical commander red, forced no external views and forced only map for clients. The Tactical commander works perfectly with Fog of War, with detections ranges according to flight altitudes and LoS.

Manuals about the MiG-21bis are in Avialogs (English) and in the Polish Air Museum: http://www.muzeumlotnictwa.pl/index.php/digitalizacja/katalog/2309 and http://www.muzeumlotnictwa.pl/index.php/digitalizacja/katalog/2308 The scan limits are +20º/0º in elevation (fixed) and +-30º in azimuth. The only movements of the antena are the "Low Altitude" mode that sets the antenna in a +1.5º angle upwards to avoid clutter on altitudes below 2000 meters and the "fixed beam" that set the radar in 0º azimuth and -1.5º in elevation. The "up and down marks" according to the manuals, only are representatives of the "relative altitude with the 21" of a contact if the 21 is flying with a pitch of less than 8º. Page 56 of the Pilot´s manual in Avialogs.

Or a proper NDB navigation with the "expanded beacons" of Gospadin. Or a proper RSBN with "manual mode" like the L-39

Same here. But not always reappear.

The -1.7º it´s for the "beam mode", fixed in azimuth and -1.7º in elevation. According to various manuals, the RP-22 antenna is fixed, not stabilized to the horizon. Standard operation manual indicates that the intercept course must be 1000-1500 meters below the target altitude, due to the scan cone of 0º to 17.5º. Of course I could be wrong.

The RP-22 scans in the following elevation patterns: 0º to +17º: standard pattern +1.5º to +17º: low altitude mode

Sith, in the medium term, could it be posible to make the default letter size a bit bigger? Maybe the GUI aswell, it seems a "bit tiny" with certain resolutions. At 1920 resolutions and above it´s a bit difficult to read the text. Thanks.

ED has the RSBN and PRMG systems implemented in the LUA scripts from BS1 onwards, alongside with the VOR, PAR, ILSN, NDB, TACAN...

In addition you can use the manual mode of the RSBN system. In the NTTR, without RSBN stations, with the use of the manual mode you can fly and navigate with a reasonable error margin.

It's a bug. The preset frequencies in the rear seat are the old presets when the L-39 didn't have the UHF scale in the R-832M radio set. And the frequencies are not updated alongside the front seat in the ME. Maybe related with the introduction of the UHF frequencies in the R-832M radio set in a recent patch.

This is an example of a short flight in the Albatros using the RSBN, the NDB and the PRMG systems. http://forums.eagle.ru/showpost.php?p=2518544&postcount=9 Maybe can be of help. Unfortunately, the 21 not depicts the nav system as IRL so even both airplanes shares the same systems, setups and modes of operations are not the same.

Skull, remember that Maykop only has PRMG in one direction of the RWY, from southwest to northeast. If the active RWY is the NE-SW, you don't have PRMG indications, it's like Krasnodar Center.

Frederf, to complete your perfect explanation only one thing, according to the Technical manual of 1982, there is no possibility of "asymmetrical loadouts", both inner or both outer pylons must be loaded with the same type of missiles or rocket pods or bombs. Example: Pylons 1-2: 2xR3S or 2xR13M, or 2xR3R, or 2xFAB100. NO R-3R in pylon 1 AND R-3S in pylon 2 allowed for example. Table here: http://www.muzeumlotnictwa.pl/index.php/digitalizacja/katalog/2309 Pages 155-156, with the corresponding settings of the selector knob and IR-Neutral-SARH switch. This manual covers the weapons employed and all the parameters regarding the weapon system I think. Regards!.

The ASP model that we have in the L-39 is accurate in the AA according to references manuals for non-maneuverable targets or targets maneuvering at a maximun of +2G. The Fixed mode must be used for attack a target maneuvering at +2G. Set the estimated wingspan and adjust the distance with the "distance selector" in the throttle. For a given wingspan, move the "distance selector", to the point that the inner points of the "diamond ring" touches the target. It´s like a classic Gyrosight. The ASP-PD model of the real 21bis, according to technical suplements and flight operations manuals, has the same limitations and for a dogfight, the technical manuals state that the Fixed position must be used alongside with the fixed grid, making the correspondent calculations in radii for the distance, wingspan and angles. Sorry for my english.

Frederf, the 21bis uses a "command console" a bit different but I think that the ARK-10 works in this way (based on the Flight manual and the equipment manual): 9 "presets": the pushbuttons. For the airdrome markers, they store the "OUTER" beacons, or NDB stations. 8 "bands" for the "Inner markers": I. 120-280 kHz II 280-440 kHz III 420-580 kHz IV 580-740 kHz V 720-880 kHz VI 880-1040 kHz VII 1020-1180 kHz VIII 1180-1340 kHz With a outer beacon selected, pushbutton depressed, set the "rotary" to the proper band. The Outer/inner control switches from one to another. Imagine that we have a proper ARK-10 system, modeled: Example: Anapa 215/443 in the ME, we set the 443 into a "presets box" (like the ark-22 of the KA-50), channel 1 In flight, we push the "1" button and the rotary in the "I" position (215 is the inner beacon frequency, so "I" is the correct subrange) With the inner/outer selector we can change between them. NDB beacons, like Dzhugba for example, are set in the "presets box" of the ARK-10 in the ME, in this case the "rotary" is not necessary. Example: in a "presets box" we set "420" in the "2" and in flight we push the "2" button and we have indication to the Dzhugba NDB. Sorry for my english.

Technical manual about the ARK-10 and other radio equipment of the MiG-21bis (in polish) http://www.muzeumlotnictwa.pl/index.php/digitalizacja/katalog/2310 It includes the R-802V radio, MRP-56, ARK-10, SPU-9 and the non modeled SOD-57 and others. Thanks to some1 for the link.

2.0.1u1 and 1.5.3 are now the same I think, except the terrain of course. EDIT: The Mirage differences... Yes Neil, I forgot it. Thanks!

Totally agree with Phantom, And I think that could be better if we could have the option in the Mission Editor, alongside the hood and solo options.

It is not related with the autopilot. https://leatherneck-sim.mantishub.com/view.php?id=93 It´s related with the Weapons System. The "lock button" is also a "damper" button for the ASP in Gyro mode, like in the F-86 for example. So the "unlock feature" was the bug, these bug prevented the use of the "damper". Whit the corrected ASP in the 1.5.4 patch and following patches, this feature is necessary to have a proper ASP sight.

The limitations could be overcome with the "manual mode of the RSBN" and the NDB system IRL is in not way related with the RSBN or the PRMG systems. Systems that are differents. I have no problems flying in Nevada or Georgia with the 39 with the RSBN in manual mode and the RKL-41 system. The 21 had limitations IRL and I think that the way to enjoy a simulation is to known its weakness. Maybe I'm too old.

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...

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.