Minsky

Yeah, I see the bug when playing your track, and was able to reproduce it in my own Kola mission. The error vary depending on location. Near Andoya it reaches 50 degrees. Whatever this is, it doesn't affect the Hornet at all. And the Tomcat seems to experience it only when starting hot at the catapult. I wonder if it's somehow related to other TACAN issues reported earlier?

In ye olde Internet webmasters used to use a Google Search widget scoped to their sites. Was a hip way to disguise the inability to set up one's own search. Maybe ED should revive that practice.

Not arguing that the search output is utter garbage (been like this for years), but: 1. The site-wide search dropdown works much better: 2. The filter helps in content discovery: Clearly, attempts were made to make the User Files section useable. However, as many things in DCS, this also moves at a glacial pace. It took them nearly four years after my complaints on removal of the "upload bumping" to came up with the subscription system, which works quite nice. Give them another four, and maybe your little rant here will also lead to a beautiful new search

>> Download << Normandy 2.0 notable changes:

Following the real world naming until this "general DCS problem" is fixed is kinda schizophrenic. Some runways (at places where the flat world matches the round world) are named this way, and others are named differently. Since we cannot 100% rely on the real-world charts anyway, it would be more logical to name everything after the in-game magnetic headings. Ideally, changed dynamically based on a selected year, but a map's default year will do.

A village near Bembridg. It's a misspelled Russian translation of Alderney (Alderney > Олдерни / Olderni > Oderni).

You can't call something a "detailed simulation" if it cannot simulate even the normal, non-emergency procedures. DCS: F/A-18C is out of Early Access and still cannot do that.

Команда в радиоменю с прошлого года не работает, салютуйте хоткеем.

It is whatever your max endurance airspeed is. (Unless you have other restrictions or need to burn fuel.) For the Hornet at 2000 feet that will be 220-240 kts.

Yeah, tried this in Syria and Germany, worked like a charm. I wouldn't worry about that, people post modded files all the time. Here's mine with Syria and CWG added as an example: \Mods\aircraft\FA-18C\Cockpit\Scripts\Computers\MC_No1.lua -- 1. Ensure that the line 23 below has "id" instead of "name". -- 2. Get self_ID value from \Mods\terrains\(map name)\entry.lua, e.g. "Syria". -- 3. Open \Mods\terrains\(map name)\beacons.lua, search for BEACON_TYPE_TACAN and BEACON_TYPE_VORTAC and grab their beaconId values, e.g. "airfield44_2". -- 4. Copy & paste the whole "elseif" section below and populate it with the self_ID and beaconsIds values. -- Note that the Hornet will only display the first ten beacons in its TACAN database. -- Thanks to Corsac and JTFF_Gemini for figuring this out: https://forum.dcs.world/topic/380541-hornet-tacan-database/#comment-5708106 local gettext = require("i_18n") _ = gettext.translate device_timer_dt = 0.05 -- 20 Hz need_to_be_closed = true -- lua_state will be closed in post_initialize() ------------------------------------------------------------------------------------------------- -- TACAN Data Stored in Memory (only for T4) ---------------------------------------------------- local fileName = get_terrain_related_data("beacons") or get_terrain_related_data("beaconsFile") if fileName then local f = loadfile(fileName) if f then f() end end theatre = get_terrain_related_data("id") -- Changed from "name" that didn't work TACAN_Data = {} if beacons then local beacons_by_id = {} for i,o in pairs(beacons) do if (o.type == BEACON_TYPE_TACAN) or (o.type == BEACON_TYPE_VORTAC) then beacons_by_id[o.beaconId] = o end end local getTACAN = function (id) local res = {} res.Channel = beacons_by_id[id].channel res.Elevation = beacons_by_id[id].position[2] res.Latitude = beacons_by_id[id].positionGeo.latitude res.Longitude = beacons_by_id[id].positionGeo.longitude return res end local theatre_ = theatre or "none" if theatre_ == 'Caucasus' then TACAN_Data = { getTACAN('airfield22_2'), -- BTM getTACAN('airfield24_4'), -- KBL getTACAN('airfield25_3'), -- KTS getTACAN('airfield29_9'), -- GTB getTACAN('airfield23_4'), -- TSK getTACAN('airfield31_4'), -- VAS --getTACAN(''), -- --getTACAN(''), -- --getTACAN(''), -- --getTACAN(''), -- } elseif theatre == 'Nevada' then TACAN_Data = { getTACAN('airfield1_4'), -- IndianSprings getTACAN('airfield2_2'), -- Groom_Lake getTACAN('airfield4_1'), -- Nellis getTACAN('airfield18_4'), -- Silverbow getTACAN('airfield3_4'), -- LasVegas getTACAN('world_5'), -- Daggett getTACAN('world_19'), -- PeachSprings getTACAN('world_14'), -- BryceCanyon getTACAN('world_12'), -- WilsonCreek getTACAN('world_18'), -- Coaldale } elseif theatre == 'Syria' then TACAN_Data = { getTACAN('world_13'), -- GHI getTACAN('airfield44_2'), -- Akrotiri getTACAN('airfield16_0'), -- INCIRLIC getTACAN('airfield46_5'), -- Pafos getTACAN('airfield64_1'), -- PrinceHussein getTACAN('airfield30_1'), -- RAMATDAVID } elseif theatre == 'GermanyCW' then TACAN_Data = { -- Hornet's database is limited to ten items so comment out those you don't need: getTACAN('world_0'), -- Hamburg --getTACAN('world_1'), -- KIR --getTACAN('world_3'), -- WSR --getTACAN('world_5'), -- WRB getTACAN('world_10'), -- Nattenheim --getTACAN('world_13'), -- BKD getTACAN('world_14'), -- Fulda --getTACAN('world_15'), -- HLZ getTACAN('airfield200_2'), -- Bitburg getTACAN('airfield235_0'), -- BUCHEL getTACAN('airfield11_1'), -- Fassberg getTACAN('airfield163_6'), -- Frankfurt getTACAN('airfield159_0'), -- Giebelstadt getTACAN('airfield16_1'), -- Gutersloh getTACAN('airfield155_0'), -- Hahn getTACAN('airfield232_0'), -- Pferdsfeld getTACAN('airfield165_2'), -- Ramstein getTACAN('airfield156_1'), -- SEMBACH getTACAN('airfield162_4'), -- Spangdahlem getTACAN('airfield28_6'), -- TEGEL getTACAN('airfield29_1'), -- Tempelhof getTACAN('airfield170_1'), -- Wiesbaden getTACAN('airfield32_1'), -- WUNSTORF getTACAN('airfield158_0'), -- Zweibrucken } end end -- Failures F18_MC_FAILURE = 0 Damage = { {Failure = F18_MC_FAILURE, Failure_name = "Failure_Comp_MC1", Failure_editor_name = _("MC 1 FAILURE"), Element = 4, Integrity_Treshold = 0.7, work_time_to_fail_probability = 0.5, work_time_to_fail = 3600*300}, }

