Minsky

Это записано в дорожной карте и входит в топ-10 самых востребованных фич:

Я бы еще от нормального мануала не отказался. В текущем, например, радиостанции вообще не описываются, а это не самая очевидная часть вертолета.

Да.

Начать можно с переделывания архаичного F-меню на что-то более вменяемое. Об этом здесь была двусторонняя дискуссия с разработчиками года два назад. Договорились до пульта управления звездолетом силой мысли и дискуссия затухла. Хотя я изначально предлагал просто добавить перемещение по этому меню хаткой/курсором.

Обычно после таких видео до релиза проходит пять-семь лет.

Так лучше?

Вот и вам для наглядности: Я банально поигрался с позицией камеры и фокусным расстоянием. Оставшиеся миллиметры можно списать на различия в геометрии кабины, аэродинамике и 80 футов высоты.

Yeah, that came out a bit harsh, apologies.

Love how people (ngreenaway, not you) repost stuff without providing any context: https://discord.com/channels/536389125276827660/544224332709232660/1151551825972039802 Looks very promising, indeed, but I have to try it to believe it

Пикантности этой картинке добавляет то, что VFA-14 и VFA-103 никогда не летали на F/A-18C - обе эскадрильи перешли с Томкэтов сразу на Супер Хорнеты.

It is somehow related to wind speed in a mission. Even in a new one, with only the client aircraft and nothing else, the Ovda TACAN stops working once winds are set to the values from your mission: And in both cases the TACAN starts to work again once wind speed is set to zero for all four layers: I haven't had time to test different wind settings and other TACANs on this map, but it looks like a bug to me. Sinai-Ovda-Tacan-43704-1.trk

P.S. I hope you're on the latest OB, because a couple patches ago the SE had some major TACAN issues.

It works just fine.

As long as I'm aware, this behavior is true to the real aircraft. Within 5 seconds after the HOME waypoint is selected, and with weight off wheels, the system attempts to calculate the home fuel. If failed, it crosses out the number and removes the arrows. You can sorta circumvent this by altering the coordinates of the currently selected HOME waypoint. Re-entering "N00.00.00" would suffice.

A bit later perhaps, but it seems that any town and city on this map is affected to greater or lesser extent. I usually fly with my FPS locked at 50 to keep the GPU quiet. And seeing 17 FPS at Rio Gallegos and 50 FPS at Hipico got me thinking that the problem is limited to large cities only. But when I unlocked FPS for today's test, it turned out that things at Hipico are as bad as anywhere else: a 50% performance drop from ~95 to 50 FPS.

Did some of my own testing at Rio Grande. There are no hedges there, so the objects seems to be the primary cause of the ~70% drop in performance: Also tested the same area at various altitudes. Once I began descending from the 95,000ft camera's limit, the performance almost instantaneously dropped by 56% from 89 to 39 FPS. I hit the lowest point at around 85,000ft: the same ~70% performance decrease. Descending past 55,000ft, I began to naturally and gradually regain some frames, as it had less and less of the city area to display. Finally, I tested it from various distances by placing the free camera at the sea level and pointing it in the direction of Rio Grande. The performance peaked at 20 nm, and began to sharply decrease after 18 nm. The lowest point came (and stayed) at 11 nm, resulting in ~61% performance decrease. TL;DR - The objects at Rio Grande are responsible for ~70% drop in performance. - Performance at Rio Grande starts to sharply decrease when lower than 93,000ft and/or closer than 20nm.

Seems so:

That's why you are a beta tester and we're not Such an obvious thing to do to narrow down the issue, yet it hasn't even occurred to me. Thanks for helping us!

Hope I read this part correctly, so I must stress this once again: the problem doesn't go away with altitude. Unlike the original issue with this map when you could only see performance drops at below 2000 feet or so, this one persists all the way up to 80.000 feet (just below the free camera's altitude limit).

A bit simplified in DCS, but overall correct as is™

First of all, nice to see you finally reacting on this ICYM my post on the previous page, I would like to reiterate that this is not just some annoying performance dip, but a rather huge FPS drop, down to unplayable values. It occurs whenever I look at any big city, even from 80.000 ft.

This is not true.

-camera -8.603446 1.030187 394.445288 -cameradir 0.929578 -0.357415 0.090214