Gliptal

From "Brevity MULTI-SERVICE BREVITY CODES FM 1-02.1 (FM 3-54.10) MCRP 3-25B NTTP 6-02.1 AFTTP(I) 3-2.5 (JUNE 2005)": DIRT - RWR indication of surface threat in search mode. See MUD. MUD (type w/direction/ range if able) - RWR ground threat displayed with no launch indication. / RWR indication of surface threat in track mode. See DIRT and SINGER. SINGER (type/direction) - RWR indication of SAM launch. NAILS (direction) - RWR indication of AI radar in search. SPIKE/SPIKED (direction) - RWR indication of an AI threat in track or launch. Note that in this document DIRT is flagged as "Not a NATO brevity word.". Also, both DIRT and the second definition of MUD are flagged as "a new brevity code, an additional meaning, or a deleted meaning to an existing term.", which seems to imply that prior to this document any AG indication was MUD, and an AG launch SINGER; DIRT was seemingly introduced to separate AG indications from AG tracking, and align it with the NAILS/SPIKE pair. I believe MUDSPIKE is a common term that took off for some reason and is now "wrongly" used by the community. Keep in mind though that the point of brevity is to convey a meaning in the most efficient way possible, so if MUDSPIKE is understood by everyone then by all means use it. It's not the correct IRL brevity (as per docs), that's all.

It is. Remember brevity codes are always spoken in context: there is no confusion between "DIRT SA-10 12 o'clock" and "DIRTY LINK". No mention of MUDSPIKE anywhere in the docs. @JNinness you got some of the RWR calls wrong.

"Mudspike" is not a thing. It's Nails for AA search, Spike for AA lock, Dirt for AG search, and Mud for AG lock.

So what are the features of the new media sync exactly?

Never used the F10 map. Use TAD, TACAN, and visual references.

What would be nice is the ability to map different buttons in SRS based on the airframe.

+ engine sounds + mach sounds + missing keybinds + INS bugs + TACAN bug + gauges bug

The devs said it.

Long story short, forget the jammer in DCS.

Really? If RAZBAM needs to resort to anti-consumer practices to survive then it's both my right to call them out on that, and their fault for poor planning.

If TAD is SOI yes.

Wait what? Something else other than the Harrier?

No it's not fixable by a mod. You said most of the threats in your mission are placed in forests: test the Iglas in and out of forests and see if there's a difference.

It probably is a bug, but keep in mind you shouldn't be treating the MWS as the primary defense against MANPADS. Always fly with a buddy and keep a good lookout, as you're already doing. The MWS should complement mutual support and good SA, not replace it.

The missile may have blown your wheels off (they are exposed even when the gear is in the up position), leaving the gear mechanics intact. At touchdown you'd then break the struts and end up doing a belly landing. You can actually check if the tire is blown/missing by looking at your sides with the gear up. If you can't see the black tire, it means either it has blown, the wheel is gone, or the whole strut is missing. This is why you should always fly with a buddy, self damage checks are quite hard to do. :D Keep in mind the following:

Are you sure? Last time I got shot by one the MWS activated. Keep in mind it's not 100% reliable, and has dead zones.

Last I checked this worked, both IFF and antenna elevation. My GPU is fried so I can't test it myself though. EDIT: Nevermind, use this version here: https://forums.eagle.ru/showthread.php?t=170524

TASER https://github.com/Gliptal/taser INTENT TAcview SLEDs Renderer: dynamically generate Tacview .xml files to render SLED attack profiles. All SLEDs parameters must be specified using the "SLED parameters" flags; the target can be chosen from the conventional NTTR ranges ("range" option), or specified through a set of lat/lon coordinates ("coord" option). The resulting .xml renders in Tacview the ideal attack wire, among all relevant decision altitudes; leeway options are also available to restrict or relax the rendered wire's constraints. LINKS install instructions usage instructions program arguments SLED examples Download latest version: 1.0.0-rel1 SCREENSHOTS

You're cycling through the waypoints part of the plan, but what changes is the steerpoint.

I like you guys at Razbam, I really do. Take this as honest feedback. This is not good behaviour on your (Razbam I mean) part, no matter the reason behind it.

In the M-2000C, the HUD is the primary ILS instrument.

I guess the reasoning behind it is that if you're lowering your gear you either have the field already in sight, or you're following ILS down. Once you're on final after a base turn or 5nm for a straight-in there's really no need for precise distance to the airfield.

You'd be surprised how shitty the hardware and software are even on 5th gen planes like the F-22 and F-35. As in "software so shitty the plane shuts down when passing the date line", and "hardware so shitty the avarege PC is N times more powerful".

Suite 7 yes please, so that I can draw childish pictures and send them around in MP.

If I remember correctly the TEL mode was used exactly as the manual states, but with own locked targets rather than GCI supplied ones. It was then removed in an updated due to realism concerns. My personal stance is that it should have stayed in, since we're never getting GCI/TEL anyways due to engine limitations, and having the intercept data on the HSI was nice.