Eurofighter Typhoon (UK versions) - Technical data and discussion

Nah, it’s performance there is also not so great as if you put any ground ordnance on it turns into a brick and is no better than a tornado at killing ground targets.

Most air RB players stick to Air RB unless they are grinding aircraft for GRB.

It was FOTM for a month, then when it was nerfed people realised it had no redeeming qualities over other aircraft.

I think we also absolutely deserve brimstone 2 in SAL mode, and brimstone 1 in fire and forget mode, but with no autonomous ability/lock on after launch.

1 Like

I would agree with that assessment, they can still do work in ground battles but they are outclassed.

If they planned to nerf it that hard they should not have added it yet.

You are wrong. Plain and simple there is a multitude of sources that state otherwise for relevant ordnance.


This really comes down to if Classification of a Target is a Subset of Identification, or if it’s the other way around, and as to how much you think it matters that it could distinguish a T-72 from an M1, M3A3 or BMP and a Ural or Gaz, it can tell the difference tween Tracked and Wheeled vehicles and approximate size but that’s all it needs to do the job, a positive VID and ROE restrictions fall on the pilot anyway so more detail really isn’t needed, since alternate guidance modes do exist to provide it as needed.

For example the AGM-114L, GBU-53/B and others like the Brimstone all used similarly derived baseline MMW seeker from the AGM-124 WASP (Wide Area Anti-Armor) project and are able to classify returns and desegregate targets using Sorting functions to ensure that repeated selection of the same target does not occur, even without the use of a two way datalink for track correlation and disambiguation as sufficient info can be provided prior to launch.

How this could be accomplished using a MMW seeker is postulated in the following paper

https://www.tesble.com/10.1109/igarss.2019.8898353

And sorting is covered in this report (Directly relevant to IIR sensor, but remains partially relevant, as it discusses sorting techniques which remain relevant to mapping seekers)

https://www.airandspaceforces.com/PDF/SiteCollectionDocuments/Reports/2010/August%202010/Day25/SDBII_factsheet_0810.pdf#page=2

UAI



https://www.iqpc.com/media/6729/4428.pdf#page=10

6 Likes

Brimstone Launch Angle Fix is on Dev-Stable coming to prod soooon. Love that new 40° limit.
image
Big thanks to @Mulatu_Astatke for the source.

48 Likes

9 Likes

Is this when we point at someone and laugh our arses off?

IMG_6008

1 Like


For whatever reason, the IRST acquire doesn’t seem to understand… looking down? If the target is below the nose it just doesn’t scan over it at all.

I wish other eurofighter fixes would get implemented as fast as that brimstone one.

3 Likes

it physically cant because it is ontop of the nose,
for it to be looking further down it would have to look through the nose


I dunno about you but that’s a pretty big negative angle it can get.

The fact it can detect a target, but then refuses to track low enough to actually lock it is my problem. the acquisition sector doesn’t cover the search sector.

You can tell because the acquisition sector is 30 degrees while the search is 40

In other news, they don’t seem to have properly fixed the MAW detecting countermeasures and under specific conditions it still will…

You arent looking at it perfectly straight from the front but from one side, which makes it seem larger than it is

image

but who said the acm box needs to cover the whole sector?

IRST as modelled in game scans a huge vertical bar in the acquisition scan. it doesn’t elevate. In that image i’m trying to acquire an aircraft
image
on the A point, here. The scan sector however doesn’t scan downwards, for some unknown reason, which causes it to completely miss and just fail to establish a track. The IRST detected it, which means it’s in vertical limits. It just doesn’t acquire that low for some reason.

because thats how the scan area got set up by gaijin

you have that huge green box on your screen showing the actual scan area
image

…Yeah and i’m saying that setup is wrong. the IRST has detected a target, so it’s within the physical limits of the sensor. the scan sector for acquisition can’t reach all points in the search sector because it has a vertical limit for some reason.

then find a source and bug report it ig

it dosent have a limit it is just not searching there

Lol

@Mulatu_Astatke many thanks for buffing the brimstone

4 Likes

Do I need a source to prove that when i try to lock a target the IRST found, it should search over the position of the target to find it?