Tarres

The mission gets stuck at the point regarding the "Set the Gun Sight Base at 35 feet". Setting to 35 feet as indicated but the trigger doesn´t work.

Spitfire support. LUA Beta file for the Spitfire. -Removed Guard frequencies for the R-863 radio of the Mi-8MTV2 according to the new manual. -Support for the Spitfire ARI 1063. DCS-SimpleRadioStandalone.lua

Minimal typo error. The radio is labeled as a "SRC522" in the ME instead of "A.R.I. 1063" File affected: coremods\wwIIunits\spitfireLFMkIX\SpitfireLFmkIX.lua, section panel radio, line 205: name "src 522" must be: name = _("A.R.I. 1063"),

The pylons are coded in the LUAs but commented. So I think it will be "activated" in the near future alongside the proper munitions and drop tanks.

Yes, the R-73 was retrofitted to the MLA but without the HMD.

Rockets and gravity bombs. Kh-23 AGM radio controlled , like the agm-12 bullpup or the rb-05 with command pod in the port fuselage station. Chaff/flares dispensers: 2 KDS-23. The MLA is the upgrade of the ML for VVS with the avionic improvements that the 23P of the PVO has. Sniped!

I´ve added the old Batumi and Sukhumi RSBN stations, removed in 1991, and they work. But adding a RSBN station in an airport with other NAVAIDS like a TACAN or a VOR seems to not work from 1.5.4 onwards (old Sochi, Tblisi and Kobuleti RSBN)

The functions regarding the "embark/disembark" have been removed from the database scripts, only remains the "All descent" function for the Player. The AI is unable to embark/disembark due to the lack of this functions.

Yes, the co-pilot MIC switch overrides all radios, but , I think that it only must override the co-pilot SPU-7, but for now both SPU-7 selectors are sync.

Bug in beta and release 1.5.5 (021216) The proposed momentary solution for the LUA works as intended, quantities of chaff and flares are fixed in the ME. The "-2 flares in the Spirale suite" persists.

The ARK-22 frequencies are programmed in the Mission Editor alongside the R-828 frequencies in the radio tab. There are some problems with some beacons due to some the definitions used by the beacons.lua and the internal function of the ARK.

Solved: in the quick start mission of the KA-50, Nellis is set as "RED".

Update: maybe only are affected the "H-#" spots?

Cold start. Unable to contact with Nellis ATC. Nellis is not showing in the F5 list. But when you start at other AFB e.g. Creech, Nellis is showing in the F5 list.

Same in the 2.0.4, even in single player. The database seems to be empty or the associated function doesn´t recognize the changes in the definitions of the database. The ARK-22 function doesn´t recognize the "Airport Homer" definitions of the beacons.LUA (1.5.5 and 2.04).

Bug present in 2.0.4

In 1.5.5, names of the units are in Chinesse charaters. To solve that, select "DFLT" in the bottom left section of the ME and resave the missions affected. Unit names will return to latin characters.

It seems that in the 1.5.5 beta ,part of the functions that work with the embark/disembark options has been removed. Not working with IA or player/client helos. The only option that remain for "player" is "disembarking". File affected: Me_actin_db.lua, lack of functions that defines "embarking" for troops. Maybe related with an overhaul of this function.

Bug now present in 1.5.5 beta (041116)

A quick workaround for this. The R-832M system is defined in the coremods folder: \CoreMods\aircraft\L-39\L39C.lua and in the systems folder of the module: \Mods\aircraft\L-39C\Cockpit\Devices_specs\Radio\R832M.lua The later defines the preset frequencies in the VHF band, maybe a leftover of the first L39 iteration that only had a VHF band in the R832 .As a workaround we can set the same frequencies in this LUA as the same of the coremods LUA. With these modification, in multicrew both members have the same standard presets. If the presets are changed in the ME, then we need to update the R832M.lua with the new presets. Sort of the old ark-22.lua of the Blackshark before the update of the ME that allow us to set the R-828 and the ARK-22 frequencies in the ME without editing the LUAs. In a future patch I think that the bug will be resolved but for now this works as a workaround. R_832M.lua

I would like to make the EWR radars to work only with a PBU and a generator attached, a sort of EWR site. I´m trying to use the "depends on unit parameter" like in the SAM sites. For example, I´ve been able to make a 55D launcher dependent of the existence a 55C launcher like in the real world. But for the EWR, I´ve been unable to make the 55G6, for example, to work only with a PBU attached to the group. Any ideas? Thanks in advance.

Ciribob, I´ve sent you a private with the solution for the "radios not selected" that affect the Sabre, the Fagot and the F-5.

Argggggg..... Yes, the SABRE. Too early to write a post from a phone. :)

@Matador, do you push the ACQ button of the R-828 until the light goes on to indicate that the channel is tuned?

A minor bug related with the operation knob: Stby/[]/PCM: .- when it´s operated with the cursor works OK. .- trying to bind to a HOTAS (countermeasures: VEI, [] or PCM), the knob moves to a "intermediate position between the selected". Ex: VEI activated with a HOTAS keybind , knob stays in a position between VEI and [], the Spirale doesn´t change the status to stand-by. Same for [] and PCM. Maybe related with a "default 3 position" instead of a "multiposition limited" definition? Thanks in advance. Edit: the problem is only for the "VEI" position. It gets stuck between "[]" and [PCM] (something like a 0.75 value instead of the expected 0) and the only way to set the Spirale to "Standby" is by clicking on the switch.