TWS second target bugging sometimes not working?

[TomCatMucDe]

is it only me or sometimes you cant bug the second target in TWS?

 

I see the issue relatively often, both targets are within the scan azimuth and elevation limits.

 

If I unlock the first target, I can bug the second target as primary

[Gnadentod]

If I unlock the first target, I can bug the second target as primary

This is how it should be.

[TomCatMucDe]

This is how it should be.

Of course not. I think you didn't understand my post. I can't bug the second target manually by placing the TDC over it and hit TMS up. If you think that's wrong, you should read about TWS or watch wags video on YouTube.

 

Sent from my SM-G975F using Tapatalk

[Gnadentod]

You yourself said in the first post that if you unbug the first target you can make the second target the PRIMARY. When there are two targets only then you can't have both targets primary, otherwise the terms primary and secondary wouldn't even make sense in this situation, hence the whole reason why you would bug a target would make no sense. Your wording and its underlying logic isn't even correct.

 

You can only designate one target as primary, which is called the bugged target. If you could bug two or even more targets then you would really designate neither of them for the AIM 120, there would be no primary target.

Edited December 26, 2019 by Der Hirte

[TomCatMucDe]

You yourself said in the first post that if you unbug the first target you can make the second target the PRIMARY. When there are two targets only then you can't have both targets primary, otherwise the terms primary and secondary wouldn't even make sense in this situation, hence the whole reason why you would bug a target would make no sense. Your wording and its underlying logic isn't even correct.

 

You can only designate one target as primary, which is called the bugged target. If you could bug two or even more targets then you would really designate neither of them for the AIM 120, there would be no primary target.

Ah I see what you mean, I think you misunderstood me. My point is once I have a primary bugged, sometimes I can't bug a secondary at all, TMS Up on him does nothing.

To make sure that the second target is actually correctly seen, I unbug the primary and try to bug the second target, that indeed works, he becomes primary. So he is "buggable". It's only a test somehow.

 

Sent from my SM-G975F using Tapatalk

[Gnadentod]

.... No, you misunderstood me and how the TWS works aswell, not the other way around. Atleast you tried I'd say.

[TomCatMucDe]

.... No, you misunderstood me and how the TWS works aswell, not the other way around. Atleast you tried I'd say.

Just don't be stubborn.

 

I know how TWS works, I used it for years BMS and I used it for a couple of weeks in DCS. However sometimes, I can't get to bug the secondary Target and can't designate him. Most of the time it does work.

 

Thank you for your contribution nevertheless.

 

 

Sent from my SM-G975F using Tapatalk

[Gnadentod]

You still don't get it and even better is the fact that you project your failure to admit understanding it wrong as me being "stubborn". Very cheap and weak. I'm out. Get over it.

[TomCatMucDe]

You still don't get it and even better is the fact that you project your failure to admit understanding it wrong as me being "stubborn". Very cheap and weak. I'm out. Get over it.

Thanks. Bye

 

Sent from my SM-G975F using Tapatalk

[TomCatMucDe]

To the other forum users, let me clarify my post:

 

Does it happen to you to fail to upgrade a second track file to a system target once you have one already system target?

 

Sent from my SM-G975F using Tapatalk

[Gnadentod]

Nice rewording of your post, let the back-paddling begin - after you tried to put others in a negative light :D

[TomCatMucDe]

Nice rewording of your post, let the back-paddling begin - after you tried to put others in a negative light :D

What rewording ?

 

Sent from my SM-G975F using Tapatalk

[Gnadentod]

What rewording ?

 

Sent from my SM-G975F using Tapatalk

Bugged Target in your initial post -> System target in your rewording post, after admitting to yourself I was right but don't want to admit it in written words, especially after putting me in a negative light. Enough for here, the posts speak for themselves now. Over and out.

[TomCatMucDe]

Bugged Target in your initial post -> System target in your rewording post, after admitting to yourself I was right but don't want to admit it in written words, especially after putting me in a negative light. Enough for here, the posts speak for themselves now. Over and out.

