Jump to content

Recommended Posts

TWS-Auto

 

I think that is one of the issues that was fixed while implementing TWS-A, so it should be better for TWS-M too. Let us know how it goes!

 

 

 

04f05a48cf3742d758cc66be2a6bdd5b.jpg

 

 

 

Sent from my iPhone using Tapatalk Pro

Win 10, AMD FX9590/water cooled, 32GB RAM, 250GB SSD system, 1TB SSD (DCS installed), 2TB HD, Warthog HOTAS, MFG rudders, Track IR 5, LG Ultrawide, Logitech Speakers w/sub, Fans, Case, cell phone, wallet, keys.....printer

Link to post
Share on other sites

Not yet I'm afraid. At least no PH improvement was mentioned in the changelog and I didn't notice any difference in their behaviour with the new patch. TWS-A is very nice however

i5-8600k @4.9Ghz, 2080ti , 32GB@2666Mhz, 512GB SSD

Link to post
Share on other sites

Did anyone try it yet? Does jester select it automatically or should we command him?

FC3 | UH-1H | Mi-8MTV2 | A-10C II | F/A-18C | Ka-50 | F-14A/B | F-16CAH-64

Persian Gulf | Nevada | Syria | NS-430 | Supercarrier // Wishlist: C-130 | UH-60 | F-4E

 

Youtube

Z390 / i5 9400F / RTX3070 / 32 GB Ram / 500 gb SSD and 1 tb HDD // CH Fighterstick - MS FFB2 - TM Warthog Throttle and Stick - CH Pro Pedals - Trackir 4 and 5

Link to post
Share on other sites

you mean your own phoenix does that?

FC3 | UH-1H | Mi-8MTV2 | A-10C II | F/A-18C | Ka-50 | F-14A/B | F-16CAH-64

Persian Gulf | Nevada | Syria | NS-430 | Supercarrier // Wishlist: C-130 | UH-60 | F-4E

 

Youtube

Z390 / i5 9400F / RTX3070 / 32 GB Ram / 500 gb SSD and 1 tb HDD // CH Fighterstick - MS FFB2 - TM Warthog Throttle and Stick - CH Pro Pedals - Trackir 4 and 5

Link to post
Share on other sites

Can't confirm that. I regularly see bandits defending only when the missile goes active (at about 15nm distance). Maybe it goes before 15nm active if your radar looses lock. Didn't pay attention to that.

i5-8600k @4.9Ghz, 2080ti , 32GB@2666Mhz, 512GB SSD

Link to post
Share on other sites
Can't confirm that. I regularly see bandits defending only when the missile goes active (at about 15nm distance). Maybe it goes before 15nm active if your radar looses lock. Didn't pay attention to that.

 

I was wondering why my Phoenixes are so ineffective now.

 

Yep, checked it out a while back myself.

 

 

 

 

 

 

BTW, flew some training missions tonight using the TWS Auto, i am glad to report seam to have our teeth back now. No longer having to do trigonometry on side your head, while flying the plane, fighting the guy and dodging his missiles at the same time, all the time fumbling with the Jester menu. You can now do sorts of cool stuff, like going high, lofting then breaking off and cranking, going in bellow him. The locks seam more stable too, both hard and soft ones :thumbup:

 

Loving it so far. Can't wait to try how it works in MP environment. :pilotfly:


Edited by captain_dalan
  • Like 1

Current modules:

FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map......ah yes, forgot the Super Carrier! Shows you how often i fly these days....

 

Modules in waiting: F-14A, MiG-23, F-4U, F-8, Falklands Map

 

 

Wish list: South East Asia map, F-4J/N, A-6, F-15A/C, Su-27, Sea Harrier FRS.1, Mirage III, MiG-17.

Link to post
Share on other sites
Yep, checked it out a while back myself.

 

 

 

 

 

 

BTW, flew some training missions tonight using the TWS Auto, i am glad to report seam to have our teeth back now. No longer having to do trigonometry on side your head, while flying the plane, fighting the guy and dodging his missiles at the same time, all the time fumbling with the Jester menu. You can now do sorts of cool stuff, like going high, lofting then breaking off and cranking, going in bellow him. The locks seam more stable too, both hard and soft ones :thumbup:

 

Loving it so far. Can't wait to try how it works in MP environment. :pilotfly:

 

Haven’t played with the new Jester menu/bindings yet, that sounds interesting to investigate.

 

