Who is excusing it?
1 Like
I get where you are coming from and that is certainly probably part of its IRL performance. But from a radar vs radar basis. Something feels wrong with how the radar acquires targets. I can live with the radar being slightly useless at tracking things. But when you point a radar into a bit of space where there is an enemy and nothing, even after multiple radar passes. Something is definetly broken. If it wasnt, the exact same thing would be happening with other radars, and it just isnt.
From my understanding. First maybe second sweep should locate a target and it should appear on the radar screen. next 1 or 2 sweeps would update direction of travel and IFF. But that can be accelerated by selecting the target and switching to narrower scan mode. That is all fine and I have no issue with having to do that until such time that IRST fusion and Priority track is modeled in game.
But from my experience. It takes at least 3 sweeps before the target might be located and even when it is, I can never seem to get my radar to hook the contact and I usually have to rescan the target a few times to actually locate it. All-in-All. It might take up to 5-8 sweeps of my radar before i’ve even gotten my radar looking at the target in a narrow search mode. Something I have never, ever had to worry about when using any other radar. Heck, even in the Blue Fox feels like a more reliable radar for finding a target im pointing the radar straight at, even when battling ground clutter. Which is just insane to me.
I have a few theories for why its not locating targets, like the TWS being in PD when the target is running laterally and it takes a few scans before switching to a non-PD search mode or something. But I just have no way to test. No way to prove or disprove it.
So, Im just going to keep doing what im doing. If/when I play it. record clips where I know my radar was pointing at the target (ideally with VID) and straight up not seeing the anything. Record the footage from in game using ReLive and then check on Replay that the target was actually 100% in the scan beam.
And then just go from there. Relying on people with far better understanding on the core mechanics to try and determine a logical explanation for why what happened, happened. And maybe in time we’ll get a solution and CAPTOR-M will feel like CAPTOR-M, not a Korean ERA A2A radar
1 Like
nobody except maybe Gaijin.
I had a random "shower thought " on this. A major disadvantage of the side stick is that you can only control the aircraft with your right hand.
With a central stick you can take control with your left hand and do whatever you want with your right hand.
This might be something as trivial as resting it after a long flight, but could also be in things like taking down a 9-line onto a knee board whilst writing with your right hand for example.
Even just being able to the grab the stick with both hands in an emergency must be handy at times. Even with more modern Fly-by-wire systems.
No the problem is very much the Devs not fixing the radar. Sensor fusion would be very nice to have for Eurofighter and Rafale, but even without it the CAPTOR-M should be a very capable radar by itself. Not a downgrade from previous M-scan radars.
6 Likes
As can be seen here, the DASS format MFD does not display incoming missiles in the cockpit, which effectively makes all the MAWS changes the EFT got during this update worthless if you fly in sim without the in-game RWR overlay. I have a short clip and will be making a bug report for this critical missing feature.
One thing I need to test quickly first is that maybe its due to the ranges involved, since the DASS format is permanently locked at 40NMi (good for irl, not so good for in-game), so maybe the missile range was too short to have it show up at all, but I’m pretty sure thats not the case and gaijin has just once again forgotten to model stuff in the EFT’s cockpit properly…
As a sidenote, tho it likely wouldn’t be accurate to IRL (at least afaik), the ability to downscale the DASS display range would be nice… 40NMi (~74km) is massive, and makes it ludicrously hard to figure out where threats are when within ~15nmi, which is when the vast majority of WT engagements occur.
The 40NMi likely wouldn’t be an issue irl either since the HMD would presumably be displaying all friendly and hostile targets real time locations, alongside missiles using the data from all available sensors, but seeing as that’s not the case in-game, its a bit more of a significant problem for situational awareness…
I have some clips of the radar in action and they’re likely to just about make you throw up ngl. Too big for the forums tho, I’ll see if I can send it on discord.
Edit: couldnt send them on discord, so here’s 1/4 for an example:
CAPTOR-L(iability) spends more time tracking thin air then enemy jets when using TWS, and this is with a relatively slow jet, flying towards me, in a predictable pattern. I’d hazard a guess at saying if you arent using STT vs an actual player, you might as well just not use the radar at all. Otherwise, have fun trying to not get your missiles notched when the radar is by default pointing the AMRAAM’s seeker at the chaff instead of the enemy jet…
2 Likes
Alright this is getting incredibly annoying. is there an existing report in for the MAW being unable to correlate SARH missiles to radar warnings, and dumping flares as a result?
-I walk into the room after thermonuclear explosion. Gosh darn it! The switch is broken!
Not that I’m aware of. I suggest you make one.
1 Like
I’m surprised you haven’t already
Not that I know of, however I’d be interested to know how far out of the main beam the missile is when the MAW picks it up and ID’s it as an IR missile. I’m wonder if its far enough off from the CW beam centre if it loses association with the emissions, after all the SARH missiles don’t emit.
1 Like
I’ve barely had any time to play the Eurofighter (or WT in general) since the update. Besides I’d rather not have the WT community rely on me to single-handedly report every issue with the Eurofighter.
6 Likes
Might see if I can get some proper tests done like what I did on dev. Not exactly thrilled to sit down for an hour and a half going through the replay and writing up a summary though.
edit: preliminary look from a recent replay is not looking good.
Launched flares for this AIM-7M
…And this one.
…And this one?? for some reason.
I have no words.
No chaff was launched for the entire engagement apart for one which i popped manually accidentally. I’ll put together a report. If anyone has sources pls post cause i don’t have any on this beyond “there is absolutely no reasonable way”.
Additionally, shouldn’t the MAW radars themselves be able to identify the missiles?
1 Like
I’ve noticed this too when flying the Su-25SM3. I think it’s just sensor fusion being weird. Like how in Test Flight’s it will only launch flares against the ADATS that fires at you.
That’s understandable as the ADATS has no radar emissions, but if you look at that fourth image… I don’t even know.
Additional testing. For whatever reason it works on R-27s more than it does AIM-7s. No comment on that one.
Is there any particular reason why the thrust of the eurofighter gradually drops by as much as 25% during sustained high G manuvers? But when you return to level flight the thrust does not immediately return to normal levels and takes 10-15 seconds to ‘reset’
It’s making the EF lose a ton of speed during high G turns, but then also making it impossible to regain speed and energy when you increase your turn radius.
I am not able to replicate this issue on any other jet to this extent. All other aircraft seem to lose a much smaller % of thrust, and regain maximum thrust pretty darn quickly when exiting a turn.
The EF engines are just so slow to respond…
5 Likes
Thats an interesting thing I hadnt considered was a possibility in-game, you using WTRTI for that data?
At first it was just something I could just feel with how the aircraft responded to control inputs, but then confirmed with WRTI.
Tightening down the turn results in a massive loss of speed if you don’t manage to rip your wings at 12g, it only takes a few seconds of turning to half your speed. But then flattening out the turn to try and regain some energy resulted in it taking several seconds to start accelerating at a decent rate again.
It’s something that just doesn’t happen to this extent on other aircraft.
2 Likes