Thanks for reporting Soitanen! I'll include a fix in tonight's update.
@Hooray, that's a completely different issue.
Gijs wrote in Sun Jul 06, 2014 7:48 pm:@Hooray, that's a completely different issue.
Gijs wrote:Thanks for reporting! I'll have a look at this and other ND bugs this weekend, to make sure it's ready for the release.
Philosopher wrote in Sun Jul 06, 2014 10:52 pm:I added a "z-index" field to the config hash for the very purpose
Gijs wrote:Johan & Soitanen wrote: think this and similar problems will be coming up for more or less every aircraft as the properties differ between FDM:s and sometimes even between aircraft.
[...]
aircraft, which will use NavDisplay must have airspeed-indicator, created as built-in instrument, so I prefer to select airspeed indicator as source (which is close to reality).
We could implement a way for individual aircraft to feed the ND with their own properties. However, standardizing the properties would make more sense, also for other use cases (bindings for input devices, dialogs etc.). That is even more important for the PFD, since there are dozens of different autopilot properties being used in FlightGear.
Displayed if wind magnitude is greater than 6 knots and blanked if wind magnitude becomes less than 4 knots.
Users browsing this forum: No registered users and 4 guests