Hulkbust44

Except his understanding of TWS vs RWS for the Hornet is all wrong. I'll post my comment on the video here. "You seem to have a fundamental misunderstanding of TWS vs RWS in the Hornet. First, the whole thing about RWR warnings for the bandit. There is NO difference between RWS and TWS. A STT is a STT. A L+S designation is the same "soft lock" in RWS and TWS. Next, there is no difference in trackfile processing. Hornet RWS functions exactly like TWS aside from the auto scan centering (DCSism). RWS just dosen't have frame refresh minimums and will only display HAFUs for a few trackfiles. (And a TUC) Advantage of RWS is larger scan volumes, less cluttered displays. You can always just use NWS to step through ranked trackfiles. The thing is, in DCS the Hornet A/A logic is not right in basically anyway. The aircraft is lacking Multi-Source Integration (MSI). This is a special type of sensor fusion the process all available data to create a track file. The radar is just one (still a primary) sensor that contributes. Other possible contributing sources: donor DL trackfiles, EW suite, ATFLIR, IFF, and HARM. With this, you can designate and fire on tracks without radar contribution. There should be no track display difference between Attack, SA, and AZ/EL formats. You can designate tracks via SA and whatnot. Not to mention that an AMRAAM launch should cue TWS AUTO and command RDR priority." The video is alright...he does a lot of unnecessary things and didn't mention some of the current radar issues and workarounds. Namely hit age out affecting trackfiles. Mobius708

First off, use the ATFLIR. AREA with the AT is a stabilized track of the pod image and is slewable. Slewing in AREA will update the TGT designation in real time as the the FLIR is the "tracking" sensor driving the designation. As with the LITENING, ATRK is just that, it tracks the area image when a point track can't be achieved. IRL there are many more variables that make accurate designations and a point tracks more difficult. On of the reasons the offset exists it so you can track something that's not at the center of the image and slew the pod laser to the target. (IRL. Laser is fixed to FLIR/TV LOS)

Yes, if you talk to the ship they know you fuel state. This is recorded and can be displayed on the LSO platform. IRL I presume ACLS T/C would give the ship your updated state. Mobius708

If you really want to use that axis, make sure it's an absolute one rather than relative. I use the middle finger rocker switch for elevation and it works great. Mobius708

I've seen this outside of AACQ. I'll need to get a track later. Just being in RWS and unboxing SIL will sometimes make it disappear. Mobius708

Bignewy, I've seen this before. What I believe he is saying is that once you exit SIL, the SIL option itself just disappears rather than just being unboxed.

And? What says this shouldn't be possible? Mobius708

Track or tacview? Hornet corner speed is 360kts, 450+ I would definitely see the MIG outturning you.

Of course you can IRL, just not modeled in DCS (yet). Any track shared to the Hornet should be designate able.

Can't do offboard designation yet unfortunately. You can match up the FLIR LOS cue with what you are targeting though. Mobius708

Oop, good catch! You are correct for 011 02 for 92A, both say the scale itself has no limitations. I'll edit the OP.

The sea radar should be able to display at any scale, however tracks can only be displayed out to a scale of 80NM. reference A1-F18AC-742-100 011 03 Page 14 SEASCL.trk

General FRS https://docs.google.com/document/d/1y0H0ceespfcZpq1wok2GKPhrlwdWufkH0xjfmqBkT0Q/edit?usp=drivesdk MDCs and .miz to go with it. https://drive.google.com/folderview?id=10I9V_amA8ruqVGpU961TR6hffETI3Zpg I realize now the additional docs I was going to grab have too much personal information included. I get some screenshots of the general outline. Mobius708

Point is that it doesn't work ever. Plus, the baro side doesn't require that Mobius708

I have a couple from my virtual Hornet squadron, just need a bit to dig up the docs. Mobius708

In the HSI-DATA-A/C format you can not set a radar altimeter altitude under any conditions. However, you can set the barometric altitude warning. See attached track. RDRALT.trk

Just as the title says, HSI "mode" sublevel says MAP instead of CHRT for AMPCD OSB 3. Note OSB 3 can say CHRT, CIB, or DTED. The functionality of toggling the map display should be moved to HSI OSB 6 replacing the position keeping source when in the "mode" sublevel. Reference A1-F18AC-NFM-000 page VII-24-9 and section 24.1.3.2. CHRT.trk

I just went and re-watched the track. The only reason I entered a spin was because the spin recovery logic kicked in as I was getting a decent pirouette going. When it did, the aircraft gave me full rudder and aileron deflection which really started the spin. Also note that the rotation is way too anemic for a proper pirouette, you need to actually enter a "spin" to get close in DCS. i.e I only ever got to a sustained 37 deg AoA, yet to properly enter the pirouette maneuver you should be at 45 deg AoA, not possible in DCS.

No, I don't believe that's possible. Also, one slight issue with that idea, the carrier is moving... Mobius708

Yes, the ATFLIR should be able to predict the position of the target from the previous track if masked. I believe in DCS it is just tracking the target no matter what. But hey, if the target didn't change course or speed it's realistic. Mobius708

Don't think so, that was my problem with the latest track I was going to report.

According to A1-FA18-NFM-000 the selection of map orientation (TUP, NUP) should be sequenced as that pressing the OSB associated with TUP, toggles NUP and vice versa. That's all for this issue really. See section 24.1.3.4.1 This will help us eventually correct the HSI layout as a whole. (No track as I am on mobile. Track should not be necessary as this is an incorrect implemention issue rather than an outright bug.) Mobius708

Yep! The controlled image base or CIB allows for a custom input map set or image to be displayed. See the NFM -000 section 24.1.3.3.1 Something you could possibly do with that is Have recce images of your DMPIs for cross reference. Mobius708

Well, at least it was Mobius708

4. For the AZ/EL you have a FLIR pointing sublevel. With FLIR on, make AZ/EL priority, the press the SCS towards it again with the cursor outside of the tactical area to cue the FLIR PNT subformat. Here you can use the TDC to point the FLIR in Azimuth and elevation. We should be able to consistently have MSI tracks here making it much more useful. You would be able to TDC depress over say a donor track file and the FLIR will snap to it following it as the L+S. SCS towards the display would then command an auto point track and the FLIR would now contribute to the MSI trackfile. Another thing. With the FLIR PNT subformat your cursor initializes over where the stores option was, but now it's FLIR. Just TDC depress and the FLIR image is cued on that display. Mobius708