Minsky

Because that info panel has been designed in the LOMAC era and only shows info for the primary runway.

Looks like an ILS to me:

Fixed, thank you!

I usually set up the E-2 and S-3 for an air start. (Just to get rid of them, but thankfully IRL they also takeoff before the main event begins.) Other than that, and me launching ASAP from a bow cat, the rest goes as it goes. And yes, for me it also happened after I launched: twice a Tomcat spawned behind the island and blocked other aircraft from getting to the waist cats.

I just checked and it works fine, you don't even need to be logged in to download. Try clearing your browser's cache or using incognito mode to force-refresh the page.

Dirty liar! Upd: 1. Checklists, Quickstart, Ordnance >> Download from User Files << 25 May 2024 - Ordnance page: bomb fuzing options added. 3. RWR Threats, HARM Radar Codes >> Download from User Files << 25 May 2024 - Tiny update: Heatblur's Phantom added. It's not in the database yet, so Hornet's RWR displays it as an unknown contact.

It's great to hear from you and I'm glad the team is alright! I'm sure the update is worth the wait and wishing you luck finishing it (and a separate round of applause for adding Hurghada and Sharm )

We are keen for any kind of communication from ORT. Not for runarounds like this reply. How hard it is to say "Sorry for the delay, we're alive and hope the update will be ready soon, although we cannot give you a firm release date" ? Why ghosting us completely, knowing people are anxious after multiple deadline busts?

I haven't had a chance to try them yet. The ordnance page has no room, and I'm not sure that adding a separate page for what seems to be a mixed bag of cosmetics, bugs, and actually useful options is the best idea. Let's let the dust settle first

No, this airfield has been completely removed from the map.

I regularly fly Retribution missions with 20+ aircraft launching at the same time, and only twice or trice ran into issues. And the culprit was always the Tomcat. Maybe it's just luck, or maybe it's because me and my wingman are trying to clear the deck for AI by departing first. Our problems usually starts during recoveries, courtesy of an occasional BWM driver: I wish ED would prioritize finishing basic stuff (comms / patterns / taxiing) over the flashy things, but I get it that they can sell more copies with the briefing room screenshots than with a correctly implemented phraseology.

Sure thing. Either way is fine with me, although linking will ensure the users have the most up-to-date version, as I often make small unannounced changes to fix a typo or improve something: https://dimon.one/dimon/files/Aerodrome_Data_and_Frequencies/

Well, it's obvious that the engine can deal with below the sea level stuff: we have seabed modelled after all. What it seemingly cannot do is to "cut" into the world ocean that surrounds every DCS map, and drain an arbitrary area. So they had to completely disable that ocean for the Nevada map to make the Death Valley possible. While parts of the engine still think the player goes underwater there, creating various artifacts. 0 ft / -2 ft :

Hi, of course! (Although this version is almost a year old, and I cannot guarantee it is as accurate as the current one.)

> Download <

I didn't mean that you should slave away alone I was referring to that particular Yandex link. Since I don't know all the criterias for including / not including a helipad into the list, it would probably be much faster for you to have a peek on that Yandex map and pick whatever is worth picking - in your opinion. Instead of having someone else writing everything down, only to then check and reject half of that data for some valid, but not necessarily obvious reason.

Yandex Maps have dozens of helipads in that area, and I doubt all of them (especially the Russian ones) exist in Google's database: There is no point for us to write down/screenshot all of this data for you. It would be easier for you to use YM to check anything of interest by yourself. I can assist you with changing YM's interface to English & satellite mode if needed.

Vector data has a relatively small footprint compared to raster images, and typically measured in megabytes, not gigabytes. Same goes for forests: it's not like every single tree is individually placed. It's just a vector shape with a bunch of attributes. If you look at the game files, you'll see that the vast majority of Kola's 145 gigabytes comes from the satellite imagery, ground textures, and mesh (~130 Gb). The rest (vectors, models, shaders) is just pocket change. I'm not diminishing the amount of work they did. I'm saying that the map's footprint seems too large for something that is, according to Orbx, partially in low-res and has no seasonal textures.

And the funniest part is that the map doesn't look like 145 gigabytes at all. More like 45, tops. It's almost like those high-res and winter textures are already included, but disabled for now on.

It's 153 actually (yes, that's after applying today's patch). Upd. The final size of the installed map is 143 Gb. Go figure

Shame that Orbx decided not to participate in the ED Miles program.

It does, thanks!

@BIGNEWY can you please answer my question on the first page?

@BIGNEWY @NineLine I have all the Flaming Cliffs 3 aircraft purchased separately. Will they be "upgraded" to their equivalents from the Flaming Cliffs 2024 bundle? Or, aside from the new title and three new jets, there is no functional difference between the FC3 and FC2024?

I'm having it as well. Track available on request, but it's dead simple to reproduce - launch the "Instant Action > F-16C > Nevada > GBU-10/12 Laser Guided Bombs" mission and let it play for about 20 seconds until the canopy shadows begin moving with the camera.