reported Cannot Lock Anything with TDC Depress After Update

[percivaldanvers]

no lock.trk

Hello all,
Today I was running a dogfight I often do with the Hornet. It's actually the 2v2 DACT training mission from the F-14 instant action folder with the Hornet swapped in for the Tomcat. I was not able to lock anything with TDC depress. I checked my bindings to make sure it was still there and it was. I checked the patch notes for indication that the process of locking targets with the Hornet radar has changed, and to my understanding nothing involving what I was doing has changed, so I thought I'd drop this track here and see if I am indeed doing something wrong or if the process has changed in a way I didn't understand. 

[PD919]

Same issue here

[Muchocracker]

been using TDC depress today with no issues. What map is this the trk doesnt appear for me in the replay list. 

[gialo87]

Same issue 

[Ethanol Enthusiast]

I also have this issue and so does a friend.

[minhnguyen404503]

Hi, I think I found something noteworthy, can be reproduce consistently and can point to the source of the bug:

• In RWS
  • LTWS on: TDC Depress can bug a target to L&S as long as the radar doesn't detect the target (no raw brick). As soon as the radar detects it with the raw brick on top of the MSI track, TDC Depress will do nothing. This is recorded in my attached track.
  • LTWS off: TDC Depress on raw brick with no LTWS won't do anything (sorry forgot to record this in the track).
• In TWS: Bugging MSI only tracks and radar tracks work properly

Current workaround for RWS is to use SCS Right when the cursor is on top of a raw brick, but it's finicky since it can STT a different target (highest priority) instead if the raw brick timed out.

msi-bugged-in-rws.trk

[percivaldanvers]

13 hours ago, Muchocracker said:

been using TDC depress today with no issues. What map is this the trk doesnt appear for me in the replay list. 

Should be Normandy. 

[Muchocracker]

Observed in your track and reproduced in my own. Internal reports made. FACQ seems to work okay and will command STT on TUC's so i would reccomend using that for now or TWS until fixed.

For future reference please make tracks in caucasus. That is the preferred map for the devs to use for debugging. 

Edited August 14 by Muchocracker

[BIGNEWY]

This has been reported internally

[Akula]

THIS IS WHAT I USED TO DO BUT NO LONGER WORKS
 

In a mission with three bandits and me with 6 aim120c I can usually target all three jets and fire on them consecutively. This is how I used to do it 

select TWS mode

set to AUTO

let the lead jet get automatically locked in TWS and let the track file populate.

At 80 miles i back out of radar and select “ANZEL” and the “AUTO”

Back to radar 

select EXP to expand the view.

select RAID

from there I can press “S” to toggle through the targets in TWS and fire at will. 

That method no longer works. When I set it all up similarly, pressing “S” doesn’t toggle to the other contacts. Just stays locked on the lead jet. 
with the way it is now I manually have to fire on the lead, break lock, lock up no. 2 and repeat for the third jet.

I’m pretty sure this is broken unless the procedure has changed. 

[SMN]

FA-18C  Cannot Lock target with TDC Depress in RWS mode.

RW SCS Right - locked to STT

TWS - locked..

Edited yesterday at 11:56 AM by SMN

[NoJoy]

Corresponding to that one?

 

[SMN]

20 минут назад, NoJoy сказал:

Corresponding to that one

Yeah, it looks like

[wilbur81]

Right now, the Hornet's radar is in a bad way for any significant air to air employment. In addition to this OP, you can no longer step through TWS priority tracks either. All-reported, but probably serious enough that it should've warranted a no-release for this MSI improvement...or a quick hot fix. They'll get to it.