If I recall from a Discord discussion. This was a phantom nerf, essentially nothing happened and Gaijin wrote it by mistake or forgot to push nerf to live.
If it is the same rwr that is used on the Tornado then the threat tables can be customised and programed on a per mission basis by the ground crew.
There is a database of known threats that can be individually uploaded to the mission computer on the aircraft to identify any kind of ping from early warning radars, datalink communication, individual missile seeker types as well as any classification of radar based on its known dopplar shift and assigned a custom, unique or common code.
The mission computer will prioritise threat types from least threatening to most threatening to avoid oversaturation of information to the pilot/wso. (No point pinging about an EAW when there is a missile being down on you.)
While gaijins implementation is technically correct in that you could theoretically assign every threat as “PD” this simply was not done in real life or in any mission.
At the end of the day, the missiont intelligence would determine what threat tables would be used
I did some digging on the internet… I found something. And started laughing. I think I found the original of our radar page on MFD… It’s on Wikipedia… Photo from ADAS 2018
Let’s start with the funny. Gaijin missed a LOT of symbols and letters.
Spoiler
Let’s go clockwise.
We’re starting off well. “GRND [AIR]” and “GRND [AIR]”
The original says “[GSC] EXI”, and in the game it’s “GCS E I”. Where’s the “X” and the frame, Gaijin?
Let’s look below it’s “A/L EIX”, and in the game it’s “A L E I”. Seems someone’s keyboard have malfunction when they were typing symbols in the game?
Next. “SNSR EXI”, and in the game “SNSR E I”. Seriously, what’s wrong with the letter “X” on your keyboard?
This part is not in the demo photo, so I will use the image from the presentation as an example
“[BSCP] PPI” and “BSC I”
Then. “[CORR]” and “C RR”
“ID” and “ID” I would be very upset if they managed to get two letters wrong.
From “FREZ” only “RE” remains
From “XIMG” → “IMG”
From “SAVE” → “SA E”
Well… Let’s get to the difficult part. It’s a real mess here. From “[RDR] MENU” they somehow got “MEN”
“[CURS]” → “C RS”
“HRES” → “HRES” Miracle
X-block is missed, I won’t blame them for that. I don’t know what it is myself
Missing slash in radar mode selection block
“INIT” → "INIT’
And back to the presentation
“EMGY” → “EMG”
Jokes aside. Now to the analysis of what we see. Upper box. Under the spoiler are the aircraft parameters.
Spoiler
As we can see in the photo, the plane is at 10,300 feet, and on the side scale, the icon of our plane is in the area of the first mark, as I assumed - the 10,000 foot mark. The gaijins simply copied this position of the mark and in this position it is at 1,000 feet and at 40,000 feet. The target taken on sight is circled in red and there is an additional vertical line on it for the entire height of the box.
In the middle box “R” still marks the distance to the target, 25 miles. “A” denotes the target height as 17.5 feet (thousands), “M” is the target speed in Mach. Below and to the left, in a frame, is the number “40” And if you look closely at the radar window below, “20” is marked there as half, which means that “40” is the full size of this radar scale. Of the entire box, only the radar size works correctly so far.
As I already said, the lower part of the MFD is already implemented well. The only thing missing is IFF and a cursor for selecting a target. And one more thing that I just noticed - there is a small blue mark on the compass. A small, large and again a small line. This is the course to the airfield.
Don’t be too optimistic :)
Just to point out, the “elevation” part of radar doesnt work in WT iirc. It shows your plane pitch, instead of where radar looks. Its the same on planes which currently uses altitude coverage at TDC on live server. If you fly straight with no pitch, it will be fine, but the moment you start pitching, it will start moving scanned altitude like if your radar is fixed (it happens when you use custom radar elevation, not the fixed one).
I will be reporting that today to tomorrow. Im doing everything wrong with radar mfd
At the same time, they get stuck at scan limit. They wont move to previously set altitude which is wrong too. They use planes avionics to determine where they should return once they are withing gimbal limits.
Then i guess im not doing that. Ill report the datalink line then.
I would say this is valid to report, its a pretty big nerf not being able to reach max altitude and the time to get there should be more accurate. Really nice job with all your testing Mig_23M!
Do you mean the indication of your missiles on the radar?
Datalink to ARH missile while it is outside of pitbull range. I will do the report tomorrow.
I didn’t quite understand what you mean, but if you know what you’re doing - good luck)
When you have a Fox 3 missle (AMRAAM, R-77) it has for example 16km seeker range, but you can fire them over a greater distance, and use TWS to update them where the target is. That is Data link, and Gripen display should have it shown. Display is a missile symbol and a line to it. Green if DL singal is strong, orange if mid, red if Bad etc.
Ah, that. That’s what I described here.
So I got it right from the start
Yea
I need your guys help
on this video you can see him move the radar cursor from the map to radar, and lock things. While he moves it around, number on it change. I tried to figure out what there numbers mean, but i failed to, could anyone plese explain it to me?
I am well aware it is tragic, but it is what it is
the green line is the DL
You can see a green dot moving, the dot also changes color depending on if the missile has enough energy to hit the target.
All can be seen here(both C and E use the same symbols, so its fine)
