- Messages
- 943
- Country

Which one is more performance friendly?
All GDI+ gauges that I have seen so far came with a considerable framerate hit.
in some case yes it was, that because i'm still beginner with this program. but after i growing my knowledge up, there many mistakes that I did.
if build GDI+ just like native C++ from SDK you would face to FPS Killer. there many thing you can do to make that more simple and lot easier.
i have 4 to 6 screen in this aircraft, with GDI+ lines reaching 1200 lines and still growing up. my computer not fast enough so i set my P3D fps limit to 20 fps. with all 6 screen active my fps still around 19.9 fps just like i use another aircraft.
for performance i feel both of them are same. just feeling not calculated by software or just see the P3D fps.
in my case
C++ only display 1 screen (PFD), 1 MFD gauge (default b737) and 3 gauge from default King Air. result from P3D is around 19.9 fps.
GDI+ has 4 screen (3 PFD, 1 EICAS),1 MFD gauge (default b737) and 3 gauge from default King Air. each screen can customize on it own screen (PFD, NAV, FLIR, STAT, SYST) and the most active calculate by know is PFD, other still WIP.
for note: 3 screen PFD call from 1 gauge, so if this displayed on 3 screen it will calculated 3 times simultaneously. the result i get is this still around 19.9 fps.
in early writing GDI+ ( around 200 lines ) and i missed 1 line to closed a "clip", that make big impact in P3D the FPS drop to 6 - 8 FPS. if beginner face framerate hit, maybe my experience can be a reference, "watch out what you type".
I'm still beginner, feel free to correct me.
add edit :
Have you tried the default Acceleration F/A-18 Hornet? Not all GDI+ gauges are slow. It all comes down to profiling and optimization -- see this post: http://www.fsdeveloper.com/forum/threads/gdi-gauges-cause-low-fps.15945/#post-103512.
i agree with it. i think there many way to build GDI+, long way or short way. but after that there still has the shortest way. just find it out.
Last edited:






