TWS mode

[71st_Mastiff]

I can bug each target but to get the 120c's to lock each one separate seems to be an issue, also

 

For some reason when 120c reach there max they lose there max just before the medium range and then it goes out and doesn't come back until short range?:thumbup:

[GGTharos]

I don't know what you're saying. English please, or some language that google can translate please! :P

[blkspade]

I think he's referring to the DLZ indication, and Rmax. If so, then he doesn't grasp the fact its dependent upon aspect and what the target is doing.

[71st_Mastiff]

I think he's referring to the DLZ indication, and Rmax. If so, then he doesn't grasp the fact its dependent upon aspect and what the target is doing.

 

targets are straight in front of me. I made a mission and have the targets flying one straight pattern.

 

when I bug up to 4 targets #1, #2, #3, #4, I launch 1,2,3,4 120c respectively and none of them track..

 

the long range max disappears after I catch up a couple of miles but does not reappear until it hits medium max, then after a couple miles I catch up to the target it unlocks or disappears, and doesn't reacquire lock until short range-max. :joystick:

 

ill post a track as soon as I awake and run it again, for some reason theres no track..

[kirk7312]

I have same problem as well.

TWS mode, locked 3 targets, lunched 3 AIM-120s in perfect range

But NO 120 tracked the target. they lost targets totally.

[Kenan]

You can bug more then 2 targets? :D

[Ironhand]

I think what's happening is that, even though the bugged targets are still within the radar's scan zone (according to the VSD), some targets simply disappear. Yet, if you shift the scan zone to the right or left a bit, they immediately reappear. Problem is, the 30 degree scan zone can't be shifted right or left at will. Something is interfering. It's not until only one target is on the VSD that I have control of the right-left movement again after bugging targets. Ran into that this morning. I unthinkingly didn't save the track. Don't know if that's how the scan zone control is supposed to work or not but it's definitely different than it had been.

 

 

Rich

[71st_Mastiff]

heres a track loss

 

heres a track I did this morning, gain contact, then loose contact I have 4 separate il76m's different heights, and one friendly German tornado contact.

 

Also I see a problem with il76m when I have 2 in one package their on top of each-other when they spawn. So I had to make them single package. :thumbup:

[Ironhand]

heres a track I did this morning, gain contact, then loose contact I have 4 separate il76m's different heights, and one friendly German tornado contact.

 

Also I see a problem with il76m when I have 2 in one package their on top of each-other when they spawn. So I had to make them single package. :thumbup:

Hopefully I'll have time to download and view the track later this afternoon. If I hadn't seen what I saw this morning during my flight, I would have assumed that they simply flew above or below the radar scan cone as the range closed.

 

 

Rich

[Vortex225]

I haven't noticed any problems with TWS, and I've used 120Cs several times in this mode recently. I'll do some tests later today to see if I can generate any inconsistencies.

[Евгений.]

Hello friends! I have one question about TEWS on F-15c. Where i can find the document, where I can find the document in which threat and radiation symbols are described?

[GGTharos]

The document for the TEWS in-game? It should in the in-game manual.

[Ironhand]

heres a track I did this morning, gain contact, then loose contact I have 4 separate il76m's different heights, and one friendly German tornado contact.

 

Also I see a problem with il76m when I have 2 in one package their on top of each-other when they spawn. So I had to make them single package. :thumbup:

I didn't have time to watch the entire encounter but the first two targets disappeared because they flew under your radar scan as the range closed. I believe the same was true for the friendly, though I wasn't keeping as close an eye on him. Had to stop viewing and get back to work before the track played out completely. Hopefully I'll have time to review it in more detail tomorrow.

 

 

Rich

[Ironhand]

Watched it a 2nd time this morning and, indeed, you keep losing the targets because you are allowing them to fly under your radar. Keep in mind that the upper and lower limits of your radar that you see displayed on the left side of the VSD are tied to the TDC's location. So, if you have it placed at 40 nm, you are getting a read on your radar's upper and lower limits at that range. If at 20 nm, then the limits you see are at the 20 nm range. Basically, you need to keep the TDC next to your intended targets (regardless of the range scale), if you want to know whether or not they are about to fly above or below your radar scan zone.

 

