From: Thorsten R. <tho...@sc...> - 2017-07-04 06:05:09
|
> This may help folks understand what the G1000 is all about. > http://static.garmincdn.com/pumac/190-00498-07_0A_Web.pdf > Writing a G1000 isn't that hard. Writing a *feature complete* G1000 is > a metric f***ton of work. ;) Browsing that, I still stand by my statement that this doesn't have more than 50 unique parameters you need to update per cycle - for most pages significantly less. All the config pages have lots of items - but you only need to update them when they change. All the fancy airport and weather charts absolutely do not need updates per-frame - your airport isn't going anywhere or changing in a hurry - you can just draw the whole layer _once_ before you bring it on-screen and then use a global transform to move it as the plane moves and run lazy updates on the edges. Precipitation you can update whenever FG updates precipitation (every few minutes). Most maps can be done as cheap raster images rather than vector data (the Saab Viggen just downloads them on the fly for instance). So yeah, it's a lot of work to code all these displays which someone has to do, but there's no reason to assume it'd be hopeless performance-wise. * Thorsten |