Jak525

DCS F/A-18 manual page 171: " If the RADAR is already in ACM mode, selecting AACQ will exit ACM mode and return to last BVR mode." In other words, you should be able to exit ACM via sensor control switch right. This does not work, however.

I was going to note this as well but I don't think that's a bug since the HUD reject does not effect the HMD otherwise.

On the JHMCS, a peak G value of 0.0 is displayed until pulling more than 4.0Gs (peak-G is supposed to show up when 4.0G+), instead of there simply being nothing there. Peak G bug.miz.trk

DCS F/A-18 manual says (page 59) that the speedbrake will retract (when in AUTO flaps) when pulling more than 6.0G. It is instead retracting above 5.0G. Speedbrake bug.miz.trk

It's not finished. I think it's a medium term priority. We still need the TGT DATA and MIDS formats done. (Idk what TGT DATA does but it's definitely related, and MIDS has stuff in it but I don't think it's functional.)

I do believe this is correct.

The DCS F/A-18 manual says that (page 56) in TWS, pressing the undesignate button will step the L&S target to the next lower priority target. Just curious if this is supposed to be for LTWS as well or is this just a TWS feature?

1) Then you'll need to designate another way such as via the HUD when a bomb is selected (TDC depress with TDC assigned to HUD) or, when it's out, the TGP and later A/G radar etc. 2) The laser is for the bomb's guidance, the aircraft itself doesn't see it. Operationally, using an LGB is the same as a dumb bomb, minus entering the code. 3) Because the ASL appears only when an A/G TGT is designated because AUTO bombing mode uses the A/G TGT.

Basically the WPDSG function is just another way of designating an A/G TGT, in this case via a waypoint. The bomb does not care if the TGT is based off a waypoint or a targeting pod or whatever. When it's not a TGT the WP does not matter to the A/G systems, it's just for navigation.

This is correct. WPDESG just uses the waypoint as any other sensor e.g. targeting pod to make an A/G designation (the "TGT").

Azimuth / elevation (as in azimuth OVER elevation) Basically, the RDR ATTK is azimuth over range, where the horizontal axis is azimuth and vertical is range. In AZ/EL, horizontal is azimuth and vertical is altitude (as if looking straight out the nose of the plane instead of from above).

I've also made this mistake but we're not supposed to talk about other simulator products per rule 1.15

Adding to this bug ... HAFU threat ranking is not consistent between the RDR ATTK in LTWS and the SA page. On the radar friendlies are always given a throw threat level. On SA they never are. (So one of these is right, other is wrong, I assume.) Also unknowns and hostiles, even when detected by the ownship radar, are sometimes not given a threat rank on SA but are on the radar.

Please merge my thread with this thread which details this and a related issue further: https://forums.eagle.ru/showthread.php?t=240855

Same goes for the DT2 diamond.

Not to sound like an elitist but I agree with Emmy. However, we are getting the ability to add PP mode mission points via some new planning tool to be added sometime, along with HARM PB points and normal waypoints and stuff (this is one reason they held back the HARM PB mode). So, you'll be able to have all your PP missions pre-filled if you want.

When you STT via castle right (AACQ) with TDC over a contact, the L&S star indication isn't shown on the attack radar format. It does, however, show when you use TDC depress to STT. L&S symbol.miz.trk

Yes but it's not done yet. Don't have the MIDS options on UFC, MIDS format, TGT DATA format, etc. Given they said "for LTWS" I'm guessing they meant MSI though yea

When the COLOR option is not selected on the RDR ATTK > DATA page, HAFUs still have color. track attached radar color.miz.trk

Timestamp 0:26 (right wing inner pylon) Does not seem to make much of a sound

Thank you guys on the Hornet team for all your hard work.

When the decenter (DCTR) option on the HSI is selected, the JDAM launch zone indications go away. Track attached JDAM DCTR bug.miz.trk

I also saw a "B" below too. When I turned off the radar altimeter the "R" would consistently go away immediately (and come back when I turned it back on), so it's definitely got to do with using that. I'd imagine B means barometric, yeah. I have no idea what A means though. It's not the radar -- I turned that off to test. Maybe ED can let us know, as I've never heard this mentioned.

Yeah things probably weren't ready for this week when it comes to new features in the actual plane. Hopefully next month we'll be getting new at least one of the items listed in the mini update recently.

So with some further testing I've found something interesting that is certainly a bug. It appears these DSPLY formats are actually "there" whenever said station in selected in STORES, but they do not draw. You can see in this track I can click on the pushbutton and it will take me there, but the text does not draw until I open the STORES format on that specific display and then go back out. To note the HARM DSPLY seems to be the exception (which I can see being intentional), as it always shows. (track attached to this reply) DSPLY formats bug.miz.trk