100 Upvotes , my brain is booming

@TheSPPlayer theres probably a better way to say that, without seeming so condescending.

Although to outsiders, this HUD and PFD are well done, I found several flaws:

1. You are still using your old architecture, and based on actual testing, this architecture will occur including but not limited to:

   • Error displayed when the speed scale value of the speed/height display bar is at the top.
   • Error display occurs directly due to scientific notation when the X or Y (or both) coordinates of the display element approach 0.
   • Severe excess problem in the attitude display section of the PFD.

2. Display of ground height on height bar:

   • What I thought at first was that the distance between each slash was constant; as the height increased, the number of slashes decreased; when reaching a certain height, it disappeared.
   • In fact: the number of slashes is constant, and the distance between each slash decreases with the increase of height and eventually disappears.

The disadvantage is also obvious: if you do not rely on the terrain position of the horizontal bar, it is completely impossible to determine the change in ground height.

I hope it will improve in the next edition

好！很有精神！

For metric?

Thank you for the hud! I made sure to credit you in my build :)

Nice display, it’s almost possible to fly on instruments using this display. My only critique is your Mach formula is only an approximation, I suppose if it was that important, I’d simply modify the formula you’re using here. Nice work.

嘿嘿我是榜一

100th upvote

please add "Part" tag

@vSoldierT Simplify equations as much as possible and avoid excessive trigonometric functions. On my EICAS and ND display, I used a script to generate arcs/circles out of dashes (no sin and cos in the label), but for a moving display like this one there is no way to remove most of them. On my modified version of the 1 part PFD (the 3rd version), I found several repeated calculations and was able to simplify them, but I still needed a lot of the sin and cos calculations (and others), since they had unique parameters. I also believe the more moving (dynamic) characters, the higher the lag. So there is no significant optimization possible, which is one of the main factors for me developing modded screens which have almost no performance impact yet even higher detail and realism.

@PlaneFlightX What is the best way to optimize labels?

@PlaneFlightX yep, it does gives an advantage since its purely vanilla

@dekanii Yeah I found that with my own label screens (the PFD is a heavily modified version of the 1 Part PFD Version 3) have a huge performance impact, while the modded screens I made (which have absurdly more details compared to the labels) have almost no impact. Although, this is vanilla which does give it an advantage, especially for mobile players.

Great job! I'm going to stick with my own heavily modified version for my plane (plus I'm focusing more on modded screens now), but this is very cool and I can see a lot of work went into it.

HUH???

(welp, time to replace the freaking PFD on my radial aerospace family...)

ayo congregation for yer platinum recieving 🔥🔥
also i love the HUD you made, but im 100% sure thats like memory intensive, too bad i cant use it since i have a dog shit phone 💔
still very good indeed

Hello

If possible, please fix the radar screen, like the one in the cockpit of the Su-35 or the F-15 and F-35.

@BluesynVNA yeah thx

@SARACONIKaviationIndustry yes good job and congetouls for 25k points