Meanwhile I find that my radar likes to confuse bandit with my own missiles. For example the radar picture started with an IFFed target, which I fire at:

->

Then as he dodged that missile and the missile flew past him, the radar screen becomes

-] <———

Namely, the IFF status got transferred into my missile and soon after that, the true target disappeared altogether. Though it might be explained by enemy notching, but if that’s the case, should I lose him earlier, before my missile flew past him? Is this the correct behavior? Sorry I rarely do BVRs so maybe I’m missing something trivial here.

Link to post
Share on other sites
I think that is one of the issues that was fixed while implementing TWS-A, so it should be better for TWS-M too. Let us know how it goes!

 

 

If it's the same issue reported here: https://forums.eagle.ru/showthread.php?t=260806

 

 

Then it's not fixed yet and I and the group I fly with are still having the same problem. We're still trying to narrow down what exactly causes the TWS track loss, as it's not 100% consistent, but it does seem to mostly happen in Multiplayer.

Link to post
Share on other sites

 

Meanwhile I find that my radar likes to confuse bandit with my own missiles. For example the radar picture started with an IFFed target, which I fire at:

->

Then as he dodged that missile and the missile flew past him, the radar screen becomes

-] <———

Namely, the IFF status got transferred into my missile and soon after that, the true target disappeared altogether. Though it might be explained by enemy notching, but if that’s the case, should I lose him earlier, before my missile flew past him? Is this the correct behavior? Sorry I rarely do BVRs so maybe I’m missing something trivial here.

 

That is weird. have you told Jester to scan in TWS only? Sometimes when the lock drops, even for a second, he switches to RWS, loses IFF, and then switches to TWS again, only after reacquiring the target, then proceeding to IFF it again. This can take as much as 4-5s at times. An eternity when merging or being shot at.

Current modules:

FC3, Mirage 2000C, Harrier AV-8B NA, F-5, AJS-37 Viggen, F-14B, Combined Arms, F/A-18C, F-16C, MiG-19P, F-86, FW-190A, Spitfire Mk IX, UH-1 Huey, Su-25, P-51PD, Caucasus map, Nevada map, Persian Gulf map......ah yes, forgot the Super Carrier! Shows you how often i fly these days....

 

Modules in waiting: F-14A, MiG-23, F-4U, F-8, Falklands Map

 

 

Wish list: South East Asia map, F-4J/N, A-6, F-15A/C, Su-27, Sea Harrier FRS.1, Mirage III, MiG-17.

Link to post
Share on other sites
If it's the same issue reported here: https://forums.eagle.ru/showthread.php?t=260806

 

 

Then it's not fixed yet and I and the group I fly with are still having the same problem. We're still trying to narrow down what exactly causes the TWS track loss, as it's not 100% consistent, but it does seem to mostly happen in Multiplayer.

 

 

 

 

Can confirm this. This odd behavior is still there. In MP I just had a horrible sortie with ghost contacts appearing and TWS constantly losing lock even as the target was flying straight towards and above me without any maneuvering. Can't provide the track though, it is way too large. But there is something wrong. Heatblur needs to take a closer look at this.

Link to post
Share on other sites
That is weird. have you told Jester to scan in TWS only? Sometimes when the lock drops, even for a second, he switches to RWS, loses IFF, and then switches to TWS again, only after reacquiring the target, then proceeding to IFF it again. This can take as much as 4-5s at times. An eternity when merging or being shot at.

 

That doesn’t sound like the case because I was monitoring the radar picture the entire time. I’m wondering if it’s possible that I have lost the track 5-10 seconds before it disappeared but the radar is interpolating the contact position based on history information. I’m not sure how F14 handles lost contact in TWS mode, does it disappear immediately from the TID? What about the missile guidance in case of a lost contact?

Link to post
Share on other sites

I never noticed Jester scanning off the side before, but did notice this in MP Aerobatics.

F-14B; F/A-18C; A4E mod; FC3 (F-15C, SU-27); SU-57 mod | Syria; NTTR; PG | Supercarrier

---

Specs & Wishlist:

 

 

Core i9 9900k 5.0Ghz, Asus ROG Maximus Xi Hero, 32GB G.Skill Trident 3200, Asus RoG Strix 2070 OC, 1TB x Samsung Evo 970 M.2 boot. Samsung Evo 860 storage, Coolermaster H500M, ML360R AIO

 

Samsung Odyssey+ WMR HMD; VKB Gunfighter 2 with MCG Pro + T-rudder Mk IV; Virpil T-50CM v3

 