I'm trying to record a track but it comes out bugged. Moving the finger lift is not recorded, so on the replay aircraft takes off with its engine off, and is essentially uncontrollable upon taking control. t45_takeoff.trk

Could you please reproduce it in a clean mission? I doubt anyone would bother finding and installing all these mods. Not to say that any of them could potentially conflict with the Goshawk. Nothing, it's there to reset the HYD warning.

I presume it should auto-populate this list with TACAN and VORTAC entries found in a map's "beacons.lua" file. However, this feature seems broken or was never finished. The only two maps where it "works" are Caucasus and Nevada, and only because their beacons were manually added into this file: (DCS)\Mods\aircraft\FA-18C\Cockpit\Scripts\Computers\MC_No1.lua My attempts to add other maps to that file were unsuccessful.

Reworked my checklist for the latest version, please enjoy: > Download <

It worked, thanks! A classic senior moment. Haven't set up a new module in ages and totally forgot that is how it works in most of them.

I'm also not sure why the master alert goes hysterical when I lower OR raise the hook.

Hey guys, congrats on the 1.2 release! Is it a known issue that the comms menu doesn't appear at all when starting in the air? It works fine with ground starts, both hot and cold.

Noted, thank you!

I don't think so. They just reduced the boundaries in the Mission Editor to prevent people from seeing too much of the low fidelity, not-yet-ready area. The "land", if you can call it that, is still there.

I guess it is included in its period correct state: the aerodrome is not yet operational, but can be used in case of emergency. Personally, I see all these unfinished, unmarked and closed aerodromes as a free bonus. They never promised us Qusahwira, and it is not crucial to a map that is focused on the Strait of Hormuz. So, instead of complaining that my glass is half-empty, I'm grateful that someone has poured in a little bit more water than promised.

This?

Bumping to remind that the issue remains unresolved, and to report another one: The RWR displays the old AH-64D (NOT the new "BLK.II" model) as an unknown contact ("U"). Should probably be "64".

Additionally, "opening" Qusahwira would require reworking the whole area which is currently a barren wasteland (no mesh, no GIS data, no proper textures). Probably too much of an investment for such a remote location on a map that has been considered complete for years. (But for the record, I'm two thumbs up for the idea.)

Download

RWY10-29 names in the H-3 Southwest Airbase's info panel are not reciprocal and don't match neither true (124-304) or magnetic headings (119-299). Should be changed to 12-30. At least this looks like 30 to me: