Tarres

OK, I will try later.

Mission hangs on about 80% load bar (spawning objects) Need a hard kill of DCS app. Unable to add a log due to this.

Well, both works on the same frequencies. But there is something in the code of the A1271 or/and the ILS beacon definition that makes the A1271 works as intended. I’m unable to set a working custom beacon even with the correct frequency in the ME that works…

Yes, as a stop gap solution, it could work.

OK. The A1271 only works when paired to an ILS signal. In this case works as intended. But I´m unable to set any kind of beacon in the ME in the WW2 maps to mimic this functionality.

Only aural signals that you are to the left/right or centered in the beam.

Yes, the beam aproach A1271 is different. I´m testing now in the Caucasus. I set the A1271 freq in the ME with the ILS freq of Senaki. In flight, If you set to on the A1271, you can hear a morse tone. This tone change according to the doc posted above by RodBorza http://www.tuberadio.com/robinson/museum/command_SBA/ Later I will try to set a A1271 beacon in the WW2 maps. Works perfect.

And the ARI is functional? Yes, we need some documentation about the system.

Yes, like the HInd.

Base is the old LOMAC MiG-21 mod, by the developer.

The LUA files that command the maximun detection range, maximun weapon range and other detection ranges are coded in meters. In DCS, LUA programming is made in metric standard MKS: meters, kilograms, seconds. The Burke has a reported detection range of about 150 MILES for the AN/SPY-1, so about 330000 METERS. The LUA file fo the Burke assigns to this variable 150000 METERS instead of 330000 METERS (150 miles is more or less 330 km) So I think that there is simple bug: range data is not translated into Metric MKS system. The same bug is present in old LUAS that come from LOMAC, i.e. the 1L13 and 55G6 EWR and the 64N6 radar. All of these units have their correct range stated in meters in the Encyclopedia but in their LUA files, range is their values in IMPERIAL. I.E. 1L13/55g6 160000 (160miles) instead of 400000 meters (400km) More modern objects with specifically programmed LUAs for their radars, don´t have this problem. WW2 EWR or the new SR radar for the SA-10 all have their range correctly programmed (130000 meters for example) These maximun values are the base to calculate the "in game contact distance", for examaple a TU-142 flying at 21000ft/7000 meters at cruise speed could be detected and near maximun range. Thanks in advance.

I think that SC comms are linked to the AWLS and other codes of the Hornet. Trying to land the Harrier in any of the SC gives me the same "standard ground ATC". Even the ATC commands me to land from the bow...

Now that we have separate subfolder for copilot controls in the HInd, can we have the same update for the Huey and the HIp?

Setting a DDG with orders: "engage with gun". Target at gun range, nearly visual. DDG engage with Harpoon and MK-45. test ship attack gun only.trk test ship attack gun only.miz

----error--- wrong module....

Only on/off, not volume control in the SPO-10.

This option is in the ME, in the special options tab of the Mi-24P

Not sure if it´s a bug. I think that there is a leftover control called "spot light button right". I don´t see any "right button" on the pilot´s collective.

This control is wrongly attached at the category : 'Ins Cyclic Stick {down = i9K113_commands.Command_StickPark_Ext, cockpit_device_id = devices.I9K113, value_down = 1, name = _('Park/Unpark Operators Stick'), category = {_('Ins Cyclic Stick')}}, It must be assigned to the 9k113 category, to park and unpark the control yoke of the 9K113 system that is now WIP. The animation exists but is not active in the sim. Corected line for the LUA files: {down = i9K113_commands.Command_StickPark_Ext, cockpit_device_id = devices.I9K113, value_down = 1, name = _('Park/Unpark Operators Stick'), category = {_('9K113')}}, On a side note an related to this, the following command: {combos = {{key = 'C'}}, up = helperai_commands.HeliControlEXT, down = helperai_commands.HeliControlEXT, cockpit_device_id = devices.HELPER_AI, value_up = 0, value_down = 1, name = _('Request Aircraft Control'), category = {_('Helper AI Commands'), _('Multicrew')}}, I think that can be added to the category: Ins Cyclic Stick. to unpark the stick and assume control, maybe with a control for the cover. This cover works as intended in the 3D cockpit. You must open the cover to push the "unpark button" and assume control.

It’s for a 4th radio transmitter-receiver. Not fitted in the UH-1H.

Graphical bug: PIlot collective light control left: hat moves right down: hat moves left right: hat moves own up: correct Operator collective light control left: hat moves up down: hat moves left up: hat moves left right: hat moves up This bug only affects the graphical movement of the collective hat, On a side note: can we have a "operator control" in control options like the "Aiming Station"? For a better map controls, for example this "Collective light" can´t be binded to the same hat for the operator and for the pilot. Edit: a bit difficult to see in the track attached. test landing light control hat.trk

It’s a known issue from the beginning. The lua file that defines the 21bis (leftover from when the 21 was a mod for the Lomac) has 2 lines with the number of flares and chaff available for the IA 21 no matter if the SPS-141 or the wrongly named aso-2 (in reality a mixed chaff/flare experimental Yugoslavian pod) are present via the ME. Even the radar associated with the IA 21 is the radar of the 23MLD IA from ED. Lines that define the correct radar (the radar defined by M3 for the 21 “player” or “client”) are commented and inactive.

Maybe I’m too old but “misspelled words” make me turn on mode “seek and destroy that aberration”. To Many years reading laws and other “Sir Humprey Appleby” texts…

Both missions are present but there is a bug in the LUA file that creates the list for the main menu. Names are incorrect in the lua, they are named as "....weapobs..." intead of "....weapons..." Attached solution quickstart.lua

This page explains how the ARK-U2 works. Gerätetechnik - Die Ausbildung zum Hubschrauberführer der NVA. Ich hab's erlebt. (nva-flieger.de) The central position is to establlish contact with the R-852 SAR beacon. Once the connexion is established, move the selector to the left position and set the HSI ARK-U2 selector to the ARK-U2 position. NOTE THAT THE "CENTRAL POSITON IS MORE ON THE LEFT SIDE, RELATED TO THE R-852 OPERATION. The pointer turns to the beacon position. You can use the R-828 as a "reception beacon", setting the selector to the right. But the audio signal of the R828 is listened, using the selector of the SPU. Sorry for the poor exemple... English is not my mother tongue.