Nealius

IFF, datalink, RWRs are not as accurate and foolproof in real life as they are in DCS. Someone on the CG FUBAR'd their ROE matrix.

User files servers are such garbage that it takes an hour to download a 300mb skin, vs 30 minutes for the entire pack from Megaupload if the Discord links were working.

Is there a direct link to the skins that bypasses Discord? All the Discord links are dead.

How often does your yacht go 130kts?

Ah that was it, thanks.

When online, using uncontrolled AI helos on the ramp as targets or as scenery, some helos in each AI group are invisible to the client. Note 5 helos parked in the mission: 3 Hips and 2 Hinds. Note the TGP footage showing only 3 helos: 2 Hips and 1 Hind. This is easily reproducible with a dedicated server.

Seems to have been fixed with the December update(s).

There was a post I saw a couple days ago with a clear-canopy mod and updated lua file entries to mitigate this but I'm unable to find that post. Anyone know where it might be?

Has it ever moved? A year or two ago I played through the mission and completed all the tasks, but the convey never actually moved during the mission.

And CNATRA, like I said. Specifically P-816 if I recall correctly. Diagrams and paragraphs are cut directly from it. Literally cited as a source at the end of the document. One thing that many people don't have awareness of is that some first-hand SME info is only valid for the time frame and squadron(s) they were flying. SOP differs from squadron to squadron, time period to time period. What was true for operations in 1997 isn't necessarily going to be true for operations in 2006, or in 2020. Now add the objective fallibility of human memory that often mixes things up, and it's wiser to cross-check testimony with official documentation. I.e. best to avoid appeals to authority. So while it is a "definitive" guide, it's not absolute and there's still a lot of leeway for exceptions. Unlike a lot of other SMEs out on the social media sphere who make it a point to stress that their information is valid for when they were in service and not necessarily still valid today, the lack of that same humility shown by the author of the document is a red flag for me.

When using the new fog and dust settings, we get proper CASE III recoveries but the launches are a bit confusing. The crew is holding light wands and the carrier lights are on, implying a CASE III state, however turning on the lights in the Tomcat does not result in a launch per CASE III procedure, and there is also no CASE III departure comms, implying that the launch was in CASE I state. I should note that in full CASE III, e.g. night, everything works fine. Is there any way to check what CASE state the carrier is in via a lua file or trigger or something?

Most of it is sourced from CNATRA, with images and paragraphs cut/pasted directly into it. Despite using it as a primary source the author claims CNATRA is "useless" whenever someone points out all the inconsistencies and contradictions.

None of them spawn facing outboard. They all spawn facing inboard towards deck center axis. They also would not block taxiing of the ones next to them at all. Elevators packed two Tomcats all the time in real life. If it's not possible to do so in DCS then that insinuates that either the F-14 models are larger than they should be, or the carrier model is smaller than it should be. I doubt either is the case.

Ah that could be it. I admit I've never had a use-case for making the HUD SOI in the Hornet. I wonder why they're doing it during approach?

I haven't checked recently but there's a possibility it was broken in the last patch or two. It worked last time I checked in November-ish.

Rhinos have an energy caret opposite the AoA bracket. The second video is a Rhino. The other two videos do not have an energy caret, so not likely to be Rhinos, however I can't find any info on what that dot in the FPM is on the first and third videos.

In my experience, if it's not going left on takeoff roll that usually means I cocked up my tailwheel. It needs to straighten out before starting the takeoff roll.

Is erroneous maximum temp limit also reported? This thread was ignored for months while a specific one about erroneous minimum temperature was addressed within a week.

Even with those slots open it still causes issues in multiplayer. Last time I tested I needed close to 9 open spawn slots to ensure a single client Tomcat spawn. There's no logical reason we shouldn't be able to spawn two Tomcats on each elevator either.

Yeah I agree, but I'm holding judgement until HB or ED discloses anything about the behavior being intentional via modeling of radar scintillation/otherwizardryI'mtoodumbtounderstand. Until then, I rip my burst from tail to nose to ensure hits.

To be fair, this discussion can go both ways because Victory's (an SME who actually used this thing in real life) explanation points to this being realistic, while other modules tend to have similar radar gun solution issues as well. This has potential to be not much different than people expecting high accuracy from their RWRs, or high reliability from TWS when reality is different.

To draconus' point about the Tomcats, nose way over the foul line. Furthermore, the system ignores static objects that the manual explicitly states should be taken into account by the taxi route and parking slot logic. It also incorrectly judges the Tomcat's width, as if I remove the S-3 from Elev. 2 I would have been directed to park there instead.

Not valid for Hornets that's for sure. SH-60s are supposed to go there.