MARLAN_

I was told HPRF/Husky was supposed to be coming "next patch" about 10 patches ago, so I think it was forgotten.

Tracks work decently in singleplayer if you keep them really short. Like only a few minutes long.

Could ED clarify what is allowed? It's not very clear. If statement C is blanket not permissible then almost nothing in DCS at all is permissible so you can probably see how everyone is confused.

If I enable the Kegetys Shaders it makes my DDI's green (I am using the LCD Mod to make them black/white) does anyone know how to stop the shaders from making my DDI's green again?

It would be definitely beneficial to understand ED's definition of the LOST cue so we can react properly to the DCS implementation. What is the meaning of the LOST cue in DCS and what information is being passed by it? What sort of action should we take in response to this cue (should we stop supporting a missile in flight when we receive a LOST cue regardless of the missile's ability to intercept)?

For example, a Fulcrum is detected by your ownship radar at 47NM, but you are unable to lock him (STT) until 39 miles. An A-50 is detected at about 95NM, but you are unable to lock him (STT) until 80 miles. STTLock2-7-11.trk STTLockA502-7-11.trk

Damage Model Improvements Flight Model Improvements (G-Onset, Pitch Authority) - the DCS F18 is unable to perform a nose-low merge without overspeeding uncontrollably (as an example, the DCS F16 can, and performs it much more realistically). DLZ still needs some tweaking, shots are hitting at Mach 2 that the DCS MC says is outside RMax. RDR/JMR PRI (Looks like RDR PRI was implemented/hardcoded this patch, but you cannot choose JMR PRI on the RDR ATTK Display) Offboard tracks should appear on AZ/EL TWS AUTO automatic select conditions HPRF active mode for AIM-120 (Husky) and appropriate symbology (flashing A / solid A) Steering Dot should indicate lead & loft and not be anchored on top of the target (works in DCS for the AIM-7, but not the AIM-120) Radar Fixes (SCAN Raid 0 ATA, LOST Cue, Undesignate Switch in SCAN RAID shouldn't exit SCAN RAID, it should step through trackfiles like it normally does in RWS/TWS) Ability to set OCID (L16 ID) E.g. "A" "B" "C" "D". Ability to colonize "CPHR" on the UFC for enabling COMM 1 and/or COMM 2 for secure radio (Even though radios are WIP, SRS could use this colonized state to implement it through SRS) AIC/FF Channels ACLS

The target is 8.1 degrees AOA not 9-11 I haven't noticed anything majorly different, the tiny bit VVI float thing others have mentioned I noticed a little bit. BTW, You don't need to go to half first, just go straight to full, it's an extra step you don't need.

Really happy to hear the first bug with the Lost Cue was fixed this patch! Awesome that it uses missile parameters now instead of the aircraft. One more small issue to fix: The LOST cue is triggering when the target is still in range. The track and Tacview clips show the missile with plenty of energy both when the LOST cue is displayed and at intercept. Thanks for the work on improving the F-18 systems! Missile at intercept still has plenty of energy and is certainly not kinematically defeated: LOST Cue is indicated here (Time +02:12): Tacview-20220320-004811-DCS.zip.acmi LostCue2-7-11.trk

Depending how old the data is, the F-18 FM has changed in the past year.

At the absolute very least, we need to be able to designate offboard tracks so that we can properly run the targeting and reattack phases of BVR combat. Of course there's a ton more that should be modeled as well, and information is available online and on the forums as well like you mentioned Harker. I wonder what exactly is the requirement for "public enough" information? If it has to be officially public release to be used, 90% of what is in DCS is breaking that rule.

Your numbers aren't matching up at all, maybe you took off from the ground or data is old? Although tests should be isolated; test climb, then test cruise separately, etc, otherwise there is more opportunity for user error to creep into data. Just tested 35K, M0.8 air-start: F/A-18C, Centerline Tank: 1508 NM (Optimum Range) F/A-18C, Centerline Tank: 1380 NM (Cruise @ 35K, Not Optimum Range) F/A-18C, Centerline Tank & 6/0/2 AA Load: 1180 NM (Optimum Range) F/A-18C, Clean: 1308 NM (Optimum Range) F/A-18C, 3 bags, 1708 NM (Optimum Range)

Here's better quality images, and if you tune the brightness knob slightly, you can see the TV/IR are basically identical. There is no infrared at all. https://i.imgur.com/49FgMYn.png https://i.imgur.com/f2EAW6B.png

If you turn ALG off on IR mode, and then decrease GAIN by 1 step, the TV & IR modes look almost identical. With ALG left on, IR just looks like a saturated version of TV... It seems like we've lost IR capability entirely at first glance.

Has anyone tested on Marianas? There was a note in the patch that The map is prepared for use in FLIR mode Maybe it's only on that terrain? I have only looked there so far though, my game has been crashing on me, trying to run some repairs and figure it out. That said, the FLIR on that map looked different than before... hard to say it is what is supposed to be intended though, just different. EDIT: After looking again, it looks like "IR" mode in the ATFLIR doesn't really do anything. It just looks like a more saturated TV mode...

I don't know about other modules, but the F/A-18C doesn't even have wind data in the aircraft, it simply displays 0. That may be part of why the GBU is not compensating for wind.

Sadly, we can't do that in TV mode (unless I'm missing something), which makes TV nearly completely unusable right now. I used to prefer TV most of the time, and have been forced to use IR lately.