As a matter of practice, it's usually a good idea to place the TDC down in the DLZ at the range where you intend to launch and get a quick read on your radar's altitude limits for that range. Then you'll know in advance whether or not you'll need to raise or lower your radar's scan zone to maintain the contactall the way into the DLZ.

 

 

Rich

Edited December 8, 2012 by Ironhand

[71st_Mastiff]

thank you, but that doesn't explain the lock I have on some targets and get no launch light when there in range?

[Kuky]

thank you, but that doesn't explain the lock I have on some targets and get no launch light when there in range?

 

Double check you are not trying to use AIM-7 in TWS because for AIM-7 you need to have STT lock

[71st_Mastiff]

no they were all 120c's

[evilnate]

In my experience launching a 120C at max range is only effective against targets that are flying straight at you, and doesn't change direction after they detect your launch.

 

If you do launch a 120C at max range, and the target changes direction, you can kiss it good bye. The only advantage to firing one at max range is to try and make the enemy take evasive maneuvers.

 

For TWS (multi-launch) engagements, it is only effective if you launch very close to the enemy targets (pit-bull range).

[Ironhand]

thank you, but that doesn't explain the lock I have on some targets and get no launch light when there in range?

No it doesn't. And I apologize. I wasn't even looking for that. Just replayed your track and I don't even see a DLZ for the selected missile. I took control, reselected LRS, turned radar ON and locked a target (STT) and still failed to get a DLZ for the selected weapon (AIM-120B). Also no joy, when I attempted the same in TWS. Now I'm not sure if I was seeing a DLZ in my previous views or not. Sorry. Too much work and too little play. My brain is very fuzzy these days.

 

 

I haven't seen this happen in any missions I've flown. Is this happening elsewhere as well for you or only in this mission? I wonder if the mission is simply screwed up somehow.

 

 

Rich

[Cali]

In my experience launching a 120C at max range is only effective against targets that are flying straight at you, and doesn't change direction after they detect your launch.

 

If you do launch a 120C at max range, and the target changes direction, you can kiss it good bye. The only advantage to firing one at max range is to try and make the enemy take evasive maneuvers.

 

For TWS (multi-launch) engagements, it is only effective if you launch very close to the enemy targets (pit-bull range).

 

That's the goal is to make them go defensive, so you or a buddy can get closer. Did something change from FC2 to FC3 or you are not using TWS correctly, cause in FC2 it worked fine even at long range shots 20+ miles on different targets.

[71st_Mastiff]

No it doesn't. And I apologize. I wasn't even looking for that. Just replayed your track and I don't even see a DLZ for the selected missile. I took control, reselected LRS, turned radar ON and locked a target (STT) and still failed to get a DLZ for the selected weapon (AIM-120B). Also no joy, when I attempted the same in TWS. Now I'm not sure if I was seeing a DLZ in my previous views or not. Sorry. Too much work and too little play. My brain is very fuzzy these days.

 

 

I haven't seen this happen in any missions I've flown. Is this happening elsewhere as well for you or only in this mission? I wonder if the mission is simply screwed up somehow.

 

 

Rich

 

no it's a fresh one I made.. So it does happen to me most of the time 120b, and C's...:joystick:

[evilnate]

Did something change from FC2 to FC3 or you are not using TWS correctly, cause in FC2 it worked fine even at long range shots 20+ miles on different targets.

 

I have had little success in killing a 4 ship of AI controlled SU-27s with TWS at 20 miles in FC3.

[71st_Mastiff]

Do I have to turn on BVR mode in-order to launch at the TWS bugged targets, or can I remain hidden? :joystick:

[tflash]

No, normally you can launch an Amraam from TWS without going to STT mode; it will sequentially go through all the targets you bugged.

[159th_Viper]

or can I remain hidden? :joystick:

 

TWS is a BVR mode - you are transmitting loud and clear and will never be hidden. No EOS on the Budgie.