Wishlist:

AC: F-14D, YF-23, F-4S, MiG-35, MiG-29K

Maps: Miramar, Vietnam, MiG Alley, Midway

 

 

Link to post
Share on other sites
  • 2 weeks later...
we noticed some issue with TWS auto where it doesnt track the manattacked bandit and prioritized others. i will try to bring up track files next time i notice it

There are already thourough reports and dev responses here:

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

Will be fixed in the next beta update.

🖥️ i3-10100F 3.6-4.3GHz, 16GB DDR4 2666, GTX970 4GB, SSD SATA3, 27" LCD FullHD, Win 10 Home 64   🕹️ T16000M HOTAS, customTiR   ✈️ FC3, F-14A/B   🌍 NTTR, PG   🚢 Supercarrier

Link to post
Share on other sites
  • 1 month later...

Shooting down AS-4 anti-ship missiles works really well now with TWS-A. I had good successes with being at around 40'000 ft and mach 1.5-ish, obviously directly ahead in the path of the missiles. Order Jester to radar search at around 5° up-elevation. After giving Jester an elevation order remember to order him to use TWS again (even if he already is in TWS). This makes sure that TWS-A is active and automatic elevation control will take over as soon as the first missile is being tracked. Target elevation change rate will pick up very quickly as the mach 3 missiles approach at 80'000 ft, so you need to capture the first missile with TWS-A before it leaves the scan volume on top.

 

The first missile will be picked up at around 70 NM, upon which TWS-A will take over elevation control. Give it some seconds to pick up other missiles in the salvo and get tracks. At around 50 NM I start to ripple fire AIM-54. At around 20 NM I can see the dots of the AS-4 visually, just as the AIM-54 connect. Any AS-4 that is missed can be observed to pass overhead and is basically untouchable at this point.

 

This is all very satisfying and something that the Tomcat is all about.

Link to post
Share on other sites
  • 6 months later...
On 6/7/2020 at 4:27 PM, MBot said:

Shooting down AS-4 anti-ship missiles works really well now with TWS-A. I had good successes with being at around 40'000 ft and mach 1.5-ish, obviously directly ahead in the path of the missiles. Order Jester to radar search at around 5° up-elevation. After giving Jester an elevation order remember to order him to use TWS again (even if he already is in TWS). This makes sure that TWS-A is active and automatic elevation control will take over as soon as the first missile is being tracked. Target elevation change rate will pick up very quickly as the mach 3 missiles approach at 80'000 ft, so you need to capture the first missile with TWS-A before it leaves the scan volume on top.

 

The first missile will be picked up at around 70 NM, upon which TWS-A will take over elevation control. Give it some seconds to pick up other missiles in the salvo and get tracks. At around 50 NM I start to ripple fire AIM-54. At around 20 NM I can see the dots of the AS-4 visually, just as the AIM-54 connect. Any AS-4 that is missed can be observed to pass overhead and is basically untouchable at this point.

 

This is all very satisfying and something that the Tomcat is all about.

I read radar switch to TWS Auto automatically as soon as AIM-54 is fired even from TWS Manual radar mode.

Link to post
Share on other sites

I have a question, more related to the phoenix but in some way to the TWS-A.

 

Do i understand correctly that a AIM54 launched in TWS-A is autonomous when the TTI start flashing so i can now turn cold?

Or is that just an estimation but not directly couple to WCS go pitbul signal?

 

If its the second option is there a way to be sure when to turn cold? I'm assuming if i turn call before the pitbull command that missile will never go active right?

Link to post
Share on other sites
On 12/20/2020 at 5:35 AM, falcon_120 said:

I have a question, more related to the phoenix but in some way to the TWS-A.

 

Do i understand correctly that a AIM54 launched in TWS-A is autonomous when the TTI start flashing so i can now turn cold?

Or is that just an estimation but not directly couple to WCS go pitbul signal?

 

If its the second option is there a way to be sure when to turn cold? I'm assuming if i turn call before the pitbull command that missile will never go active right?

The blinking TTI indicates the Phoenix has gone active on that specific TWS track. You are clear to turn, since the Phoenix is active, but the Phoenix will fall back onto the AWG-9 if the TWS track is held the entire time the Phoenix is active. I’m not sure entirely, but the AIM-54C variant will go active if a TWS track is lost.

BreaKKer "Holdback"

CSG-2 - CVW-3

VF-154 Black Knights RIO
CSG-2 Website

 

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...