Azrayen

I find it a bit too shiny... but then, what isn't currently in DCS 2.1? :) (oh, and yes, I saw the picture; take with a specific light, and a bit over-exposed) Will certainly test, to make a more informed opinion! :)

Well, I'm sorry to read that; as I shown, no issue here so I'm guessing the problem is on your side. I suppose you checked the usual suspects? (drivers up to date, no obsolete mods and so on...)

Check your version number against https://updates.digitalcombatsimulator.com Friday morning there was an updater update = no change in DCS per se. Friday evening there was a DCS update.

Apply update from friday evening. Problem fixed. Screenshot 1: custom skin not using dynamic numbering Screenshot 2: custom skin using dynamic numbering Screenshot 3: default skin using dynamic numbering

Yeah, 14° AoA is pretty close to the "not-sweet-at-all" spot of the AoA curve, currently. I guess it'll be better soon. In the mean time, why not aim for a little less AoA if you find it easier. Personnaly, I tend to stick with 14° but hey, whatever works for you.

Indeed. So a little patience is in order IMO :) @ Fox One, you're entitled to your opinion, but writing harsh comments about people without knowing the whole story is probably not getting anyone towards a better mood, don't you think?

I tried the JSGME version, can't see it activated (effects, I mean, I get the UI). I'm probably missing something, first time trying ReShade. What I did: - download the JSGME mod - convert from .rar to .zip (I use OvGME instead of JSGME) - install the mod using OvGME - turn off MSAA (DCS) and all AA settings (nVidia => controlled by app). - launch DCS & fly. Even did the ReShade "tutorial" to no avail. If someone can point what's my mistake... :) [edit] OK nevermind, found it: my DCS is not in the default folder. I had to update dxgi.ini file with correct pathes.

Looks like dev team is aware. External model said to be fixed for next update here: https://forums.eagle.ru/showthread.php?t=188091

Wish logged internally.

1/ There is no auto-land on this aircraft; you can use the AP in approach (with ILS) down to 200ft. At 200ft (height) you must take control back. 2 & 3/ Already answered above.

Unless disk space really doesn't allow it, I advise to keep both release (currently 1.5) and open alpha (2.x) branches installed.

Yes. In fact 4 is not really here. Workaround: Re-enter 4. Then you can add 5 (6, 7...) A memory management issue I guess.

GBU-24 guidance is KO for now. As is its 3D model. Better stick to GBU-16 until fixed.

Why aren't BADs pre-progammed? 1- IRL they may be. In DCS this is not possible. 2- And BAD have different uses, it's not "limited" to a FAF (and IRL not all BADs are FAF, far from it in fact). Using a BAD for a FAF is a possibility, not an obligation. It's an optional aid IRL, and you should be able to make your approach without it: simply fly "by hand" and think of your IDN (HSI) as a map, that's what it is, really. It is possible to add a BUT in cockpit. What is (for now - DCS limitation) not possible is to get the synthetic runway. The synthetic runway is an optional aid IRL, and you should be able to land without it.

Perhaps that's why I wrote it's used for T/O and Landing. ;)

I'm not sure about "C" (at work, can't check). The control is named AA Guns Select, or something close. There is also Magic Select and PCA select. All 3 simulate a 3-position switch on the throttle of the real aircraft. On a side note : reinstalling the game doesn't remove/change your personal files (including controls). If the problem comes from them, reinstalling won't help. I suggest you try resetting your controls (files in Saved Games).

I'm aware of this. But it's (strikethrough) PSIC then, not PSID ;) I'm not trying to nitpick, but to avoid Accipiter to be confused about the two :)

@CrashO good idea :) I would advise to add altitude too. At least for terrains far from the sea.

I'm not aware that PSID may be displayed on the HUD? OTOH, PSID and PSIC are also sometimes called PID and PIC. With PID, you'll get a math in the manual :)

Wow, big work Robin_Hood, kudos. For your "next round", I suggest you add the precise DCS version used (not just 1.5 / 2.0) as indeed FM changes do occur regularly. FWIW, I wouldn't make another round just now, but would wait a bit further down the road. Regards, Az'

1013 is not QNH, it's standard pressure. And Mirage mostly uses QFE for take off ad landing. Set your altimeter to zero. You're at QFE setting. Easy peasy :)

Please note that this chart is an estimation from an outsider. It does not originate from the manufacturer nor from a client air force. So: good doc, to be taken with a pinch of salt ;) Simple example: the internal fuel load is off by 200kg (2960 on the chart vs 3160 IRL). If calculations/estimations were made with "wrong" data, the then results may be "off" too. By how much? It's anyone's guess...

They should be identical at the moment. See here https://updates.digitalcombatsimulator.com/

OK :) Check list (*) 1 - 0 Pilot's memory. ;) Ndeg apparition is an expected behaviour in this case, as per Razbam's implementation. (*) including "payload - check" step Well, ALCM worked for me even before the last update. Must have been something wrong with your DCS installation, or a human mix-up. At least, it wasn't a "general" bug. Glad it's OK now :)

Too many assumptions ;) Let's stick to the bug at hand, shall we?