Santi871

Awesome, looks like the FCS now pulls up during the launch. This wasn't in back when the Hornet released so they must be working on it. This is realistic behavior, but I also want to dig into exactly how many degrees the FCS puts the elevator up at:

Not yet, but it is WIP.

The previous thread for this bug report was deleted, and I was advised to post it again. Attempting to STT an offboard-only trackfile seems to be inconsistent. Sometimes it locks the correct target, sometimes it locks the wrong target, sometimes it doesn't lock anything. See attached track. msi_stt_bug.trk

Air start Hornet spawns with DL and IFF on already.

Human-controlled Hornet does not show in MSI in radar page. AI shows correctly. No AWACS present. Only two Hornets (in the same team). Video: https://streamable.com/k68vo Against AI Hornet: Against human player Hornet: Sadly, I can't get the track working correctly, so I can only upload a simple mission to test. Steps to reproduce: 1. Create private server using the provided mission 2. Have 2 players, one for each Hornet slot 3. Run the mission 4. Observe Hornet does not appear in radar page with MSI, only brick appears msitest.miz

Aim9 seeker is slewed to L&S. TPOD in A/A mode can be slaved to L&S. Firing AMRAAM would make it switch to TWS centered on L&S. Firing Sparrow will make it switch to STT on L&S, as would sensor control right once AACQ is finished. L&S isn't a concept specific to LTWS, it's the name of the primary a/a target of interest in the hornet's systems.

The radar continues to emit with weight on wheels, even though the standby cross is displayed. radar_emitting_weightonwheels.trk

Thanks for the quick response!

The Mach and Altitude does not display to the left and right of L&S in SA page. Only picture I have is from a finnish upgraded export Hornet, but L&S has mach and altitude showing in radar page in DCS Hornet, so it would make sense that it also shows in SA page. missing_mach_alt_sa_page.trk

Yes, as well as bottom-half-only HAFUs.

1. Yes 2. Yes 3. F/F donor tracks are tracks that come from another fighter (ie the fighter is broadcasting what it sees). PPLI is a special track that contains information about that (friendly donor) aircraft, such as its position, fuel state, callsign, weapons on board, etc. This is how friendlies in link16 transmit their position. 4. See above 5. Ingame right now the only C2 asset is AWACS. IRL there are others. C2 and SURV are pretty much synonyms ingame. 6. Just how the symbology is

No, Chuck's guide is incorrect unfortunately. I'll send him a message so he can fix it. Here is a correct description: https://drive.google.com/open?id=17C0jnvo6xdFBQwyvwD3Brpv-ChVEH3nJ (Correlated onboard tracks = onboard + offboard).

You can have different TOO1 and 2 if you undesignate before switching between them (so that it doesn't get overwritten with the current designation).

You are attempting to STT a track your radar hasn't "found" yet. Look into HAFU symbology on wags' link16 video.

the "range circle" is called IRLAR or in range LAR and represents the maximum aerodynamic range of the bomb with the given aircraft conditions. What the team is referring to as "dynamic zones" is the IZLAR, or in zone LAR, which is shown as a small square patch within the IRLAR and it represents the area where not only aerodynamic requirements are satisfied but also guidance ones, taking into account the terminal settings. Within the IZLAR, the HUD cue changes from IN RNG to IN ZONE. If you are within the IRLAR but outside the IZLAR, terminal settings will be ignored one by one (I don't remember the order in which they are ignored) until the bomb can make it.

yep, same issue here

Could you also find out whether mach and altitude should show upon hovering over an offboard track in radar page? Like it does in SA page. It doesn't right now.

You can attempt STT anywhere, including outside the current radar azimuth coverage and of course on top of an offboard track. Like normal, the radar will attempt to track by performing a very narrow (iirc 5 degrees?) scan at your current bars setting. If anything is found, it will lock it. So in that sense, it's a poor man's spotlight search and you can use it to lock offboard tracks as long as they fall within your bars setting. The real spotlight search would be a bit wider in azimuth and also spatially stabilized, but for now what I said above is what we have. I would also love to know if the lack of mach and altitude of an offboard TUC on radar page is intentional or a bug.

AACQ is currently bugged and incomplete - WIP. The bugged behavior you can expect right now is the radar locking the first thing it finds on a left to right sweep regardless of TDC position.

This is unrelated to PLID and was present before it. It's pretty much as jak described, and I reported it to nineline. Unclear if that is fixed internally though.

the MIDS page should display more detailed information, although that does mean taking up another DDI. Potentially looks like this: https://forums.eagle.ru/showpost.php?p=3723152&postcount=4 Unconfirmed though.

Sorry, I was unclear. It doesn't work even with an awacs marking the friendly hornet as friendly.

I'm not sure we are on the same page here. When a hornet locks a friendly hornet, it doesn't get the half circle on the HUD. Ever. Under any circumstances. Is that fixed internally?

The problem is it doesn't work against other hornets under any circumstance. First, they are part of the network and broadcast their information constantly which should in theory eliminate the need for awacs to paint them and say they are friendly. But even if you do have an awacs painting them it still doesn't work from my testing. Hopefully that clarifies it a bit.

It doesn't, cause it's the same info the radar page provides you with a few other additions, but it doesn't give you a God's eye view (ie just like in the radar page it's only providing info about the forward hemisphere). That said, there's a possibility the TDC also has a "sticky" behavior to it where it sticks to and follows a HAFU if left alone on top of one which would alleviate the need for the STEP function. Even goes for pages other than SA. No idea about how accurate that is or if it's a thing in our legacy hornet version, though. Anyway, we will find out when wags or someone else provides with more info I suppose.