Yep, gets spoofed by missiles every time, unintentionally
2 Likes
I tested the R-73 with a friend, look how it shakes. It can’t even stabilize without fuel.
6 Likes
Unusually the R-73 seems more stable if its turning instead of flying in a straight line
Yes, it looks very strange.
There have been several instances when using an R73 that I overtake my own missile and nearly get shot down by it because it pulls too much AOA off the rails when it really doesn’t need to.
Seems rather problematic as the oscillation is causing very severe drag issues ontop of being very slow to accelerate.
4 Likes
But even if it gets some minor modifications, large parts of the original design were maintained. I doubt it’ll be enough to make it decent compared to the western aircraft, even more if we consider that those also got modified on their late variants.
But perhaps until then the og FMs will all get fixed or at least improved, we need to wait and see what happens.
I really wish we could turn off automated tracking mode switching. There have been many times where I’ll try to switch from an IRST to a radar lock and it’ll just stay IRST. I’ll be spamming the fire missile and wonder what’s going on and then I realize I have mess to with the radar/irst :(
1 Like
Does anybody know if a pdf of this book is available online? Does it have info that the Su-27SK employment manual?
https://meshok.net/en/item/292966698_Самолет_истребитель_СУ_27_Радиоэлектронное_оборудование_Техническое_описание_2022
Havent flown the Su-27 love the look of it.
Whats the main issues with it, when I face it in the Tornado they seem to do well?
Is it just an FM issue? Avionics, missiles?
Mostly comes to FM issues and piss poor radar
3 Likes
Is the Radar accurate to real life? We know Soviet tactics was to use a ground controller to guide the aircraft to intercept point?
It is not, because of lack of documentation on it combined with not the best guess work by Gaijin.
There is some info on the modes and “sensor fusion” with IRST, but some crucial details are missing, like the scan patterns and their period (time of one full scan). IRL, it shares a lot of commonalities with the MiG-29’s radar, which we do have plenty info on, so the Su-27’s radar, in the game, is mostly a copy past MiG-29’s radar with more range.
Here are a couple of things that are wrong:
- Scan width should be 60° instead of 50°
- The 27’s radar has a narrower beam width (3° vs 3.5°). Since the scan pattern is entirely a copy paste of the 29’s radar, there is now very little overlap between the scan bars (the radar scans the sky in horizontal bars. To prevent targets that are in between two bars not being spotted, horizontal scan bars usually have some overlap, kind of how you would overlap your strokes, if you are mopping the floor, to make sure you don’t leave any space not mopped). Because there is little overlap, the radar sometimes misses some targets when scanning the sky (this is an educated guess on my part of why this happens in the game)
- There is currently a bug that affects all airborne radars, but it particularly makes the matters worse for late Soviet radars (Su-27, MiG-29). Because of it, instead of each target, on your TWS screen, taking 3.7 seconds to update (time of one full scan), it can now take up to 7.4 seconds, depending on where the target is in the scan zone. Due to this, you can often have TWS targets on your screen not get updated, so you get false info on where the target is (TWS track flies in the direction it saw the target fly, while the actual target is in a different place).
- The radar now automatically switches to IRST when it thinks it is needed. The problem is, it often does so when you don’t want it with no option to turn it off (there is an option like that IRL, however). It is often that you lock a target with your Radar HMD, but the game decides to switch you to IRST tracking, which you can often don’t even notice, because only some letters above the radar screen change. You then try to launch your radar missile, but the game will not let you, because your are tracking with IRST. You then lose precious seconds fighting your radar to get it to launch. This has killed me quite a few times.
- There is a 10 km limit for Radar HMD (while most western radars at that BR have 19km). That 10 km limit is not actually listed anywhere in the Su-27 or the MiG-29 manuals. That figure is only given to vertical ACM mode. So Gaijin just put the same limit on Radar HMD for the 27 and 29. While I can’t directly prove that the 10 km limit is not there for the HMD (can’t really prove it by going “oh, there is no mention of a limit”), there are however some “hints” in the manual about that (IRL, there is an option to have the radar switch to a Radar track, from an IRST track, automatically, if the target is within 15 km, or manually, if the pilots presses the lock button. The manual refers to it as locking “into a point”. The manual also states that locking “into a point” is how the Radar HMD works).
- IRST has like a half of its all aspect range. There is also a 30 km limit, which Gaijin “fixed”.
- The IRST scan zone is fixed in the game, while it should be able to be moved. Interestingly, it was possible to do so in the game before, but they removed it.
Overall, the Radar/IRST set is inferior to other planes at that BR (except for the presence of the IRST) and is quite finicky to use. However, I find it more fun to fly the Su-27SM that the F-15C or the F-16C, because of the variety of play stiles you can go for. Although, it is probably one of the most “positioning skill” dependent plane right not.
11 Likes
no, it isnt.
https://community.gaijin.net/issues/p/warthunder/i/GXyfSoc4CHSt
and theres one more about that radar must lose lock if bank angle more than 90
Community Bug Reporting System found it
Good break down:
The TWS errors and tracking missile is a massive issue for me when using the Tornado.
The Tornado is a poor airframe but has a great RADAR, I read that they were able to jam other RADARs with it.
Do they just ignore your bug reports or do they asscept them?
Having only flown the F-15 MSIP II on a friends account it was easy mode
Hope they fix the issues and make this aircraft playable :)
Will the PAESA
2 Likes
ban yourself lol
A lot of aircraft can use their own radar, or special pods, to jam enemy radars, we simply don’t have any kind of radar jamming implemented in the game.
Usually not. They accept them, but it can take anywhere from a month to more than a year for things to get fixed (if they get fixed at all). Devs tend to focus mostly on bugs that are about newly added vehicles. In this particular case, when the Su-27S came out, I was busy with school and didn’t file many bug reports (other people have done so, but there are some bugs that I knew about and nobody filed them). So I kind of missed that window of devs paying a lot of attention to new vehicles. A specific example of that is this bug. It was a couple of months since it got accepted, but there were no fixed, so I tried messaging Smin about it (it is my favourite plane, after all). The devs tried to fix it shortly after with the launch of dev server (can’t say it was Smin who nudged them, but I would like to think so). However, the fix didn’t really fix much. The IRST was still capped at 30 km (they increased that cap to 100 km in one part of the code, but not the other, so nothing really changed). They raised the all aspect lock range value from 5 km to 6 km, but it was not enough to bring it to IRL performance. I guess they were very busy with tuning the FOX-3’s that were about to drop in a few weeks, and they just kind of spent the minimum time required to fix it to get back to working on the update.
It is pretty easy to fly. Though, for some reason, I didn’t enjoy it as much and didn’t have games where I was getting a lot of kills as often. I didn’t play that many games in it, however (just a bit more than required to get all the mods that are not for ground pounding).
The SM does not have a PESA. Later version of the Flanker have it. I will probably just make life easier with more reliable TWS with a shorter scan time.
Hope so too, but I doubt it will be any time soon.
6 Likes
Hey, has anybody had this following issue? It does not happen on the Flanker, but I don’t know any big threads for planes which are affected, so posted here.
Looked on J-7E and it seems it comes from that CM dispensers always fires in pairs (switch to only FLARE or SHAFT, it will launch a pair), but then switched to SHAFT and FLARES it does exactly this - fires both pairs.
Now… I honestly dont remember now if before equipping SHAFT and FLARES option would change the pair to include both or not
How it was before:
- Take only flares - 1 key press deploys 1 flare
- Take mixed - 1 key press deploys 1 flare and 1 chaff
How it is now:
- Take only flares - 1 key press deploys 1 flare
- Take 30/30 - 1 key press deploys 2 flares and 2 chaff
Also, I’m curious, why do you capitalize flares and chaff, and why do you write shaft instead of chaff?
Further tested with J-7E and yes, if take 72/0 it does a single flare, but if to take, say, 71/1 and switch to only flares it does fires them in pair. Now thats weird tbh. Wouldn’t be surprised if Gaijin made the logic with new switchable flare/shaff based on old flare and shaff option with just preventing use of the other variant if it switched to just flare/shaff, but the logic is built on firing a pair (to make old flare + shaff work) and so it does exactly this. Could be a base for a bug report come to think, but I aint brave for those
As for the other thing - just highlight, nothing special. And autocorrect desperately tries to correct “shaff” for “shaft”
Edit: Tested on MiG-23ML, MiG-27M and Su-25 and they fire flares in pairs even if selected only flares. J-11 and J-11A fire a single flare if only flares selected. So it seems like it specifically those (+ unknown more) aircraft issues (unless those work correctly, but Im not knowledgeable on the matter)
1 Like