Unlock on TWS

[...]

For those who do not speak English and translating the Hornet manual is the double challenge of translating and understanding ... Does anyone know how to unblock a blocked contact in TWS? The only thing that works for me is to go back to RWS and press TDC. Sometimes it gets annoying, especially when you've already shot down a target and the lock is on. Thanks in advance.

[noisy_lightning]

Press Rset on the right side OSB (Fourth down I think but can't remember exactly).

 

Sent from my SM-G986B using Tapatalk

[...]

Press Rset on the right side OSB (Fourth down I think but can't remember exactly).

 

Sent from my SM-G986B using Tapatalk

 

 

Reset has never worked for me with TWS. I will try again.

Edited July 20, 2020 by La Unión | Atazar

[...]

https://www.youtube.com/watch?v=kGdaIDKPpm0&feature=youtu.be

 

I confirm that RESET does not work at this time.

 

I am seeing this issue unsettle more people and we have not yet received an official response beyond impromptu solutions like changing weapons or switching to RWS. Reset should erase all contacts but as they say in this thread, it doesn't always work.

 

https://forums.eagle.ru/showthread.php?t=261593

 

It is also surprising that after landing, with the radar in standby, the radar has blocked one of the components of my wing, on the ground and with the engine off.

 

https://www.youtube.com/watch?v=9la-0zkb9ps&feature=youtu.be

Edited July 19, 2020 by La Unión | Atazar

[Swift.]

AFAIK, TWS will always have L&S shown. If you don't want to see those, then don't use TWS.

[...]

This is my standard configuration for CAP operations.

 

 

[ATTACH]242853[/ATTACH]

[...]

Since I have already posted several questions, I can add another. Do we know if the sensor control switch depress function will be implemented to identify in TWS? Until now and since its implementation, all contacts are shown as unknown.

 

 

EDIT: [No error] This works. Initially it did not work but has been implementing at some point.

Edited July 21, 2020 by La Unión | Atazar

[Swift.]

Since I have already posted several questions, I can add another. Do we know if the sensor control switch depress function will be implemented to identify in TWS? Until now and since its implementation, all contacts are shown as unknown.

 

I admit I haven't used TWS all that much, but I'm still fairly certain IFF works with TWS. Just to verify, you are turning your IFF on right?

[falcon_120]

Since I have already posted several questions, I can add another. Do we know if the sensor control switch depress function will be implemented to identify in TWS? Until now and since its implementation, all contacts are shown as unknown.

Iff works with TWS, you need to put the TDC over the target and press the Iff button, which is TDC depress or recce mark?

I will look the exact name and tell you.

 

Enviado desde mi ELE-L29 mediante Tapatalk

[Tholozor]

IFF interrogation is performed with Sensor Control Switch Depress.

[felixx75]

IFF interrogation is performed with Sensor Control Switch Depress.

 

This, and it works fine.

(In RWS just hover over the contact)

[Ramsay]

For those who do not speak English and translating the Hornet manual is the double challenge of translating and understanding ... Does anyone know how to unblock a blocked contact in TWS? The only thing that works for me is to go back to RWS and press TDC. Sometimes it gets annoying, especially when you've already shot down a target and the lock is on. Thanks in advance.

 

I haven't found a quick way to unlock a target in TWS* but NWS/undesignate allows you to quickly step to the next target in the HUD / priority list (even if it's not DT2).

 

*TWS seems to want to autolock whatever is in front of it.

 

IIRC you used to be able to put the TDC over a contact and use NWS/undesignate but that doesn't seem to work now, so perhaps I've misremembered or something has changed.

 

Tested with an E3 + 2 x Hornet escort @ 25,000 ft in open beta 2.5.6.52196

[Harker]

Upon pressing RESET, TWS should designate the highest ranked trackfile as L&S. Then, pressing the NWA/Undesignate button will cycle through the rest of the displayed trackfiles, in order of threat ranking.

[...]

Okay, so the answer is that it is not possible to deselect a lock. I just wanted to know that to rule out that it was a mistake or that I was doing something wrong. The rest of the options I already knew, an undesignate (s) to change objectives, etc. In this sense I have already obtained an answer. As for the IFF issue, I know I can identify by putting the designator over the contact, but this doesn't show a diamond in the HUD like in RWS.

[...]

This, and it works fine.

(In RWS just hover over the contact)

 

 

Thanks, I know it works in RWS, but I mean the IFF in TWS.

[Bunny Clark]

In TWS there will always be a primary L&S target designated, and you can manually designate a DT2 if you want, but it's not possible to completely deselect a target. TWS is an attack mode, there's no reason not to have a designated target. Now, that said, there are bugs in DCS now that make it more difficult to undesignate a target at other times. I believe you should be able to completely undesignate all targets in RWS, even with LTWS enabled, but that sometimes doesn't work. Also, the ability to track and designate targets with the radar off or when on the ground is definitely a bug.

 

The Hornet requires two separate methods of ID to mark a target as hostile. Typically this is a lack of IFF response and hostile ID from surveillance datalink. If you're operating without an AWACS then the second method needs to be NCTR, which does not work in TWS. It's possible there's a datalink correlation bug in TWS, I haven't noticed, but I don't use TWS a lot. Or if you're operating alone then a STT track will be able to set a hostile ID but TWS will not. You can also manually set a target ID using the PID function on the SA page.

Edited July 19, 2020 by Bunny Clark

[falcon_120]

In TWS there will always be a primary L&S target designated, and you can manually designate a DT2 if you want, but it's not possible to completely deselect a target. TWS is an attack mode, there's no reason not to have a designated target. Now, that said, there are bugs in DCS now that make it more difficult to undesignate a target at other times. I believe you should be able to completely undesignate all targets in RWS, even with LTWS enabled, but that sometimes doesn't work. Also, the ability to track and designate targets with the radar off or when on the ground is definitely a bug.

 

The Hornet requires two separate methods of ID to mark a target as hostile. Typically this is a lack of IFF response and hostile ID from surveillance datalink. If you're operating without an AWACS then the second method needs to be NCTR, which does not work in TWS. It's possible there's a datalink correlation bug in TWS, I haven't noticed, but I don't use TWS a lot. Or if you're operating alone then a STT track will be able to set a hostile ID but TWS will not. You can also manually set a target ID using the PID function on the SA page.

Exactly, probably the cause is either is a mission where you are the only source for the interrogation. To the OP, If you add an awacs to the mission you'll see iff working just fine.

 

Enviado desde mi ELE-L29 mediante Tapatalk

[Tholozor]

Thanks, I know it works in RWS, but I mean the IFF in TWS.

 

IFF interrogation is the same in RWS and TWS. Put the cursor over a contact and SCS Depress.

[dundun92]

I have found a sort of "workaround" to unlock a target, just move the radar scan cone off the target, and wait till it fades (e.g, by setting the elevation to the upper/lower extremes, or move the scan zone left/right). After it drops the lock you can then set the scan volume back to normal

[Al-Azraq]

But there's no point undesignating targets as it is not a hard lock and the locked target does not receive a RWR warning. I always have targets soft locked while in RWS and TWS for more situational awareness and you should be used to the same.

[...]

But there's no point undesignating targets as it is not a hard lock and the locked target does not receive a RWR warning. I always have targets soft locked while in RWS and TWS for more situational awareness and you should be used to the same.

 

Yes I agree. In addition, the radar configuration that I usually use is very strict and allows to attack and evade without losing the blockade, even at more than 90 degrees between mountains to be able to retake the initiative. In that sense, it makes sense for a contact to stay on your radar as pasted.

 

Forgive my English, I use Google Translate.

Edited July 20, 2020 by La Unión | Atazar

[...]

IFF interrogation is the same in RWS and TWS. Put the cursor over a contact and SCS Depress.

 

 

I would appreciate a short video or a hint where you show HUD showing you a diamond by asking questions on TWS.

[Hardcard]

But there's no point undesignating targets as it is not a hard lock and the locked target does not receive a RWR warning.

 

TWS autolock is a pretty bad idea for several reasons:

 

- Increases the chance of blue on blue

Imagine that you have an enemy contact ahead, as well as some friendlies around (within radar cone).

Those friendly contacts are provided by AWACS, you don't IFF because you already know they're friendlies (you also have comms confirmation or whatever) and also because that bandit is about to fox, so there's no time to lose.

But just when you're about to fox, bandit fades and TWS autolocks one of the friendlies that you didn't IFF (because there was no need to)... by the time you realize what's going on, it's too late.

 

- Tends to autolock bandits you're not interested in

 

- It's annoying af

Edited July 20, 2020 by Hardcard

[falcon_120]

I would appreciate a short video or a hint where you show HUD showing you a diamond by asking questions on TWS.

 

Atazar, as said previously, in order for you to see a diamond in the hud, you need at least 2 donors declaring the bogey as a bandit. So for example you need at least, your own interrogation plus an awacs or another friendly aircraft that interrogates the bogey.

 

Are you sure you dont get a diamond in TWS after the iff interrogation IF there is an awacs in the mission?

[kengou]

TWS autolock is a pretty bad idea for several reasons:

 

- Increases the chance of blue on blue

Imagine that you have an enemy contact ahead, as well as some friendlies around (within radar cone).

Those friendly contacts are provided by AWACS, you don't IFF because you already know they're friendlies (you also have comms confirmation or whatever) and also because that bandit is about to fox, so there's no time to lose.

But just when you're about to fox, bandit fades and TWS autolocks one of the friendlies that you didn't IFF (because there was no need to)... by the time you realize what's going on, it's too late.

 

- Tends to autolock bandits you're not interested in

 

- It's annoying af

 

 

Never going to happen with correct tactics. Airspace should be sanitized and bandits sorted before any attack takes place. Friendlies shouldn't be in proximity and at same altitude as bandits or you run the risk of AMRAAMs going active on friendlies, so you're not going to launch in that situation anyway. In such a situation with no time to lose, you go into STT lock.