Hulkbust44

What's the question here?

When/uf things stop changing. Hopefully that's nowhere near soon though. So much work needs to be done.

With just what we know from available documentation, it's easily 40 percent. Flight Model issues I'm not going to count as there's no way to quantify that. Here's a document we put together a while back taking some of the missing functionality and explaining it. https://docs.google.com/document/d/1qOyE7L1CJ0R1x1kvUZQ4SlvxLsRVb-7RbW68ki1jgJc/edit?usp=drivesdk This isn't even close to all of the issues. Expect for the A/A section we didn't cover any of the bugs.

No, not even it close. I'd give it maybe 60% complete. And that's a stretch.

Sounds like he didn't have IFF on. Being friendly in DCS guarantees a positive mode 4 reply if you interrogate it. So NCTR knew that the aircraft is ine in the theater that's enemy, plus it had a negative return.

Yeah, it dosen't matter what they declare it as, it's still missing major functions.

That also gets cluttered, I don't care about the altitude of 95% the tracks on the display. Just the handful I'm targeting.

Trust me, I set up the Hornet correctly. It's the lack of IFF response modeling/this idea that IFF is only tied to the radar that is the problem.

It’s because you can’t tell the AI JTAC to change laser codes.

Fixed: Slant range cue should not be fixed at 5500

All we really know is that MSI processing is stopped when A/G matermode is entered. Some similar functions still exist, but it's not officially under MSI. Such as SA donor designation for Harpoon employment.

More applicable documents say otherwise. 742-100 is strictly for the APG-65, which we aren’t modeling. We reference it for when there’s nothing else, but if you have a document that states APG-73 then that trumps all. Sent from my iPad using Tapatalk

Yes I see that now, dated November 1st 2002. I’m looking at A1-F18AC-600-500 028 00 dated 2 years prior. Was it really removed? Only reason I could think for that would be if another function took it’s place. Sent from my iPad using Tapatalk

According to what? I have applicable documentation that say otherwise up to a certain date. Highly doubt it was removed though.

Couldn't be simpler, based on documentation the AZ/EL should be accessible in NAV master mode as well as A/A. @BIGNEWYI will send you a PM.

Do you have those controls bound to physical switches? Could be a controller state sync issue. There's a toggle in the settings for reset cockpit state or something similar when it comes to the HOTAS.

Oh, I see that now. I was looking at 600-100

With the COMM 1 or 2 channel selector set to GUARD (G), you are unable to enter a new guard frequency via the scratchpad and the default of 243.00 remains. The means you can't even set the civil guard frequency of 121.50. It should be able to be set to anything within the valid frequency range. (VHF band is increments of 5 KHz , the UHF band is with 25 KHz increments) The G XMIT switches in the back left however will always force 243.00.

This is just a bug, there will be nothing official about it. The trackfile isn't displaying on the Attk format when it is on the SA and AZ/EL. Also the fact that you can TUC it even though it doesn't exist visually.

Would this still be true if you set a DT2 in STT? Or would undesignate step to the DT2? (or L+S for that matter if it's different from the STT target.

After inputting the TERM HDG for a JDAM, I noticed that the terminal heading indicator on the HSI was way off. Unsure if calculations were being made with this incorrect heading, but the symbology itself is certainly bugged. TGT_HDG.trk

As you can see in the track, I make sure to bring the function to the top level on the HMD reject format and there is still no FOV indicator. You only see the designation diamond in the HMD. The Hornet should have a FLIR FOV cue similar to the A-10C. nullhttps://trace.tennessee.edu/cgi/viewcontent.cgi?article=3359&context=utk_gradthes - Using Helmet Mounted Displays to Designate and Locate Targets in the Urban Environment

Just as we see on the HUD, the time datablock is missing from the HMD. TIME_FOV.trk

Well that would be unrealistic, DCS is a little too perfect, but for now that makes up for the lack of INS stabilization...the Tomcat's is supposed to be crap. (based on the time period) Not to mention questionable design choices. I.e. putting receivers on the stabiltors that ya know, move all the time. We need to start with modeling radar correctly...

Not at all. You can have 10 missiles guiding on 10 tracks simultaneously. Also, the missile will only go active at a pre-determined point, doesn't matter what you do in the jet. 2. That's not possible. The "warning" comes from the missile itself. Good questions!