The DCS SC LSO is not very good, typically my advice is to just ignore it, hopefully it will be improved when developers can devote time to the supercarrier core features like LSO, Night Wands, NV PLATCAM, etc... After the briefing room maybe we will see these core features developed. As for why it's bad, is if you legitimately had a 3PTS landing, that means you landed with all 3 wheels down at touchdown, which means you had nearly 0 degrees AOA, which typically means you pushed the stick forward to force the landing instead of taking the bolter. This is a dangerous practice. Assuming you were on AOA until touchdown, it's just the DCS SC LSO giving incorrect grades.

Just in case anyone was thinking the black/white visual mod affected anything (I was curious too, who knows!) here's another recording with no mods whatsoever. (And oh my, it's impossible to see anything on the screen, especially in green. Too bad we can't adjust the screen independent of the symbology, turning down brightness helps a tiny bit, but the symbology is still very hard to see.)

Yea, this is right, thanks for the info, at least now I know exactly what to do to avoid this bug until it's fixed! Here's a video showing the issue @BIGNEWY-- It also highlights how annoying Auto Track is to use in DCS (not even trying to make this difficult on purpose lol, it just won't track, or tries to track the ground here's a video displaying the ATFLIR point track -- hopefully the new FLIR model will help not targeting the road, although you can see the way point track is acquired in DCS is different. There is a growing acquisition box)

In the track I'm pretty sure I showed the maverick failing to point in the correct direction throughout the entire attack. Ill make another track in a bit. Maybe it's fixed on your internal version.

The ATFLIR while in point track does not update its target designation. For example, if a target is moving 10 meters/second and you point track that target at position A, then you slave your maverick to the FLIR 20 seconds later, the target has moved 200 meters, and your maverick will slew to the original point, not the current point, so it will be 200 meters inaccurate. This seemed like a AGM-65F bug initially, but the AGM-65E will in fact "work" (sort of) The AGM-65E will slew to the same incorrect target point that is behind the moving target, however, when you fire the laser it will correct itself to the correct point. It seems the ATFLIR is not updating its target designation like it should, but it does update its laser to the correct position. Track attached. MovingTGT.trk

Don't fly for the 3 wire, fly the ball. Also, which wire you trap has no bearing on how good a trap was, the 3 wire is just your target, but you could still trap a 3 wire with a poor pass, or trap even potentially a 1 wire with an acceptable pass. Personally I've never had issues with the IFLOLS, although the platcam I believe is about a ball low.

100% There's a lot missing, I just meant to identify a single big piece I feel is very important.