ooh i might actually fly this in sim now
Btw, is it me or has the FPM of the A-10’s HUD been correctly implemented or at least improved a bit now?
1 Like
Eurofighter cockpit seriously needs a rehaul like some other jets have gotten. Couple things come into mind.
- Unfinished button texts & backlight
- HUD UV tint
- HUD symbology is stretched
- Missing EEGS mode
- Improper azimuth display
- Missing DAWS symbology
- Missing radar elevation profile MFD
- HUD & HMD symbology completely broken in VR
- HMD missing ability to display RWR contacts
- HMD datalink symbology incorrectly aligned
- HUD missing FLIR overlay
- HMD missing SIRPH mode
- MAWS should display missiles on HMD
4 Likes
I find it insanely funny and infuriating the fact that most aircraft still use the same shitty digital artificial horizon placeholder when there are tons of cockpit footage to show the actual uniqueness of the said components and others.
3 Likes
The FPM seems to be working fine to me.
However, I have found another problem. The AoA indexer on the left of the HUD is behaving clearly strangely.
I recently noticed that the AoA indexer adjustments on many aircraft, not just the A-10, seem to be messed up.
No matter how you look at it, the optimal AoA is set to a value that will cause the aircraft to completely stall and crash, so it is completely unreliable.
As far as I know, the only aircraft that are fine are the F-16, F/A-18, and Su-33. Almost all others have problems.
The indexer on the F-4 doesn’t even light up at all.
Did you guys noticed that on VR in EF HMD is showing friendly planes but the marker is slightly off, around 2cm from the actual plane. Does anyone know if there is any bug report for this?
1 Like
right here
1 Like
Added
Mosquito B.mK.XVI has floating gunsight reticle
L-39ZA Albatros wing not rendering in cockpit mirror
F-104G wings invisible when looking through the cockpit mirrors
Su30sm2 no targeting pod on screen inside cockpit
(DE) EF-2000 (AESA) Missing IRST view on MFDs
Hawk 209 cockpit inaccuracies
[DEV] JAS39E Radar MFD not scaled to map BUG
[DEV]JAS39E current cockpit model error
JAS-39 Gripen Heads-up-display width inaccurate
JAS39E missing in-cockpit NCTR functionality
3 Likes
Resolution in MFDs is a big problem in almost every plane, perhaps Gripen E being the most broken one. I wonder if Gaijin would do anything to address this issue.
I’ve created another issue affecting the F-18’s cockpit
https://community.gaijin.net/issues/p/warthunder/i/hKrRQbVCHIUD
3 Likes
There are so many issues with cockpit RWR displays.
In many cases the symbols are just outside of the outermost ring instead than within it, making them only possible to see in the RWR GUI overlay…
3 Likes
Added
2 Likes
Yea, likely some bad conversion maths and then mapping to a standard sized texture atlas
Something like this:
note: none of this might be true, and i’m just huffing something
1 Like
I don’t know if u mentioned it in this but the MFD3 doesnt work in the ah64D/E (same cockpit cause gajin is lazy)
1 Like
I don’t think there is a report up for it. But yeah they just didn’t bother with that display.
https://apps.dtic.mil/sti/tr/pdf/ADA310523.pdf (Page 165) (It is approved for public release and sharing)
It wouldn’t really show much but it’s just that little bit extra detail.
1 Like
Greetings, is there a plan or perhaps a roadmap to address all the issues present with displays and sensor information?
I am genuinely asking since issues with the JHMCS and DASH III (to name two of the ones I’ve seen reported) haven’t been addressed so far.
I’m kinda curious to know what the stance or process to follow is.
I’ve seen displays such as those often become a static .png of made-up data, something similar to what happens to digital UFCPs or aren’t modeled like the SCP (Stores Control Panel) in the F-16A