Tarres

For the Mi-8MTV2 I have used the Devrim Cockpit and the description.lua from the Chinese Cockpit. Works perfect. Thanks!

One more thing, the F-5E-1 is not the manual for the block -1. Dash 1 (-1) is the standard designation of the USAF for flight manuals. So: T.O. 1F-5E-1-1 is the flight manual for the F-5E, revision 1 from August 1978. If BST is modelling the block 3 (or E-3) and it has a RWR, the manuals -1 and -34 will be revisions from the 80´s. But these dash 1 and dash 34 will give us an accurate idea about the plane, except the RWR thing. USAF upgrades in the 80´s were about safety, radios, -159 with more modern gunsight and the RWR but nothing else. Another different thing are the export models, every country selects a different configuration regarding radios, Nav systems, the "Maverick mode" for the CRT, fuel probe... Regards.

Dash 34 is the standard name for the USAF manuals regarding the Non Nuclear weapons delivery. T.O. 1F-5E-34-1-1 F-5E/F Tiger II Aircrew Nonnuclear Weapons Delivery Manual So this is the weapons delivery manual (dash 34 or -34) of the F-5E block 1, first revision, date: march 1980. Regards

Bug remain in 1.5.1 I hope that for 2.0/NTTR will be corrected, to have a proper Nav System in Nevada. Regards.

Yes, works like FlankerOne says. You need a description.lua file along with the files of the cockpit. The path for the "custom cockpit" is dcsopenbeta/mods/(the plane)/liveries/cockpit. You can see how it works in the L-39C, MiG-15bis or the Mi-8 for example.

Same here.

The "both" selector doesn´t work in the A-10C but is a bug in the module not in the DCS-SR. This weekend we will test it.

No problem here with a IA unit using Guard frequency and an A-10C. When UHF set to guard, you can hear the signal. UHF set to preset or Manual, Guard goes off. There is a bug with the UHF selector in "both" for the A-10C I think but not related with the DCS-SR And in 1.5 there is a reported bug about the custom frequencies. Only the server can hear the custom frequencies.

You can use RSBN-5S in manual mode. http://forums.eagle.ru/showpost.php?p=2518544&postcount=9 Regards.

Until BST tell us what F-5E type they are doing, it's better to stay relaxed and wait. The E-1 were upgraded in the begining of the 80's to something like the export F-5's with the -159 radar, RWR and improved radios and ejection seats but they lacked the "Maverick mode" of the CRT and another things The USAF wanted them as an "Agressor" so all other things were not important. So I think it´s better to wait until BST presents the features of the F-5E "sub-variant" that they are making. Regards

Yes. Over the pilot´s seat.

Quick update. 220FM not working. In my test, if I use both AM and FM frequencies in the same mission, it seems to result in the R-863 not working. Maybe a bug with the R-863 FM frequencies?

Sorry. Yes 1.5 But there are a pair of switches in the R-863 labeled as "N/F" regarding the Guard frequencies and the ARC mode of the R-863. For example I can´t hear a transmission in the Emergency Frequency (121.5VHF or 243UHF) with the switch in the "guard position". It works in the KA-50 perfect. Maybe a member of the BST team or a Moderator can post a quick update about these "N/F"switches.

No problem with R-863 at 220Mhz AM here in manual mode.

Hi Lino. Mi-8 uses NDB/ADF navigation with an ARK-9 system. Same navigation system as the F-86, MiG-15, Albatros, Huey and KA-50 (ARK-22 with presets only) Regards

From the English draft manual, pg. 92. Are the following items implemented? .- "АП" (EMERG) green lamp indicates presence of an active signal on the emergency receiver (regardless of the position of the "АП" (EMERG RCVR) switch), .-"АП" (EMERG RCVR) switch allows the pilot to monitor signals from the emerency receiver when set to the ON (up) position, and, "РК" (RK) switch enables monitoring of radio transmission regardless of the position of the rotary selector on the SPU-7 control panel. (I assume that this allows you to hear R-863 and R-828, for example, at the same time and talking on the radio selected according to the position of the SPU-7) Thanks in advance.

Correct. My mistake.

Great work as always Lino. For a 1.1 revsion maybe you can put the RSBN and PRMG channels along the frequencies, and add 430 as an inner beacon for Batumi and 1000 for Gelendzhik. If you want I can send you the morse codes for the beacons. I´ve a jpg for my kneeboard for Huey, Hip and Albatros navigation. Thanks!

Yes 04 sorry

The 21 uses a propietary file, and you can put a beacon (RSBNPRMG or ARC) wherever you want in the map. Fotr the 21, I use a moded file with the same beacons (morse codes and frequencies for the RSBN-PRMG) that are the same that are in the beacons.lua master file. Remenber that ED and BST modelues are the only ones that use this "master file". LNS, VEAO (I don´t known about Aviodev) uses their own files. Regards.

AWACS, JTAC, Cargo and Embarking options are coded in the LUA of the respective modules. For now, AWACS and JTAC options are not available for Helos. You can set the frequencies but you can´t be able to establish contact with the AWACS or JTAC. Regards.

Tested. Works perfect. Thanks!

Thanks, I hope it will be fixed too. Maybe it´s related to this: http://forums.eagle.ru/showthread.php?t=150467

Hello AlaskanGrizzly. In the 1.5u3, I´ve got a: "Dicktkey_DescriptionText_1" in the Mission Briefing and Task Briefing pages. Other pages work as intended. No problems in the 1.2.16. Thanks for your app!

As Gospadin said, it´s the use of the ED´s core navigation system. Even the Hawk (I don´t know about the C-101) uses an "own system" and it´s a western plane. All systems (NDB for ADF/ARK, ILS, VOR, TACAN, PAR, RSBN, PRMG...) are available in the beacons.lua and beacondata.lua with associated models and everything you need since Blackshark 1.0. It´s in the hands of the developer to use it or make their own system. For now only ED and BST use this system, I don´t know why. But I think Zeus (or the developers team) has given good answers for this Q&A. Thanks!