Rainmaker

It was asked on youtube, the answer is yes. Video from Wags potentially forthcoming.

@RShackleford @Klarsnow Pretty easy to tell where this photo was taken. Lol Aircrew gonna aircrew... Working on the post marshall salute?!? Didn’t know hours were that hard to come by. Offtopic...but on topic.

Pretty sure mine was blank by default and DCS didn’t default a key press...

It’s been 16 years (to the day pretty much), so I’m not going to claim to remember the exact reason. We had some jets on alert in case they had intel about some of the HVTs (think the deck of cards) that were loaded with AGM-130s. They were basically “no fail” missions so there were extra tails with pods in case they needed spares had the prime aircraft broke. That may/may not have been why those still had them on there. We dropped a few 130s at the start, but they were not dropped on a continuous basis as they were not really necessary.

Datalink pod.

That’s probably a safe bet.:) “Better him than me” as they say.

Gulf War II pics WAMPUM

Before, the default was a diamond, which is hostile. If people mucked up the interrogation, it stays hostile. Now iit defaults to the box, which is unknown. It’s now working the proper way.

I haven’t looked at the manual from ED personally, but that could very well be the case.

NATOPS manual, page 1-2-61. Listed right under the warning.

No bug...normal

No, the RVS would however...unless they have changed the requirements again.

LVS = Left Vertical Stab light. It’s a running joke because the bulbs for those are POSs.

Stupid LVS is out....

From the looks of it, and this may very well be proved to be wrong by someone, the radar through limitation or by choice, doesn’t show uncorrelated tracks on the radar screen. This meaning that it will not show interrogation/datalink symbology on the radar screen for anything it cannot match up to a radar return. Some aircraft can do this, and it would be awesome to have, but it doesnt appear that it’s a capability on the hornet version we have. Again, I may get proven wrong on that, it’s just what I have come to understand.

I think this is just left around from the old IFF code, and very well may be fixed already I just didn't see it mentioned in Wag's mini-update, but the TD box will mipple between the "unknown" TD box and the diamond depending on whether it's inside or outside the HUD FOV. It still acts like it did prior to the last beta update. Just worth an honorable mention, the "shoot" cue was still present also when I did this against a friendly refueler even after trying to interrogate. The DL symbology never changed to friendly either. This was just on the instant action refueling mission so it may be due to the mission setup, I don't know, so possibly a non-issue, just thought it was worth bringing up. Track attached. HUD TD Box Mippling.trk

You could save a bit a of time by watching Wag’s videos and reading the mini-update thread. What you are describing is not a bug...it’s not implemented yet!

Pretty sure that’s normal for AA master mode castle sw operation.

It was acknowledged in Wag’s mini update that it’s fixed. Perhaps they’ll throw a hotfix out there this week.

I would imagine the -82 is better than the both of them by a generous margin. The V1s have been around for a while now.

Someone apparently merged threads with no context. The first part of his origanal post was already acknowledged to be a bug. It broke the DL, never saw anyone say it was supposed to work that way...no need to go on the defense about it.

A1-F18AC-NFM-000 Page VII-24-55

To your bottom question...yes.

You can still drop the azimuth width and point the nose, just can’t stay on the gimbles like that. If you are super good, you can still command mini-raster with the designate button, but I think that’s like a 3-5* sweep. :)

Why MD/Boeing didn’t take a page from the F-15E when it comes stuff like this I will never understand