need track replay TWS undes locking tgt outside reasonable RDR FOV.

[DUSTY]

Not sure if related to the recent bar scan issues but on a SP flight recently I selected undesignate while in TWS and the radar managed to lock a target way outside of the radar FOV:

 

 

 

 

 

I'll try and get a nice concise track file of it when I can.

[Padonis]

This has long been the case, TWS mode does wonders. Look at the video, the radar catches the target behind me, which should no longer be visible through the radar.

 

[Santi871]

Need tracks, please

[Yoshua]

This has been a issue for a while. I was in the hornet last night and was on the ground with my radar in silent and was pressing the undesignate button and was switching between targets at 50 to 100 miles.

[Hulkbust44]

No issue here. Track file is being remembered by the computer and can still be designated in that time. As you turn around the radar is able to extrapolate the track as it picks up the target again.

[MARLAN_]

While MSI isn't fully implemented in DCS, in the future when it is, you WILL be able to designate tracks that are not inside your radar scan volume.

Also note, designating an L&S is NOT a lock.

[Mikaa]

11 hours ago, MARLAN_ said:

While MSI isn't fully implemented in DCS, in the future when it is, you WILL be able to designate tracks that are not inside your radar scan volume.

Also note, designating an L&S is NOT a lock.

Quick tangent question. If an offboard only target is designated (let's say L16 from an AWACS), how is the transition handled from that L&S track to an onboard firing solution for an AIM-120? Is this handled in a pseudo AACQ once within radar scan volume or does it have to be manually designated again in RWS/TWS, but until then the L&S cues will give intercept symbology for the offboard linked track?

[MARLAN_]

1 hour ago, Mikaa said:

Quick tangent question. If an offboard only target is designated (let's say L16 from an AWACS), how is the transition handled from that L&S track to an onboard firing solution for an AIM-120? Is this handled in a pseudo AACQ once within radar scan volume or does it have to be manually designated again in RWS/TWS, but until then the L&S cues will give intercept symbology for the offboard linked track?

As far as I'm aware, you can launch on an offboard track file - you wouldn't even need radar contribution and could bridge that offboard information from L16 through your aircraft, transmit through your radar, to the missile - albeit with a lower data rate than with radar contribution. The target could even be launched on outside of your radar gimbal limits (thus totally unsupported after launch) and be able to fly to last known intercept, like how in DCS if you lose radar contribution after launch.

I'm not quite sure what you're asking with AACQ - if the track was designated as an L&S and is not inside your scan volume, but is inside your radar gimbal limits and you command FACQ or AACQ (SCS right) your radar would command STT about the L&S, if you were in TWS AUTO, your radar would automatically slew towards the L&S (and if it was outside radar gimbal limits it would move towards that side of the radar until the track entered your radar gimbal limits)

[Swift.]

Yeah as Marlan described, it would start as a bottom HAFU with the L&S symbol to show that you have an offboard only track as the L&S:

Then when the radar begins to contribute (aka when the radar can 'see' the aircraft) you will see a radar contribution circle appear and the top HAFU appear:

It will still keep the L&S star and still keep the bottom HAFU because its still the L&S and there are still offboard contributors. And then if you wanted a better quality radar contribution, ie going to STT from RWS, then you could command STT on the L&S by castling into the radar display with TDC priority already assigned, or by cursoring over the L&S and depressing TDC. But the HAFU wouldn't change.

 

Edited January 18, 2022 by Swiftwin9s

[Mikaa]

I didn’t realize you could have guided intercept with entirely off board contribution, but that makes sense.

My question was really about if the onboard radar has an easy way of taking the off board track designation and easily acquiring it with your onboard radar without much (read any) pilot input (ie the radar snaps to the L&S track without having to manually slew and train elevation). Of course you can manually cursor slew over it and designate yourself once it shows that your radar is also contributing. 
 

Being able to launch off a donor only track makes my question a bit moot anyways. 

 

Thanks! 
 

[Harker]

1 hour ago, Mikaa said:

I didn’t realize you could have guided intercept with entirely off board contribution, but that makes sense.

My question was really about if the onboard radar has an easy way of taking the off board track designation and easily acquiring it with your onboard radar without much (read any) pilot input (ie the radar snaps to the L&S track without having to manually slew and train elevation). Of course you can manually cursor slew over it and designate yourself once it shows that your radar is also contributing. 
 

Being able to launch off a donor only track makes my question a bit moot anyways. 

 

Thanks! 
 

Not exactly, but there are ways of quickly looking for a contact with the radar. You can make the MSI track the L&S and then enter TWS AUTO: the radar will prioritize the L&S in its search pattern, likely finding it quickly. Or you can attempt an acquisition with FastACQ, using SCS->RDR ATTK page: the radar will enter a mini-raster scan and attempt to acquire the target, transitioning to STT if it does.

The thing with MSI, is that an MSI trackfile can be created by several different inputs and the radar is only one of them (the most important one, but still, only one). The radar works with and considers MSI trackfiles, not necessarily only the ones coming from itself. In DCS right now, we just have datalink, but not really MSI.

Edited January 19, 2022 by Harker