You really don't get it...

 

Sometimes, I can't have a second system target and therefore I can't bug him. When this issue occurs I have only one system target that I can designate, the other remains a track file that is not buggable. I can TMS up on him and he would never become a system file to be bugged.

 

Your contribution was not helping. Thanks and bye.

 

Sent from my SM-G975F using Tapatalk

[Gnadentod]

Your contribution was not helping. Thanks and bye.

You usually won't get help in whatever it is in life if you can't articulate yourself properly. Nice try.

[TomCatMucDe]

You usually won't get help in whatever it is in life if you can't articulate yourself properly. Nice try.

You are polluting the thread. You said twice that you were leaving ...

 

Sent from my SM-G975F using Tapatalk

[NeMoGas]

The issues I have are related to the fact that most the track files appear as correlated hostile DL indications and it is impossible to visually see if they are selected as a system track file. When you TDC over them and press TMS up it does not always set it as a system file. The only way I can tell it has worked is to watch the radar azimuth limit lines center around that track (it seems the cursor must be perfectly over the track or it won't work). Then I can use TMS right to cycle the bugged target. Also you can't set a new track file as a system file while you already have another track set as the bugged contact. Not sure if that is real or a DCSism, just that it seems to work like that for me.

Edited December 26, 2019 by NeMoGas

[Mikeck]

You usually won't get help in whatever it is in life if you can't articulate yourself properly. Nice try.

 

Man....let it go already. You’re smart. We get it.

Let him ask the question in peace.

[Gnadentod]

Man....let it go already. You’re smart. We get it.

Let him ask the question in peace.

Yes. "Yeah just let him put you in a negative light while you actually answered his question when it was him not being able to articulate himself properly, then getting butthurt about it." Muh feelings. Nope, not gonna happen.

[Wicked.-]

You need to see a white dot in both red contacts. That lets you know your radar sees the target. If they’ve split and bracketed vertically, or one has notched, the radar has lost sight of the contact. There’s nothing you can do but monitor the radar and see if the second target pops back up with the white dot. There’s a lot going on visually on the radar with L16 active. With the current behavior of the radar I begin trying to get contacts twizzed up around 40 miles. Keep in mind you’re also limited in azimuth in TWS. If they’re pop up contacts inside of 20 miles don’t bother with TWS.

 

If you have two close contacts that have the white dot, TMS up ONCE on each which should make them solid red. Once that is done TMS right to bug one and then TMS again to swap the bugged contact.

Edited December 27, 2019 by Wicked.-

[Deano87]

Yes. "Yeah just let him put you in a negative light while you actually answered his question when it was him not being able to articulate himself properly, then getting butthurt about it." Muh feelings. Nope, not gonna happen.

 

Regardless of if you were correct in the initial discussion or not, you are acting like an ass now.

[TomCatMucDe]

You need to see a white dot in both red contacts. That lets you know your radar sees the target. If they’ve split and bracketed vertically, or one has notched, the radar has lost sight of the contact. There’s nothing you can do but monitor the radar and see if the second target pops back up with the white dot. There’s a lot going on visually on the radar with L16 active. With the current behavior of the radar I begin trying to get contacts twizzed up around 40 miles. Keep in mind you’re also limited in azimuth in TWS. If they’re pop up contacts inside of 20 miles don’t bother with TWS.

 

If you have two close contacts that have the white dot, TMS up ONCE on each which should make them solid red. Once that is done TMS right to bug one and then TMS again to swap the bugged contact.

Thanks Wicked!

I have the impression is that sometimes I can't get the second contact to be fully red (system file) I'll test again if I still see the issue. Yesterday it didn't happen again.

 

Sent from my SM-G975F using Tapatalk

[TomCatMucDe]

Yes. "Yeah just let him put you in a negative light while you actually answered his question when it was him not being able to articulate himself properly, then getting butthurt about it." Muh feelings. Nope, not gonna happen.

Nah, I don't get butthurt on forums :) you are again derailing the thread. Ciao.

 

Sent from my SM-G975F using Tapatalk