Tarres

SAM SA-10 S-300PS LN 5P85D must depend on a SAM SA-10 S-300PS LN 5P85C to be able to fire. The 5P885D lacks the equipment bay present in the 5P85C. Corercted LUA in attached file. Unfortunately I donñt know how to implement the ratio 1:4 for the 85C/D. 5P85D S-300PS LN.lua

I´ve doing some tests. The behaviour seems to depend from the loadouts, the weather and the spawn point (in flight/on runway) The SAU PRMG AUTO mode seems affected too.

After 11/06/20 patch, engaging SAU recovery, establish a constant -5/-10 m/s descent rate. It seems that the plane stabilize at 0º, not a 0 m/sg with the desired AoA. Edit: Work perfect IF no wind or turbulence is present in the mission.

Yes. Correct. Maybe I am too old, but I will prefer a 80’s model. Thanks to both.

Yes, this is that I think. About the "wingspan" in gun without lock, is the selector on the top of the WCS? And it´s funny that that we have the 9-13 FM, cockpit and radar... and we don´t have a izd.9-13. But the most important thing is to have a "manual next WP" from my point of view.

One question. I think that the "radar scale" is tied to the radar mode selected. If this is correct, and assuming that FC3 are "easy to use", wouldn´t be better to have fixed range, and less controls to assign? I think that the fixed values are, in km: 150 for encounter 100 for auto/TWS 50 for pursuit 25 for STT 10 for CC modes 5 for AA Gun

Luwa Airbase. Defined as RSBN instead of TACAN/DME (military base) Lack frequency and ID

SSpain 462th Escuadron C.15-79 must be Spain 462th Escuadron C.15-79 Attached corrected LUA description.lua

4. Of course nav panel/number. Nothing brakes immersion like having to go to F10 map or such. Regarding number 4, even better if the "Auto next WP" could be disabled or at least an option to setup as "auto/manual"·

MLRS vehicles don´t resume route UNITL last round reach their objective. Example attached: 1 SCUD 1 BM-21 1 BM-27 1 BM-30 Not resuming navigation UNTIL their rounds landing/ecplode. MUST resume navigation AFTER last round fired. Obviously with the necesary time for return to transport mode. MLRS test.miz

Track attached. Thanks Norm. RLK41.trk

Seems solved in OB 03/06/2020

Lights too dim seems a general issue in this update.

IA helos like KA-27 and SH-60 make landings throught the ship until (O,0,0) position of the model, in both, old models (Peter Veilky) and new ones (Burke IIA)

In order to use the search function in the ABRIS, these fields must be filled. A possible working file is attached. Beacons.lua

Corrected frequencies in attached file Beacons.lua

Bug still appears. Selector "click position", "visual position" and "value position" don´t match. Example: Selector: value "3", "click point": "8", real value for RKL navigation "5"

Tested with Iran as launcher and Rusia (A-50) Awacs. Target engaged OTH. @Deadpool, the missile is launched without having a radar contact by the silkworm radar. So you have only signal that an AWACS is in the zone and spike from the Styx radar when engaged. It colud be better with the recon label, but for now only works with the AWACS label. I´ve modded the TU-142 to make use of the surface search radar (and not the AS/SS of the A-50) as an awacs, Due to elevaiton limits, airplanes are not detected... well sort of..

I´ve been making some tests. In order to fire an ASM, for example a salvo of 6 P-500 from the Moskva cruiser OTH, we need a OTH radar. First I tried with the most logical plane; TU-142 as a recon. No joy. The enemy ships are displayed in the F10 map and the ASM can only be launched IF the player shoot manually, using the assign target. BUT, using an AWACS (A-50), ships are located AND the Moskva launches the P-500. Tweaking the TU-142 LUA and adding the value AWACS, and doing the same test, the 142 detect and transmit the data and the ships engage OTH. Maybe ED could tweak the RECON tag to achieve the same results as the AWACS tag. Mainly because the radar of the 142 is coded as SurfaceSearch in the dbsensors. With this adjust to the tag "RECON", we wiil be able to use SH60 or KA-27 as radar picket helos.... well the KA-27 mujst be redone, because it lacks any radar. And yes, the P-500 engage at 400km, the KH-41 at 200km and P-700 at 400km.

Some controls doesn´t work as intented, mainly toggle switchs. E.g. Start Cover open/close or carbutator heat/cold. Undercarriage lock isn´t defined like in the MiG-15. UC order automatically open or close the lock. UC lock is defined in LUA and in EDM. ARK-15M: in Kompass mode unable to hear the morse code. In ANT with RK on or off works as intented, you can herar or not depending on the selector. "Squelch" not working (always on) Thanks in advance.

NDB´s in LUA are in HZ instead of MHZ. It can be solved easily, for example: Line 649 frequency = 310000000.000000; must be frequency = 310000.000000; Can I send to the team the corrected LUA?

In ...DCS World OpenBeta\Mods\terrains\Caucasus\Radio.lua must be changed to 125.5 MHz(line 29) in order to adjust wrong airfield frequency outside the VHF AM range.

Minor adjusts: SA-10: 1 more type D launcher per type C launcher (1:3), 1 more firing section for a total of 12 launchers, 3 Type C and 9 type D SA-6: Gaz type instead of the more modern trucks.(URAL) SA-2/3: PBU and KUNG instead of mobile ATC (SKP-11) BUG: s-300ps 5p85d ln, line 37: must depend on s-300ps 5p85C ln. GT.WS[ws].LN[1].depends_on_unit = {{{"s-300ps 5p85C ln"},},}; Type D launcher unable to shoot if no type C is oresent as per desgin. Thanks in advance.

In Flight IIA, only 1 CIWS is installed. The bow position is ready, but not fitted with a MK15. (as per 2019).

Yes, SM-6 ERAM in ASuW mode. Unfortunately not in DCS for now. But ASuW are poorly designed in DCS, even a small cargo ship can be damaged by 2 P-700 or P-500 (bigger than a Harpoon) and doesn´t sunk. It´s related to the LUA definitions of warheads and the "hits points" of the ship. Basically a 1: 2 ratio betweren ship hit points and ship tonnage.