Tarres

These statiosn are fixed so wings must be at minimun sweep from take-off to landing. Only use was for ferry flights.

Thanks Frederf. This is what I understand too.

I´m strating to think that part of the problem with the ASP is related to the "Realistic option" in the tab specials on the main menu. If they deactivate, or better erase this option, the code can be more straightforward and the workflow of the swtiches combinations easier to adjust. On a side note, in beam mode can the radar be locked on a target IRL? It seems strange.

All these things are leftovers from the 21 Mod for Lomac. Asp, ARK, MRP-56, slant range...haven’t been developed for ages. I think that this part of the code (avionics) has never been developed from their initial status.

The "navigation code" is a leftover from the "LOMAC 21 MOD". Even it has the old "beacons" from Crimean map. From KA-50 onwards, different types of beacons from NDB to ILS and RSBN are available in the base code. You can see the code in the respective LUA. People must remember that this code has not been updated and the first idea was the 21bis designed as a "standalone" (many years ago). You can see this in the warehouses in the ME, there are some weapons from LOMAC e.g. the old BETAB with their old names.

The main problen and the foundations of all these problems, is that the base code for the non-graphic part, was made for the LOMAC 21bis MOD. After some years of troublesome life cycle, this base code hasn´t been redone. So I think that every patch is a new layer of solved-unsolved problems. I seriously doubt that before M3 release and make profit with a new module(s), the 21 will be updated seriously, rewriting the base code as a new foundation to mantein the module within the DCS ecosystem.

Any chance to have RSBN-4 with associated PRMG station in the main miitary Syrian AB?

Abu Musa has the definition for their DME and NDB merged: DME with NDB freq. Must be 2 separate entries, something like: display_name = _('Abumusa'); beaconId = 'airfield1_0'; type = BEACON_TYPE_DME; callsign = 'ABM'; frequency = 115400000.000000; channel = 101; position = { -31252.106776, 5.425148, -122338.729886 }; direction = 174.107027; positionGeo = { latitude = 25.878140, longitude = 55.022870 }; sceneObjects = {'t:436600879'}; }; { display_name = _('ABU MUSA NDB'); beaconId = 'airfield11_0'; type = BEACON_TYPE_AIRPORT_HOMER; callsign = 'ABM'; frequency = 280.000000; Data from Skyvector.

The "problem" is that the NDB frequencies in DCS are from late 90-early 00. So , the far-near not match exactly with the math equation that the ARK-5: uses (Far*2)+20. One solution maybe is "to adjust the Near frequency" of the AB only to match the maths that work in the ARK-5 in the db. The ARK-10 was one of the first (the first I think) with presets and with the particularity that "NEAR" only worked with the 2-4-6-8 presets, 1-3-5-7-9 were used for navigation only. The Selector defined two zones I/II to selct if the Near was below (I) ot above (II) the preset, to avoid possible problems with the 3 independent selectors.

Currently the ARK-5 works as the real one. Basically you turn the frequnecy for the "FAR". This is the "main NDB" for navigation purpouses. To make an NDB apoproach, you dial the "FAR" frequency and the NEAR is set automaticaly when yopu select the appropiate "Sub-Sector". The 150-1060 general frequency range is divided in 3 "Sub-Sectors": 1. 150 - 310 kHz 2. 310 - 640 kHz 3. 640 - 1300 kHz. For exemple, if you turn the ARK-5 to 150, for the "NEAR", if you select the Sub-Sector II: you get the 310khz freq, if you select the Sub-Sector III you get the 640 freq. In this example, 150 is in the 1st Sub-Sector, so you can´t get the 1st sub-sector freq. for the 150-310 FAR freq. So for an airodrome with 150-310 (outer-Inner) beacons, you dial 150 in the ARK-5 and select the Sub-sector II. Note: if you select more than 1 Sub-Sector, the ARK-5 will broke, because the antenna will try to find 2 freq at the same time.

Yes. I was referring to "mixed IR loadouts" as stated in RL manuals. And sorry for my english.

For mixed loadouts, e.g 2xR13M1 and 2xR60 in inner (R13,1-2) and outer (R60 1-2). Selector in Neutral: you choose the type of missile to launch. Position 1, order: R13M1-R13M1-R60-R60 Position 3, order: R60-R60-R13M1-R13M1

Thanks to Hiromachi, I did some more tests and work perfect. The "problem" is that the pylon numbers in the ME aren´t the same for the WCS. In the ME:1-2-(3 central)-4-5 For the WCS: 3-1-2-4

Correct. R-55 only for inner pylons IRL. Used as training rounds in the bis IRL.

Yes, in neutral you choose the sequence, but now the second prioriry (the firing sequence) it´s broken. For example you can select a sequence of IR/SARH/IR SARH in order to fire an IR and a SARH at the same target (as per USSR doctrine) A lot of things are broken now. I´m testing and the ASP and the weapons selector according to RL manuals and what we have now (the manual it´s outdated, also the training missions).

Yes, 1st priority: IR/Neutral/SARH. If set to neutral, you select the fisrt pylon in the sequence. Only the salvo positions can be used with the 1st priority. Edit the previous post to clarify.

Long modifier is for the "West Longuitude", west of Greenwich 0º Meridian. Data are enetered in decimal, in the Options TAB I think that you can choose this coordinate format. Otherwise you must convert º/'/' to decimal.

1.- Yes 2.- AA priority is selected by the IR/Neutral/SARH selector. Only if the selector is in the Neutral position the priority is established rotating the pylon selector AND ONLY to select the first pylon for the sequence. The training missions must be updated to reflect this.

Thanks for the quick answer. I suppose that for now I can deal with the hybrid 64N6/36N6. Thanks for your time Czich. As a side note, the same is aplicable to the 2 EWR Systems with their way off max range.

About the 64N6 radar. In the sim, as a leftover from LOMAC/FC, we´ve got the S300PS system with 5V55 missile, 5P58C and D launchers, 5N66M and 30N6 on mast and 54K6CP. But the LR search radar, the 64N6 uses the data of the 36N6 (OTAN: Tin Shield) in the dbsensors and 64n6 definitions LUA data. So the data and ranges are accurate. To sum up, we´ve got a 64N6 3D model with 64N6 description in the Encyclopedia but with the radar data of the 36N6 mounted in a mast type 40NB6M (correct). I suppose that these old models will be replaced in due time, so maybe it will be possible to have a proper 36N6 model to couple with mid 80´s S300 type that we´ve got. Note: not sure if a bug or intended as no 3D model for the 36N6 are available.

Doing some test with the manufacturer value (320km) in last OB: Caucasus Map, northen flat part. No mountain ranges. C-17@cruise level: detected at 300km. F-15E at low level: derected at 120-100km. F-117 at low level: detected at 20-15km With the normal values C17 and F-15E both detected at the same time at the same distance. Around 110km.

Solved deleting diff.lua in savegames

When in cockpit, no input from keyboard avalilable, Must kill DCS.exe to exit. Steps: Launch DCS, start any mission with 29A, NOTE ONLY 29A is affected on my end. Unable to send any input from the keyboard. Eve escape to quit mission. Edit: SOLVED. Seems like corrupted lua file in savegames. Please close it.

Making a quick test, the preparations to resume path, start 90 seconds AFTER the last round hits the target. (BM27/21/30 and MLRS) Tomorrow I´ll post a track. P.d. SPH not tested yet.

Thanks! I test it later with a fresh new mission. So move to WP 1, launch x number of rounds, wait 90 seconds, make preparations and resume route. SS-1C is considered a SRBM instead of MLRS, same rules with its corresponding time I suppose.