Feedback Thread - Tomcat Patch 24-12-24

[Sideburns]

Thank you, after a few sessions online the AWG9 TWS is once again usable in MP. The dropped tracks and whacky correlations were getting quite frustrating.

Edited December 27, 2024 by Sideburns

[Raven (Elysian Angel)]

The changes are definitely noticeable: I ran a quick test with the SoH BVR mission: before this patch when I launched 2 Phoenixes (yes under proper conditions) always 1 of those 2 would fail. This time both connected, even after heavy defensive manoeuvring of the 2nd MiG.

Edited December 27, 2024 by Raven (Elysian Angel)
typo

[Joch1955]

yes, did a bunch of the PG/Syria maps IA BVR missions and TWS AUTO has definitely improved. Pre-patch, when firing at two ACs, typically only one would hit. Post-patch, I am seeing a lot more 2 out 2 hits when using the same tactics.

[IronMike]

Glad to hear!

[RustBelt]

On 12/26/2024 at 5:51 AM, draconus said:

Really? He said: please.

ED and 3rd parties can manage to come up with changelog on time. HB always delays it somehow, some changes are not really there and now there's no changelog at all but it's cool to make excuses for them.

No you’re right, this is enterprise critical serious business here playing make pretend airplane. /s

[Spartan111sqn]

On 12/27/2024 at 3:54 PM, Joch1955 said:

yes, did a bunch of the PG/Syria maps IA BVR missions and TWS AUTO has definitely improved. Pre-patch, when firing at two ACs, typically only one would hit. Post-patch, I am seeing a lot more 2 out 2 hits when using the same tactics.

Can you ellaborate a bit more and indicate some parameters on the shots?, i.e.: your altitude and speed, distance from the bandit, and also altitude of the bandit.

 

Thanks in advance.

[Joch1955]

nothing fancy. IA missions spawn you at 25-30k with the AI coming straight on at the same altitude, so not much time for planning. I go into a climb in AB and track with tws auto. I fire at 25-30 miles distance or when I get a warning from the RIO that the AI is locking me and usually at 30-35k altitude. You won’t get hits all the time since the AI is very aggressive in trying to evade the missile.

[Koziolek]

On 12/24/2024 at 6:19 PM, IronMike said:

Thank you for your very kind patience, guys!

May you all get plenty presents!

Well,  I've got only one but it was F-14 module so I'm not complaining 

[Spurts]

Any one else getting a CTD when jumping into the F-14?  So far B on single player custom missions with plane set to client has crashed across several missions including ones made post update.

[Fear-Factor]

I am quite new in a F14 and so far i can hadle it in mp sessions but i am not sure if after the update something changed.....
My bind for dropping flares seems sometimes not to work and before the update it was fine.
And i have also a strange thing now that when i drop gbu12 so they are realeased pairwise.... do i need to change something now before dropping?
I am not sure about this both things because i fly the F14 for more than 3 months and this problems were not present.
So i assume something changed after this update?

[draconus]

4 hours ago, Fear-Factor said:

My bind for dropping flares seems sometimes not to work and before the update it was fine.
And i have also a strange thing now that when i drop gbu12 so they are realeased pairwise

Both are selectable in the RIO seat so ask Jester for flares pilot controlled and ripple single for bombs. If you're still having the problem ask in a new thread.

[Fear-Factor]

Ok, thanks. Will check it

[Sindar]

AI-RIO takes a very long time with IFF and radar settings. My speed and altitude are equal to the enemy. When a new target is detected in TWS-auto at 30-35nm range, RIO identifies the target as enemy/friendly at 25-30nm range. At this range, there is no longer any difference in arrival time to target between the AIM-120 and AIM-54. In 8 out of 10 cases the AIM-120 hits me faster than my AIM-54 hits the enemy. And that's in the mission editor. In multiplayer, things are much worse. There AI-RIO does more harm than good. Just don't advise me to look for a live person to take the place of RIO 

[draconus]

18 minutes ago, Sindar said:

When a new target is detected in TWS-auto at 30-35nm range

TWS is not for target detection. If you play as a lone wolf (which requires constant radar work) and get jumped on at 30nm you probably already lost the battle. Of course the AMRAAM will get you faster. I hope you don't you don't fly straight head on in the process.

Btw, where are the patch notes, again?

[Sindar]

7 часов назад, draconus сказал:

TWS is not for target detection. If you play as a lone wolf (which requires constant radar work) and get jumped on at 30nm you probably already lost the battle. Of course the AMRAAM will get you faster. I hope you don't you don't fly straight head on in the process.

Btw, where are the patch notes, again?

