Yeah, compare it to a Su-30SM2, the new Eurofighter, the Rafale, or even the Gripen E when it’s finished, the J-10C is worse in every aspect, but it’s still pretty competitive, it doesn’t fall behind
1 Like
What I think happened is it probably was causing server-side issues. Maybe they’re just scratching the numbers a little bit to see if the itch would disappear.
What, the scan speed or the vertical coverage?
It’s ugly though
1 Like
The scan speed
Would make sense if su30 didnt sit at 215
1 Like
Nah it’s not ugly cmon…
The hump is bad but the jet is kinda cool
Man it looks like inbred F-16
There’s worse imo, but eh fair.
1 Like
It’s way better than the J-10A at least.
I can justify it by saying that I would conduct performance test the same way. Find the most obvious trouble maker, shave it to perfection, then level everything else accordingly. But why do I even bother at this point? The only bone I’m catching this year is SPICE bombs. If they would want me to defend them - brimstone rework and we’ll start talking.
2 Likes
I will say after using the AESA to ripple off 8 SPICE 250s on 8 convoy targets in grb i’m a pretty big fan of them…
@Smin1080p_WT can we get an explanation for this please as the old scan rate was already half that of it’s real values and now it’s been made worse
1 Like
AESA TWS has like a stupidly high scan speed, like iirc the entire 200x200 area gets updated in less than a second, so i don’t imagine a ~250deg/s scan mode is a problem
Maybe when everyone in the match does it at the same time?
Look, all I know from participating in the same thread last year - they don’t have a clue what they’re doing. Guessing is impossible if the subject is as clueless as you are.
it’s 185 right now. 245 was okay-ish. Problem is that TWS drops targets hilariously easily (i had it drop an f15 flying straight towards me 10min ago lol) so having a slow scan is just abhorrent for maintaining decent awareness.
edit: nvm just followed the reply chain and realised what you meant, ESA TWS is a bit of an outlier. It doesn’t really scan per se. it just does the thing TWS+ does at the end of the scan 25 times per second.
but the problem then would be the AESA TWS rather than the scan pattern, no? so that would be the thing reduced
They’re updating dev every day, so we’ll see. We have Gunjob, they don’t.
Why would this be the case when the Gripen and sm2 both sit comfortably above 200d/sec scan speeds lol
1 Like
The TWS has the search pattern (currently 185deg/s) and an AESA track that runs in the background to update contacts that looks to be coded as a search pattern as well.
My point is that if the coded scan speed/period was causing issues for the server then it would be that AESA track feature that’s responsible and not the search pattern