Minsky

It is explained on at least two occasions. Agreed that the manual is inconsistent regarding the number of chaff and flares dispensed in the bypass mode. As for the rest: manual clearly states that S/A and AUTO are work in progress. No reason to describe missing or unfinished features.

Nope, the ADF equipment in our Hornet works only in the MHz range.

Valid frequency range for ADF is 108.00-400.00 megahertz. This includes all VOR and ILS beacons, and all VHF/UHF radios. This excludes all NDB beacons as they operate in the kilohertz range. Chuck is trying to tune to a 113.6 MHz VOR. You're trying to tune to a 443.00 KHz NDB.

Open the DLC page and look for the "ABOUT THIS CONTENT" section. The list is usually at the very top... ...but if you can't find it, carefully read the whole section: Alternatively, if you want to be 100% sure, find the campaign in question in the ED store. The requirements there are listed very prominently, impossible to miss:

GBU-31(V)1/B и GBU-31(V)3/B - базовый армейский вариант. GBU-31(V)2/B и GBU-31(V)4/B - флотский вариант с усиленным покрытием. 1/B и 2/B - обычные 2000-фунтовые фугасы. 3/B и 4/B - проникающего действия для укрепленных целей ("пенетраторы").

No, you must meet all requirements. If a campaign requires a map (as stated on its store page), you must have that map purchased and installed. Be extra careful when purchasing from Steam, because the requirements there are very easy to miss.

Now it all makes perfect sense. Thanks!

I still don't get it. The codes we enter on the AI page: are they to interrogate others, or to respond to some different type of interrogation? If it's the former, then what is the point of interrogating someone with the code 1234 in Mode 3 Charlie?

I understand the transponder part. But what's the point in having the exact same set of modes and codes for the interrogator?

Brilliant, this is 950% shorter than my list, and way more understandable The Hornet uses a similar pattern.

I have a remark in my notes saying this However, I just did a more thorough test, and it is more complicated than that: There seems to be a pattern, but I have no idea how accurate it is to the real jet: X0-X3 - OK X4-X7 - ERROR X8 - resets to X0 X9 - resets to X1 EDIT: so the above ranges give us enough codes to support up to eight four-ship flights.

That's the common "civilian" MODE 3 squawk, entered alongside the other modes mentioned above.

To add to the above: - Mode 1 allowed range is 1-23 EDIT: not quite so - To squawk IDENT, if requested, you press the I/P button on the up-front controller; - Mode 2 is not used in DCS; - Make sure the transponder is enabled ("XP" or "AI" is displayed in the scratchpad).

Yes, Case I and II departures are zip-lip, unless something goes awry.

CASE III departure when on tower's frequency.

You are a wealth of information, as usual. Thanks!

The RECCE event mark switch is used to create "bookmarks" on the flight tapes, or to operate a reconnaissance equipment on certain aircraft. Doubt we'll ever see either function implemented in DCS, so mapping it is a waste of a joystick's button.

They're still tweaking the burble effect; what we currently have is the first iteration.

1. Options > Gameplay > uncheck the "Wake turbulence" and see if that helps. ACLS plus the "burble" effect equals bolter. 2. Waveoffs and bolters are not yet supported. You have to repeat the whole approach, starting from the 'inbound' call (or restart the mission).

Let's add some weight to this report. According to the standards (UFC 3-260-04, or any other appropriate FAA/DOD publication), taxiway centerline (the yellow part) should be either 6 or 12 inches wide. Taxiway centerlines at Nellis are significantly wider than one foot. It's hard to measure them precisely using the in-game ruler, but I would say they're 16 to 19 inches wide. Fix would be appreciated.

I wouldn't hold my breath waiting for a prompt response. The map is considered "completed", and this is not a game-breaking issue. Maybe they'll decide to revisit the NTTR at some point, and will fix this alongside the other problems.

I cannot simply add a couple of HARM codes without adding the rest of the data on each SAM. And this will create a mess, since many of their systems share the codes and RWR IDs with the core units ("BB", "10", etc), yet have a completely different engagement ranges. But I'll tell you what, at some point I'll have to split this kneeboard in two to accommodate the upcoming assets and modules. This will likely give us plenty of space to include the HDS as a separate section.

Это может происходить при триммировании со включенным автопилотом и/или автоматом тяги. Или в том случае, если они до этого были отключены пересиливанием, а не соответствующими кнопками*. Или если скорость слишком высока (>200). Или если автомат тяги подключается слишком рано (>140). Или это очередной баг. * - у себя чаще всего наблюдаю этот сценарий.

(DCS)\Mods\aircraft\FA-18C\Cockpit\Scripts\TEWS\device\CMDS_ALE47.lua

@Wags Not sure why you moved & renamed this topic. I'm not asking for more datalink functions. I wanted to know if the current, ACLS-related, functions are properly implemented.