I understand everything you're saying. But the problem isn't me or the F-14. The problem is RIO's slow performance. In comparison, the AI operators of all helicopter multicrews are much faster. Although there are problems there too. But their reaction speed is significantly faster than the RIOs in the F-14. For the last year, I've been doing almost 90% of my combat from the RIO seat. I only move to the pilot seat for takeoff/landing and maneuvering. That's not right. And no one is talking about it. And it's very important.

[Tomcatter87]

On 1/22/2025 at 7:56 AM, Sindar said:

AI-RIO takes a very long time with IFF and radar settings. My speed and altitude are equal to the enemy. When a new target is detected in TWS-auto at 30-35nm range, RIO identifies the target as enemy/friendly at 25-30nm range. At this range, there is no longer any difference in arrival time to target between the AIM-120 and AIM-54. In 8 out of 10 cases the AIM-120 hits me faster than my AIM-54 hits the enemy. And that's in the mission editor. In multiplayer, things are much worse. There AI-RIO does more harm than good. Just don't advise me to look for a live person to take the place of RIO 

I highly recommend you put Jester in RWS mode when you're on patrol, he can switch to TWS after detecting targets. The longest range mode would be PD Search - afaik Jester does not use this one, though. So RWS would be the choice with the second-longest range. 

[draconus]

22 hours ago, Sindar said:

But the problem isn't me or the F-14. The problem is RIO's slow performance.

I don't agree. In your situation - going head on - time from 30-35nm to 25-30nm is just a few seconds. RIO also needs a few seconds to push the IFF button, designate the target and mark it as hostile.

[Sindar]

3 часа назад, draconus сказал:

I don't agree. In your situation - going head on - time from 30-35nm to 25-30nm is just a few seconds. RIO also needs a few seconds to push the IFF button, designate the target and mark it as hostile.

I described the situation above. Perhaps not in as much detail as I should have. There is no problem on a target at 30-35 nm head-on. It is very bad when 1-2 more targets appear in the radar detection cone on TWS AUTO from the side or below at the same or slightly longer range. AWACS has already labeled them as enemy. But the RIO spends a lot of time classifying them and assigning a number. Sometimes he doesn't mark them at all. Why does he need AWACS' guidance if he's going to start doing the IFF himself anyway? In those cases, I move into the RIO chair, quickly adjust the altitude and azimuth of the radar in the TWS MAN to the new targets, mark them as enemy (based on the markings from AWACS) and make a launch at those 2-3 targets. When I check myself on time, I spend 7-8 seconds on the new target. The RIO has the new target marking sometimes flashing for 15-20 seconds and it doesn't mark it as a target. On the first target, I have already made a launch and it is 30-40 seconds to hit. But RIO does not want to assign a new target. I have to catch it already in PAL mode and I get killed with 15-20 nm. I am very disappointed.

3 часа назад, Tomcatter87 сказал:

I highly recommend you put Jester in RWS mode when you're on patrol, he can switch to TWS after detecting targets. The longest range mode would be PD Search - afaik Jester does not use this one, though. So RWS would be the choice with the second-longest range. 

PD Search is a great mode. I know it and use it always at the RIO site .

[RustBelt]

It’s checking because other than SHTF ROE, you never trust the datalink to perfectly correlate with what your radar sees. 
 

Jester runs a more restrictive ROE than you want to play. It would be neat to dial that in on the fly. But, right now, that’s what Jester do.

[Raven (Elysian Angel)]

On 1/23/2025 at 6:06 PM, Sindar said:

Why does he need AWACS' guidance if he's going to start doing the IFF himself anyway?

HB have stated Jester doesn’t use AEW&C data yet, but that it’s planned for later during the F-4 EA - and since the F-14 is also supposed to receive Jester 2.0 at some point, both modules should benefit.

[Sindar]

В 31.01.2025 в 03:07, Raven (Elysian Angel) сказал:

HB have stated Jester doesn’t use AEW&C data yet, but that it’s planned for later during the F-4 EA - and since the F-14 is also supposed to receive Jester 2.0 at some point, both modules should benefit.

Thank you very much. If I had known this before, I would not have purchased this module.

[Despayre]

10 hours ago, Sindar said:

Thank you very much. If I had known this before, I would not have purchased this module.

Then you'd be missing out on the best module in DCS.

[BIGNEWY]

Removed off topic posts

 

[Sindar]

В 05.02.2025 в 19:47, Despayre сказал:

Then you'd be missing out on the best module in DCS.

A module in which the critical element RIO is not done properly cannot be the best. HB themselves recognize the shortcomings of RIO.

[draconus]

4 minutes ago, Sindar said:

A module in which the critical element RIO is not done properly cannot be the best. HB themselves recognize the shortcomings of RIO.

It is done as intended for the scope. They were always clear on that: