LazyBoot

What's the difference between the different radar display filtering modes? I struggle to see any difference between "TGTS" and "NONE".

It's been a while since I tried it, but I seem to remember that you need to point the pod at the general area you expect to find the laser.

I was more thinking of the fact that he shot at the cockpit and an engine died from it.

Seems relevant:

if you look back to SRS version 1.7.4.0 you'll see the latest 2.0 beta version of lotatc is now making use of this

Since SRS has started reading the status on the IFF panels of different aircraft, it would be nice if the panel had number dials (and non-crashing ident button)

it uses another type of DL, but it talks with the AWACS, and the AWACS talks Link 16

Here's another post with track and video showing this issue, plus a possibly related issue where the targets also drop from the F-16 radar when the JF-17 detects them https://forums.eagle.ru/showpost.php?p=4182979&postcount=47

Here's what I mentioned about the JF-17 and F-16 datalink interaction (will post this in the JF-17 section as well) Any time a contact is detected by the JF-17, the F-16 no longer sees it on datalink The server track is the JF-17, the other track is the F-16 server-20200121-205210.trk Viper_DL_Test-20200121-145232.trk

Me and a friend observed this as well, but for us it even extended to the contact dropping from F-16 datalinks when spotted by the JF-17 radar

Did some small scale testing with a friend... While we didn't come across this issue, we did find that the JF-17 interferes with the F-16s datalink. A JF-17 with datalink enabled in master mode would cause any contact shown as "unknown" to the JF-17 (ie any contact it has not IFFed) to be removed from the F-16s datalink/HSD It did not seem to affect the F/A-18 at all, all datalink contacts seemed to stay on no matter what in that one. This was only with 2 players though, so there could be other interactions with more players, or 2 or more non-hosting players

The altimeter shows true MSL when set to the default 29.92 no matter the actual pressure setting

See post from Wags on page 2

Do they not get the friend pop up from IFF, or do you mean they show you as hostile on datalink? The latter is a known bug with the Viper.

Are you sure you're pressing the hotas command and not the panic button?

Oh, there's certainly something not right going on https://forums.eagle.ru/showthread.php?t=257305

sounds like you're pressing the panic button instead of the normal countermeasure button

From what I've seen, internally DCS calls red "allies" and blue "enemies"

Still... His wording was mostly that it felt a lot closer to the huey than the current Gazelle. And we could clearly see it behaving a lot more like a helicopter should. EDIT: Also, you can see at least shorter snippets here I'm obviously not suggesting to jump on it before seeing proper reviews or anything, but only that I personally think it looks promising based on what I've seen so far.

Here's from the Hoggit Persian Gulf At War server dcs.log-20191128-204842.zip Tacview-20191128-151538-DCS-Persian Gulf At War 1.0.0_morning.zip.acmi.zip

Part of the problem is that there's no change in symbols between tracks you can, and tracks you can't, cycle as the bugged one with TMS right

Will we be able to edit flights from inside the cockpit, or is that only set in the Mission Editor?

Wind direction does normally determine if ILS is on or not, so it would not surprise me if that is the case with dynamic weather as well.

Anything we can do on our end while waiting for the official fix?

This sounds highly improbable to me, even the F5 and F14 have proper lock indicators for more than a single RWR contact