Tarres

Same in the Viper. Always shows "DTC Default"

Same here, 10GB...

1.3 MB/s of 100MB/s. At least in the "MB/s zone" again.

Thanks- I will try later. I only fly as a WSO or for testing I always deactivate Jester. I never have used Jester from day 1. You are correct. The "left hand modes" of the selector mode not use any input from the WRCS. Only timers and angles. WRCS are only for the USAF models from the D onwards.

@pierscockey I’m interested in the TL mode, what mode do you use as stopgap?

From 96MB/s down to 27MB/s here and now 0.0

38gb here with Kola (8.5gb downloaded, 38gb final after installation)

@NineLine I was to open a new one, but I ´ve found this. In the 2.9.15.9408 I´m unable to make the SS-1 launcher to resume their route. Same with others MLRS. But If I set the number of rounds less than the maximum (11 instead of 12 for example in a BM-30), the launcher resumes their route. Attached 2 tracks: 1st.- BM-27 launches 12 of 14 rockets. Route resumed. 2nd. BM-27 launches all 16 rockets, Vehicle remains idle.MLRS test 16.trkMLRS test 14.trk SS-1 always remains idle: 1 rocket only so no route resumed. mlrs test 16.miz

@gulredrel there is no problem. The nav system in the 21 is purely fictional and completely independent from DCS core. It is a leftover from Lomac 1.0. The 21 was designed as a stand-alone product.

Yes. It’s 800Mhz. Sorry. RSBN it’s like a TACAN station so you need a frequency and a channel. Thanks again for your test. I suspect that this file has been rushed into the “public version” due to the “eastern navaids affaire” because there are some errors in all the systems: ILS coded like VOR, duplicate beacons in the same airport definition, beacons without definition or frequencies…

Yes, it’s a M3 issue. Not Ugra o ED issue. M3 must create their own code.

In a exchange for the TACAN/ILS in the GDR There was a comic in Spain about a couple of spies… Mortadelo y Filemón. In German: Clever & Smart.

As you can see it’s fairly straightforward. Yes, there are some strange definitions in the file. Can you try to change the ils definition for damgarten for a PRMG? Frequency range in the 900Mhz I think. Like the RSBN but with the PRMG loc/glide definitions. Thanks! And maybe we must leave more frequency separation between stations… RSBN uses a 800-1000 mhz range.

I could place the names but it’s difficult to do it without having the map. In a new version, I’ve deleted ILS and tacan placed in GDR airfields. Maybe tweaking the ils definition with prmg definition and adjusting a couple of datafields in the definition may give us prmg. Ok: Wadajom is the radio callsing for Allstedt

Thanks!

@gulredrel. Here is the file. It´s a very quick test done in 15 minutes so it´s like a version 0.0001 Try Damgarten in the L-39. In the ME, the beacon list it´s updated. I haven´t got the map so I can´t test the file on my own or make new versions very quickly. beacons.lua NOTE: IT¨S NOT IC COMPILANT OBVIOUSLY.

Same as other nav problems, bad data coded in the beacons.lua

Yes. They created a file for each map. Rsbn and ark operation in the 21 is a leftover from lomac 1.0 waypoints

The 21 uses rsbn that only works with the 21, same with the ndb. IRL only 9 presets with outer/inner selection via sector/number are available. Something like Yak-52’s ark-15 and the future 29 FF. The file affected for the 21 is in the 21 directory and doesn’t use the standard beacons.lua that is coded as a definition in every map.

With the moded file I’ve tested rsbn and prmg are fully functional in the 39 and in the FC3 (prmg). For the 21, until M3 makes a v2.0 to get ride of all the old code and use the standard DCs core navigation, it’s up to M3 to create the file for the 21.

Tomorrow I will post the file with the changes if you are interested. It’s a very quick test, so there is a lot of room for improvements. I don’t have the map so I can’t test all the changes. Basically I use 8xx frequencies with the xx being the same number that I put in the channel defition. With the real rsbn list that @ESAc_flankercobra posted I code first the channel and with that number I put the frequency. Sorry for my english.

The 21 doesn’t use the standard dcs core navigation. It needs a proprietary file. It was never intended to be a part of dcs world. I’ve changed and adjust the beacons.lua file and works perfect with the L-39, for now the only airframe that uses the Rsbn/Prmg in the dcs core system. The code is available from 2005, before DCs world.

It’s easy to solve the problem for Ugra. I solved it in 15 minutes and without their tools, but only to see if it was possible to solve. Remember that only the modules that use the RSBN/PRMG coded using the DCS Core Navaids (L39 and PRMG for the FC3 Soviet airplanes)are affected.

Tested a modified beacons.lua with @ESAc_flankercobra with the L39 and a perfect IFR flight with functional RSBN stations from the DCS Core.

Second one, (70_6) lacks frequency in its definition. For a 88 tacan, 1131MHZ must be used in the frequency, but doing this will trigger an error due to a duplicate system in the same area.