Jak525

When the Radar is in STT with the Gun selected you should be able to toggle the unguided gun funnel symbology via the Cage/Uncage button (I think intended for training). I can PM a clear source for this, just let me know. AA Gun - Cage Uncage Funnel Function.miz.trk

Bump, I know this came in during a big batch of bugs. Thanks

Bumping. This came in during a big push of bugs so I think it got missed. Thanks for getting to our reports, I know y'all are busy! @Harker - Yeah, each patch we've got some progress so that's great. Thanks, appreciate it. It's details like this that make the Hornet feel like much more of a polished simulator vs just blow-stuff-up simulator.

The following HMD symbology is missing in NAV: TDC assignment dot in the center of the HMD cross. The avionics are correctly recognizing when the TDC is assigned to the HMD even in NAV though, because the velocity vector dot on the HUD is correctly placed/removed when the HMD is blanked vs. not. The dot on the HMD just never shows up when the HMD is un-blanked (looking away from HUD). A/G designation diamond and target locator line (TLL). (In NAV it shows on the HUD, but not HMD.) Also, the TDC assignment dot inside the designation diamond never disappears on the HMD when the TDC isn't assigned to it (HUD and HMD). HMD designation blanking bug.miz.trk

Part 3 of the epic HARM trilogy! I'm sure I sound like a broken record with this stuff. Serious props to the devs to getting to this related chain of firing interlock bugs though, they've made iterative improvements each patch recently. Getting small things like this right make the module feel so much more polished (and more intuitive to use). It wasn't in the notes but the HARM "Ready" indications have been further improved this patch. The Stores and HARM format are now one thousand percent correct in all circumstances. The problem can now be narrowed down very simply to the HUD. Correct behavior: HUD will "X" HARM out when Stores / HARM format have it X'd out. HUD will not "X" HARM out when Stores/Harm format do not have it X'd out (and say RDY). Current behavior: HUD is X'd out when master arm is set to SAFE, and not X'd out when master arm is set to ARM. This is simplified logic that does not account for the various other factors which the HARM/Stores indication do correctly account for already. All that needs to be done is simply have the HUD mirror the indications on the Stores and HARM formats. Another thing: the HARM legend on the HUD is displayed in NAV master mode. This is usually not the case for weapons so ED may want to double check their information for this as well. With this fixed, the HARM indications for firing interlock should be a million percent correct and consistent. Thanks! HARM RDY bug ITERATION 3.miz.trk

With the AIM-7 selected, the text GO STT should be shown below the Launch & Steering target TD box on the HUD/HMD whenever the L&S is designated outside Single Target Track (i.e. radar is in RWS or TWS). See EA manual, page 274 and 276. Sparrow GO STT bug.miz.trk

Great catch!

The Pulse Doppler Illumination (PDI) indication on the Attack format has been broken since the STT PRF fix. Sparrows do seem to guide still, so the radar must be PDI'ing under the hood. The actual cockpit indications are gone though. Correct behaviors: - If Radar has not yet been commanded to PDI, with Sparrow selected selecting PRF will command manual PDI and show a boxed PDI indication in place of PRF. - When Sparrow is fired, Radar goes to full PDI. Unboxed PDI is shown in place of PRF indication. (Unboxed PDI text indicates automatic, boxed PDI text indicates pilot commanded.) - PDI indication stops at time to impact + 30 seconds. It can be manually deselected once time to impact is reached. Current behavior: - None of the above happens since a patch or two ago, except the manual PDI function. Sparrow PDI indication bug.miz.trk

There's a bug where Cage/Uncage doesn't work with the Maverick with master arm SAFE. Otherwise not sure.

The vertical lines are the indication that you're in Vertical Acq. If they're not there you're not in VACQ

The avionics have been explained well. Caveats to keep in mind - there are some bugs (mechanical and visual) which make a very intuitive avionics system quite unintuitive: - Gun Acq is also bugged to where you can't Return to Search to GACQ via the Undesignate button when another ACM scan pattern is selected and the Gun is also selected. If, for example, in Wide Acq with the Gun selected, proper behavior would be to press Undesignate to return to Gun Acq. But this is bugged so there's no way to get back to Gun Acq. - TWS Attack format is bugged to all hell when you enter ACM from TWS. GACQ is bugged and won't work from TWS either. - This one's not a bug but just a note to what Harker said, the SET function is only an RWS feature and is ignored in TWS.

It seems in the recent patch (maybe the hotfix or the previous one not sure) the HARM indications have been improved. It is now closer to being fully correct but there are a few scenarios where the indications are still wrong. Note the HARM format is always correct - it's just the HUD and Stores which need to programmed mirror it. Hopefully this is straightforward! Track attached Incorrect scenarios: - SP / Master Arm set ARM / A/G Master Mode / RWR off or no targets detected: Stores should be X'd out. HUD should be X'd out. HARM format correctly X'd out. - TOO / Master Arm set ARM / A/G Master Mode / No H-OFF Stores should be X'd out. HUD should be X'd out. HARM format correctly X'd out. - SP and TOO / Master Arm set ARM / NAV Master Mode: Stores should be X'd out. HUD should be X'd out. HARM format correctly X'd out. All other combinations are fine from what I can tell. HARM AG Ready bug part 2.miz.trk

Adding onto what Fred said there is a large S displayed on the Maverick format to indicate designation-slaved mode. You have to undesignate it (Undesignate button on the stick) to be in manual mode. It's just how the Hornet avionics have integrated the Maverick. If your issue is different post a track or YT video.

