grunf

Here's an inHg to mbar conversion table I made for myself, which I keep in the kneeboard. :)

2018 would be my guess too.

There are wind socks, you can place them in mission editor.

There are also people who are not comfortable using beta, and have no disk space or desire to have both versions.

ATC gives you QFE in inHg. Did you properly convert it to mbar?

LOL What's next? Pilot puking all over the cockpit because his breakfast didn't agree with him? Maybe should be added to the failures list. :D

10x is waaay too much. Maybe 10% :) Variable speed would be good, if it's possible at all. IMO Fisherman82's suggestion is the best so far.

Maybe it should be a bit faster, but not so much that it compromises precision. I'd rather have it slower than jumpy. :D BTW should the vertical speed indicator move as you adjust the QFE?

@Calinho You should put only the last part of the link in youtube tags, in this case it would be this: iot4BMv0FDg

I may be wrong, but I think the shadowplay is always running anyway, so it's just a matter of turning the indicator on.

Perhaps the wrong coordinates are fed into the ck when starting from Anapa, thus my suggestion to nav fix on a waypoint near it. :)

Could you create a waypoint near Anapa, do a nav fix on it and proceed with the mission, just to see if the same error is still there?

Just a short one. Almost got bombed by AI. :D

It's a bug.

It's always a pleasure to give positive feedback. :)

I always keep them on auto... too lazy to use manual :D

It does make landings...interesting :D, but it's not difficult to compensate. It just needs some getting used to and practice.

Which mission map? ARK-9 frequency range is 150-1300kHz, which means it can tune to non-directional beacons and runway inner/outer beacons.

The roll isn't that bad IMO. If you need to fly straight and level, use the autopilot. :D

https://forums.eagle.ru/showthread.php?t=182214

By default, the bases selector is tuned to your starting base, you can contact it by using presets. The A/G button is used for VHF frequency, C/F for UHF. All the presets are in the kneeboard. Your flight's frequency is on the preset channel 1 (top row buttons). H button is for transmitting/receiving on guard frequency. There's also a possibility to monitor both selected and guard frequency, but this feature does not work (devs, hint :)). Other "special channels" in the same row, labeled 2 and no label can be set in mission editor. Button "-" is used for manual tuning. Other flights channels are located in the bottom row (buttons 1-9), used with the left knob (group selector). The presets are automaticaly generated and can be found in the kneepad. It does work. :) You either have easy comms turned on, or you messed with the radio selector knob, which will fry the radio (bug). :D

MFG crosswind pedals have a feature that axis can act like a button, so you can assign W key to the toe brake axis. It's not a perfect solution, it will work as a keypress not axis, but it may work for you until the proper brake axis is enabled. I used to use it for Su-27 before it got proper brake axis recently. I think the option is disabled by default, you have to enable it in MFG crosswind configuration software.

Maybe not related, but I had another crash during shutdown after a longer mission (cca 40min). It crashed when I shutoff the high pressure valve and tried to open the canopy (didn't exactly folow the proper procedure :music_whistling:). The master mode was still at NAV. DCS didn't create .crash file (neither did at previous crashes), so I'm including windows log instead, and DCS log. Hope it will help. dcs.zip

Yesterday's update removed the huge stutter when loading terrain, that was introduced in the previous patch, so yeah it does feel much better.