Minsky

That's part real-life Hornet procedure part CV NATOPS. 150 kias is the standard approach speed during carrier instrument approaches. Speed is not mentioned in the MApt/Waveoff/Bolter section, so one would assume the approach speed still applies here. IIRC those speeds could be overridden by the aircraft's manual -- however, this is not the case with the Hornet so it sticks with what the CV NATOPS says.

As said above, bolters & waveoffs aren't implemented yet (and neither does the ACLS reacquisition). If you don't have human ATC directing you, you can simulate the "loss of comms" procedure from the NATOPS which is roughly described in the "supercarrier AI" boxes below:

Yeah, maybe someday ED would allow us to SHIFT-select multiple units at once

That will be excessive for the purpose of these kneeboards. Besides, such precise magvar would only be valid over a tiny area of the map.

Списываются при оплате заказа.

You can start here: http://gonavy.jp/CVf.html

He likely drawn that chart based on SME's input. Currently, offsets are neither implemented, nor explicitly mentioned in the roadmap. And several threads requesting them got no official response.

This is me being calm actually. Stop trying to assess my emotional state. If you have personal requests, you should've posted them in a wishlist thread. Instead, you revived an old and kinda unrelated topic to post what is borderline rant with zero arguments, and managed to insult the devs in the process with that "90s" passage. It seems that it is you who needed someone to talk to.

Do we even need to respond to this nonsense?

Yes, I've noticed this behavior yesterday while trying to get rid of small rocks, flowers, and other clutter. If you rapidly move the camera to another location a couple miles away, you can notice a hi-res splat texture over a low-res photobackground. It then gets immediately overlaid by several other textures to form the final medium-res look. Really hope someone smarter than me could look into this and submit a bug report if needed.

Untick that little wristwatch icon at the bottom:

I don't mean this to sound rude, but can the team just apply a basic human logic? Imagine the following: - Pilot receives coordinates in the vicinity of a target, creates waypoint, and presses WPDSG. - He hawks the area for some time, trying to discern a specific vehicle, or waiting for it to make a move. - Once finally cleared to engage, he tries to move the crosshair over the target, but WPDSG prevents him from doing so. - Human error, happens to the best of us, no biggie, right? He immediately presses TDC to correct that, and then the cursor starts to drift. While he tries to correct this, the moment's gone, and so is the target. I cannot think of a single scenario where such behavior could be of any use. Especially considering that this "feature" is not annunciated by any symbology, and the crosshair still implies that the pod is stabilized in the INR mode. And if neither the team or users possess documentation that explicitly confirms this behavior, I would rather go with implementation that makes logical sense, instead of something that looks like a bug.

I have it on separate buttons.

You are my hero, thanks!

Have you tried this yourself? How many matches for "STD HDG"?

The jet uses carrier's position and heading provided via datalink.

Hey, you can still make it happen with the twist axis if you setup the curves like this: The only disadvantage is that the brakes will be released if you twist the stick to the extreme right.

No issue here:

Разумеется - как и все остальное, удаленное из установочной директории.

В англоязычной части форума уже некоторое время обсуждается идея разделения модулей и их дефолтных ливрей. Чтобы люди могли скачать только саму модель, а дополнительные скины для нее загружать-удалять по мере необходимости через менеджер модулей. Или выборочно для каждого модуля, или единым паком "Дополнительные ливреи". Вопрос возник в свете того, что сейчас абсолютно каждому юзеру ДКС "навязывают" около 42 гигабайт ливрей. Не интересен Томкэт? Все равно скачай 12 гигабайт скинов. Не летаешь на Апаче? А 10 гигабайт ливрей поставь. Пофигу на поршни? Держи еще несколько гигов. И так далее. Дальше, разумеется, ситуация будет только ухудшаться, т.к. модулей меньше не становится. Что думают по этому поводу разработчики?

To put things into perspective: the total size of all "mandatory" (installed for everyone) liveries for all clickable modules currently exceeds 42 Gb. In many cases liveries occupy more space than the module itself. The biggest offenders are: F-14A/B (15 Gb for the whole folder with Forrestal - 12 Gb of them are Tomcat skins), Apache, MiG-21, and Viper.

Nope, just the coating peculiarities: The only "artifact" here is that they've copied & pasted the same texture across the entire Supercarrier fleet

Make sure the Dispenser Mode switch is ON, and ALE-47 is either in MAN, S/A, or AUTO mode.

Мне кажется, дело не в AGM-154, а в контейнере. Хотя такого количества проблем (случайный дрифт после 10 секунд и невозможность переназначить ППМ) я не наблюдаю, что-то странное с ромбом явно происходит. Пока можно попробовать переключаться в SCENE, или циклично через все режимы обратно в INR - это должно заставить прицел одуматься.

Prerequisites: current OB (2.7.18.30348), a mission with any waypoint, ATFLIR. Correct behavior (second half of the track): SCS > FLIR display HSI > "WPDSG" TDC DEPRESS Move TDC in any direction = all is fine, FLIR crosshair stays stabilized in INR mode. Questionable behavior (first half of the track): SCS > FLIR display HSI > "WPDSG" Try moving TDC in any direction TDC DEPRESS Move TDC in any direction once again = FLIR crosshair still looks like it's in INR mode, but begins to drift like in Snowplow mode. FLIR-INR-Snowplow-issue.trk