

Jak525
Members-
Posts
752 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Jak525
-
The operating mode of the radar is displayed under "RDR" in the upper left on the Az/El format. This includes ACM modes such as BST, WACQ, etc. All ACM modes display correctly, including BST, except the HACQ and LHAQ modes. The field is blank when these are selected. AZEL HACQ LHAQ bug.miz.trk
-
The A/G Ready indications for LGBs have been improved since last patch but it's still funky. See attached track. If there is no code entered, the bomb never indicates RDY however it will be un-X'd out still if the master arm is set to ARM. There are a few issues but in summary: ARM, A/G, and code set - "RDY" and no X Any combination that is not the above 3 - no "RDY" and X'd out Thanks Laser guided bombs RDY bug 2.miz.trk
-
The air to ground SMS firing interlock indications for conventional weapons have been significantly improved this patch! However, there are some issues still. For the rockets, they never indicate 'RDY'. They should say RDY whenever not X'd out. Furthermore, they are un-X'd out when the master arm is set to ARM in NAV master mode. They should only show RDY/no X in A/G master mode with master arm ARM. In all other combinations (A/G and SAFE, NAV and ARM, NAV and SAFE), they should be X'd out with no RDY. AG Rocket RDY bug 2.miz.trk
-
GRID coordinates are just another way of defining a waypoint. Any waypoint can be made the A/G designation (WPDSG pushbutton). The FLIR slaves to the A/G designation, whatever it may be. Tl;dr yes, but GRID is a coordinate entry method, it's not directly related to the FLIR.
-
When the HMD is on and not looking at the HUD, and an L&S exists, the seeker will follow the HMD EXCEPT if the radar is in STT on the L&S AND in ACM condition. If the L&S is acquired in regular STT, or while in TWS or RWS, when the HMD is looking away from the HUD, the seeker no longer slaves to the L&S. When the HMD is looking at the HUD, or if the HMD is off, it works as intended. Current behavior: With HMD OFF, or with HMD ON and looking at HUD, AIM-9 seeker slaves to L&S regardless of mode. With HMD ON and looking away from HUD, AIM-9 seeker slaves to L&S in ACM STT; otherwise, AIM-9 seeker slaves to HMD center. Intended behavior: regardless of HMD OFF or ON, or looking at HUD or away from HUD, the AIM-9 seeker should be slaved to the L&S regardless of what mode the radar is in (STT from ACM, regular STT, TWS, or RWS). AIM9 HMD seeker slave bug.miz.trk
-
Uplook actually works. However, the seeker circle is blanked so you have to rely on audio only. Not sure if that part is correct.
-
When the Gun is selected, the radar is always in the ACM condition and cannot be exited. With a missile selected, the ACM condition is selected via Sensor Control Switch forward. But once in ACM condition, behavior is the same with regard to the Sensor Control Switch. It is however a tad confusing because the logic for the Gun / ACM is slightly wonky/broken right now. Hopefully will get fixed soon, though it works pretty ok now. https://wiki.hoggitworld.com/view/F/A-18C#Air_Combat_Maneuvering_.28ACM.29_Modes
-
The HMD will be able to make an A/G designation (the diamond) which all sensors inherently slave to - FLIR, radar, etc. So effectively yes. I'm not sure if the FLIR can be directly slaved to the HMD though.
-
There are quite a few inconsistencies between the HSI and SA formats in terms of the looks of the symbology which should be common between the two. - Waypoints / markpoints are entirely different. On the SA, it's a large circle with a number. On the HSI, it's a small circle. - The A/G Target designation is slightly different. On the SA, it's a relatively large diamond with a dot in the center. On the HSI, it is a small diamond symbol. - The waypoint (upper right, shown in track) and TACAN (not shown in track) data text in the top corners is positioned differently. On the SA, it's higher and actually clips the TDC priority diamond. - The aircraft position symbol in the center is higher on the SA vs. the HSI. - The aircraft ground track indicator diamond is a tad closer to the compass rose on the SA vs. the HSI. HSI SA inconsistent symbology.miz.trk
-
No NIRD display in HUD with L&S target designated, or even STT
Jak525 replied to Stearmandriver's topic in Bugs and Problems
What Harker said is probably what's going on here. Whether by hitting Cage/Uncage or it erroneously happening due to a bug, the AMRAAM here is clearly in VISUAL mode. There's still the bug of the SHOOT cue being shown while in VISUAL mode however. That got reported a while ago though. -
[REPORTED]Aircraft icon location differs on HSI and SA page
Jak525 replied to Jak525's topic in Bugs and Problems
Can we merge these two threads? https://forums.eagle.ru/showthread.php?p=4514395# -
Nice Bunny. Some other HOTAS functions we'll get somewhere between now and 2025: - Castle right should invoke the Attack format on the RDDI unless that display can take TDC priority (e.g. HSI, SA, FLIR, Az/El, AG weapons). Initializes to A/G radar in NAV or A/G and A/A Radar in A/A - Castle left in A/A master mode invokes Az/El format, with the same caveat as above. - Castling toward the Az/El will do various things depending where the TDC is, including STTing a trackfile (technically not AACQ I don't think, only acquisition of a specific track under cursor) and swapping the priority Az/El sensor between the radar and FLIR - (not sure if correct for our OFP) castle left in NAV or A/G invokes Stores format - (not sure if correct for our OFP) castle toward Stores in A/G invokes appropriate weapon format if applicable - TDC depress on HSI should make a TGT at current aircraft position - Undesignate button L&S behavior should work independent of TDC assignment - You should be able to TDC depress with cursor to designate L&S on the SA format - Rang scale should be able to be 'bumped' via cursor on SA just like Attack format
-
This. And as I said, not all implemented yet.
-
Such a chart would be dated at some point because the HOTAS has a lot to be changed/added.
-
Correct. This goes for all weapons and sadly it's quite messed up for basically everything but the Maverick, though luckily the bug has been reported for most the rest of the weapons. The thing is the HARM indication is actually perfectly correct on the HARM format itself. The indication on the STORES format and the HUD just need to mirror what the HARM format shows. The Hornet has a really intuitive interface, even better than the A-10 you might argue, with regard to this stuff. It's pretty obvious when there's a giant X through your weapon indication that you need to do something else to fire it.
-
On the dedicated HARM format, "HARM" indication, with its associated "X" out and "RDY" when appropriate, is entirely correct. However, the issue is the STORES and HUD formats always display "HARM" - it is never crossed out. The STORES however properly displays the "RDY" text but it is never crossed out. Current behavior: HARM indication on HARM format correct. HUD/STORES incorrect. Correct behavior: HUD/STORES "HARM" indication should mirror currently correct "HARM" indication on HARM format Thanks HARM AG RDY indications.miz.trk
-
[ALREADY REPORTED]ADV- line blanking on SA when put on MPCD
Jak525 replied to Jak525's topic in Bugs and Problems
Hey Bignewy, Sorry, mentioning the weapon video in this report is probably confusing since it's bugged right now. Assume this report pretends that bug is already fixed. Basically, that bug concerns the fact that the ADV- line is never displayed on the MPCD when weapon video is put on the LDDI. However, it still is when the LDDI is turned off or the BIT page is selected. This bug simply concerns a bug where, if the LDDI is turned off or the BIT page is selected, the ADV- line won't show up if you have the SA on the MPCD, but otherwise it works. If they're already looking into this they might find it anyway but it is a separate issue so I wanted to make another report to be sure. -
The ADV- line on the MPCD is blanked if it is displaying the SA format and the MPCD is in a condition to be displaying the ADV- line; e.g. LDDI has been turned off or is displaying the BIT or a weapon video page (in this .trk I demonstrate it by putting up the BIT page). Interestingly this error is not present if the SA is on the RDDI (e.g. LDDI in the mentioned condition AND MPCD is off), which I demonstrate afterward by turning the MPCD off. The ADV- line correctly moves to the RDDI, even on the SA. Current behavior: When the LDDI is turned off or is displaying weapon video or the BIT format, the ADV- line will never move to the MPCD if the MPCD has the SA format. All other formats work on the MPCD. Correct behavior: The ADV- line should show on the SA format (and any other format) on the MPCD if the avionics are in a condition to be displaying the ADV- line on the MPCD. SA MPCD ADV- line blanking.miz.trk
-
The castle switch logic for Automatic Acquisition (AACQ) is a bit off right now. Currently, the logic is "Castle right with TDC assigned to RDR ATTK = AACQ". The logic however should be "Castle toward RDR ATTK with TDC assigned to RDR ATTK = AACQ". So obviously if you have the RDR ATTK on the right DDI, as is typical, behavior is the same. The problem lies in when you put the RDR ATTK on the left DDI. You assign TDC to the RDR ATTK on the left and castle right to command AACQ. This commands AACQ but then moves the TDC to the RDDI as well. All other applications of the "bump toward format" castle switch behavior works, like with the FLIR to cycle tracking modes and even the A/G RDR ATTK format to start FTT/GMTT. Current behavior: AACQ commanded by Castle right with TDC assigned to RDR ATTK, regardless of if it's on L or RDDI Intended behavior: AACQ commanded by Castle toward the format the RDR ATTK is on, with TDC assigned to the RDR ATTK. E.g. Castle right for RDR ATTK on RDDI; castle left for RDR ATTK on LDDI. Track attached demonstrating this, and also the FLIR and A/G RDR ATTK format behavior that is already correct. AACQ castle switch bug.miz.trk
-
Good report. In ATRK or PTRK, from a technical standpoint it's considered a tracking designation where the TGT is slaved to the thing the FLIR is tracking. In Stabilized Pointing Mode, it's the opposite where the FLIR is slaved to where the TGT is and happens to be slewing it. This is why the FLIR legend on the HUD only shows for ATRK/PTRK, just like the AG radar for example - RDR only shows when the radar is tracking. If you just TDC depress in MAP, it's not considered a tracking designation and there is no RDR legend. But tl;dr I don't know for sure the correct behavior. However it's possible the way it works now is right.
-
[ALREADY REPORTED]Attack format never references magnetic north
Jak525 replied to Jak525's topic in Bugs and Problems
I heard this before, couldn't remember where it was. Well, I don't think that's an excuse to stray from how the real system works. If you want true reference just switch to true reference. -
On the RDR ATTK format, all heading/track numerics (ownship heading, BRA, etc.) are referenced to true north at all times. This should only be so when true reference is selected in the HSI DATA sublevel. Current behavior: Attack format always shows true headings. Correct behavior: When magnetic is selected in the HSI, headings on the Attack format should be magnetic. When true is selected in the HSI, headings on the Attack format should be true. Attack format true heading bug.miz.trk
-
[REPORTED]Aircraft icon location differs on HSI and SA page
Jak525 replied to Jak525's topic in Bugs and Problems
Can we merge these threads? https://forums.eagle.ru/showthread.php?t=286851 -
[REPORTED]Weapon formats not available on [TAC] menu
Jak525 replied to Jak525's topic in Bugs and Problems
Track now attached. Thanks