The Ready logic for GPS guided weapons was a bit improved over the last patch but is still incorrect. Since other weapons have been improved recently hopefully it can be easily carried over. The issues are: 1. "RDY" legend is never displayed until the timer reaches 7:30. Since the bomb can still be released during the warmup, it should display RDY assuming other conditions are met. (Doesn't mean it's smart to do so) 2. "X" should be drawn on Stores format and HUD when there is no valid target selected; i.e. a PP mission with lat/long and altitude or a TOO mission with the same. 3. When in NAV master mode and the master arm is set to ARM, the legend is not X'd out. Since NAV prohibits release, it should always be X'd out in NAV independent of all other parameters. In summary, "RDY" should be displayed when these things are true and otherwise no "RDY" and there should be an X drawn. - Master arm set to ARM - Master mode set to A/G - PP or TOO mission selected with coordinates and altitude In any other possible combination where the above is not true, no "RDY" should display and there should be an X'd out legend on the Stores format, JDAM/JSOW/SLAM format, and HUD/HMD. JDAM AG Ready bug.miz.trk

Note this report just has to do with the visual indications, and is separate from the issue of A/G Ready status which I will make a separate report for. Anyway, there are two problems with the HUD indications for GPS-guided weapons: 1. The "X" should be drawn through the weapon acronym like J-82, not the mode above. (Note, the "X" is currently not always displayed when it should, but again, I'll make another report.) 2. In Manual mode, the text should read MANUAL not MAN. Evidence: see timestamp 6:24.

The correlation bug is PPLI trackfiles not being correlated to onboard tracks on the Attack format (or the Az/El). Compare the Attack and SA formats. It really sucks cause what's supposed to be an identical MSI picture, just presented differently between the three displays, is messed up due to it.

When an option on the Attack format is selected via the TDC cursor, the cursor should "stow" in the upper-left corner of the format (the position it's initialized in). The one exception is the ACTIVE option in Silent mode. I can message info if needed. Also would like to bring attention to this related, now very old report again: https://forums.eagle.ru/forum/englis...-selection-bug - All top level options except the DATA sublevel, EXP, SIL, and the not yet implemented radar channel select (CHAN) should be selectable via the cursor. This has the potential to be a really useful feature but has not been kept "up to date" as more options have been added/made functional on the Attack format. (.trk title is weird, I reused it from the other bug I just reported.) TWS azimuth bar cursor selection bug.miz.trk

In TWS there is a problem with selecting the azimuth and bar options via the cursor. In RWS, it works fine. - The bar setting displays the options available. However, regardless of which one you select via the cursor it cycles through all options instead of going to the one selected. - 1B is displayed, which is not permitted in TWS. In TWS, it should show 2B 4B 6B when cursored over, NOT 1B 2B 4B 6B as in RWS. - The azimuth selection in TWS, unlike RWS, currently cycles through the available azimuths instead of displaying to you all the available azimuths. It should expand when cursored over to show the available options like in RWS. TWS shouldn't show 140 since that's impossible. So cursoring over should show: 80 60 40 20 not 140 80 60 40 20 like in RWS or VS. Note that directly selecting a certain azimuth or bar needs to automatically change the other, unchanged value if it exceeds limits. E.g. in 4B/20, if you cursor over the azimuth and select 80, it will automatically go to 2B, since the widest azimuth in 4B has to be 40. If you were to select 40 though, it remains in 4B, since that doesn't break the TWS rules. PM'd info. TWS azimuth bar cursor selection bug.miz.trk

Bump - I can message info if needed.

No, TWS and RWS are different. TWS displays all trackfiles as HAFUs (at least the priority 10), including ownship radar only. RWS does that too, with the big caveat that only raw hits are displayed for ownship radar only trackfiles (unless cursored over or designated or I think if an AMRAAM is in flight against them).

Interesting Klar, thanks for the info. I will document that on the wiki, I don't think that's been mentioned anywhere.

https://wiki.hoggitworld.com/view/F/A-18C#MSI_HMD_Indications Will improve it soon with illustrations of the actual HMD boxes and info depicted (callsign, type). But the logic is there.

When you command Return to Search (RTS) from STT into TWS or RWS, the STT target, which is the L&S trackfile, is dropped. Though RWS/TWS will pick it up again quickly, there is a period of time where the L&S disappears and has to be re-acquired. The radar should instead maintain the L&S in the transition. This is particularly important now that hostile/friendly ID is not saved when a track is dropped (an improvement with the recent patch). Information PM'd. Thanks! In short: Current behavior - RTS to RWS or TWS immediately drops L&S trackfile Correct behavior - RTS to RWS or TWS retains L&S trackfile (unless/until it's not found again and dropped like any other trackfile in RWS or TWS) RTS L&S bug.miz.trk

There are a few issues with LARs on the Attack format: - When there is an L&S but no DT2, it should show for the HAFU currently under the cursor, if any. If there is no L&S/DT2 then it should also show, which is already implemented, and if both L&S/DT2 are designated, it should not show for HAFUs under cursor, again already implemented. It's the instance of only an L&S and no DT2 that's wrong right now (should continue to show LAR for HAFU under cursor). - Should not be shown in NAV master mode. - Should not be shown in EXP or SCAN RAID. (Is currently shown/incorrect in EXP, is currently not shown/correct in SCAN RAID.) - SHOULD be shown in STT. It actually used to be; it seems it was broken at some point. Attack format LAR bug.miz.trk

Declutter level 2 (DCLTR2) should remove the Secondary Designated Target (DT2)'s Launch Acceptable Region (LAR) line and theL&S ground track number in the upper left. Currently, DCLTR2 only (correctly) removes the differential altitude and closing rate numbers on the left/right sides of the format. Thanks! Attack format DCLTR2 bug.miz.trk