Sooo, link all the sources and see what sticks???
That’s specific snip? No, doesn’t mention threat ID at all. Plus remember with any secondary sources we need atleast two and ideally as many as possible.
1 Like
Third party website, no use I’m afraid.
So you’re saying those websites and documents are basically useless?
No, just the one I sent
It’s the same RWR on the Tornado, you guys already have plenty of data for it.
@Panther2995 Tag me for Gripen related stuff, even if you don’t agree with me at times I do have a long list of sources.
8 Likes
I was just about to say :)
1 Like
This works, if someone can kindly do the needful I can forward a report on it.
3 Likes
Appreciate it, even tho we dont always agree with each other i can always count on you when it comes to sources and proper bug reports.
Thanks again.
1 Like
I don’t have the dev server downloaded. What exactly is being bug reported? Threat identification issues?
Additional information;
basically all radars showing up as “PD” on Gripen
The RWR classes pretty much every fighter radar as F for fighter (or PD currently) rather than identifying the specific radar set and aircraft that it is attached to.
(E.g mig-29/su-27 show up as PD now rather than M29)
3 Likes
According to the source, the library has 10,000 stored emission modes. I don’t see why that would be necessary if anything within a certain range is just considered “F” for fighter.
2 Likes
Will the 0.5GHz count as low band? As Gripen has a low band antenne. It is C band
I believe this is the current data-mined info, and then on dev server Mig-29/Su-27 just show up as PD. Perhaps two separate issues?
So some of these I don’t believe are gripen specific (Though as F-8s are one of few aircraft with decent-ish sarh’s at 10.7 it would be good to know).
So upgrade to C will be confirmed. Hard do say about elevation, but wingtips sensor might suggest it did got ± 90 option
TLDR:
all threats show up as “PD” or “F” instead of specific threats.
and the JAS39C is stil using the AR830 instead of the new BOW-21