Harker

The Tomcat doesn't have jamming effects on the radar display though.

Same, updating the server to the latest build resolved the issue. Good to know, thanks guys.

I had a mission with the same issue, which started after the last patch. No track or anything, sorry. The Tarawa was sailing perfectly fine, without any visible damage, except for the fact that it was on fire. I re-saved the mission and that seemed to fix it.

This is correct or at least working as intended. That space is reserved for advisories. There was a debate on whether the line should be blanked or not if no advisories were present, but ED said it's correct for our Hornet. You're supposed to use the central MPCD or the right DDI for the HSI and SA pages or any page that you care about the data at the bottom.

I'd also like to hear an update on this.

Tested yesterday, worked OK for me. Are you sure you had TDC priority to the radar display?

Some F/A-18Cs do have glass UFCs, but we're not talking about the USN Legacy Hornets now, at least AFAIK. An example is the Spanish EF-18.

I use realistic comms, with the aircraft radios and COMM1/COMM2 HOTAS buttons. I have Easy Comms disabled in Gameplay Options. Still, I get all applicable units in the comms menu, regardless if I am tuned in their frequency or not. Is it different for others? Thanks for the reply, btw.

Omg that, so much.

Can you post a screenshot?

Agreed. It'd be nice if they worked on these changes in the background though, separately from the release branch and introduce the whole system when it's ready. Because now, they'll likely have to revert to older code as a quick fix for the current issue (unless their seeker - ECM interaction API is ready), which means wasted dev time. We had something that was working better than the current version, we could've kept it until the new API was fully completed. This is likely pretty complicated stuff to code and I feel for the devs who have to code back and forth between versions. Much better to work on it on the side and introduce the code block(s) when they're ready, without the pressure of releasing it incrementally and dealing with the issues as they pop up.

+1

Guys, a slight off-topic question. Is there a way to disable the comms of oil rigs, gas platforms and specific ships (such as escorts)? I'm doing a similar mission, where I have recreated the oil and gas fields in the Gulf, but they pollute the ATC comms menu (showing up as OIBA) and it's impossible to select the carrier ATC, at least in the F-18. Some great info on here btw, thank you to the guys who posted.

There's an option for SAMs to engage within a certain percentage of their max range. You can set it via Advanced Waypoint Actions in the ME.

STT is definitely needed for NCTR. It used to be that simply designating an L&S in LTWS was enough to get the ROE NCTR part, but that was a bug and it appears that it was fixed or at least improved recently. As for getting an NCTR print now, it worked fine for me yesterday, after going STT on a MiG-29 at around 18 NM.

I tried with the massive, rotating Big Bird radar of the SA-10, no joy.

The popping comms menu occurs when you update or repair DCS with VAICOM running. Make sure to shut down VA+VAICOM, repair/update and then launch VA again.

TBH, I'm surprised this issue wasn't fixed in this patch or in a hotfix. It's a top priority, game breaking problem.

I tested that the other day and it's not implemented. Seems like GMT only detects moving targets, not movement in general. A little disappointing, but maybe it'll be improved in future patches. There's potential though, I detected a helicopter at 80 knots once, but it was showing up as a faint return brick instead of a full brick, so there's some variation coded in.

You should also consider whether it is reasonable or not that a single Hornet can wipe out a convoy protected by an SA-15. Take a wingman or two with you and order them to attack the vehicles, after you take out the SA-15.

+1. Would be nice to get the 4000 RPM sound

The Stable version will be updated to include the new features, presumably at some point in the near future. If you still want to switch to the Open Beta, it's easy and works in a similar way to patching - it's just a different game version, essentially. Likewise, you can easily switch back to Stable. I invite you to take a look at Skatezilla's Updater utility, it's probably the easiest way to deal with this. If you want to run both the Stable and the Open Beta version, that's also possible. You just need to maintain two separate installs.

Isn't REC supposed to also provide threat audio though?

That makes sense, but AFAIK, DCS doesn't model any of the bands and channels, everything is just "radar". Relevant options in cockpits do nothing. Perhaps the jammer behavior will change as this gets modeled.

With an A/G designation, press mode to select R/BL mode. It's unavailable without designation.