70
edits
Bugs: Difference between revisions
Jump to navigation
Jump to search
mixture versus altitude
John Denker (talk | contribs) (version number) |
John Denker (talk | contribs) (mixture versus altitude) |
||
| Line 4: | Line 4: | ||
If the version number hasn't been released yet, that means that the fix is in CVS (this makes life easier maintaining the page - status doesn't have to be changed each release) | If the version number hasn't been released yet, that means that the fix is in CVS (this makes life easier maintaining the page - status doesn't have to be changed each release) | ||
==== Z-buffer burn-through ==== | ==== Z-buffer burn-through ==== | ||
| Line 191: | Line 185: | ||
First posted to the flightgear-devel list in November, 2006. | First posted to the flightgear-devel list in November, 2006. | ||
==== Mixture versus Altitude ==== | |||
It is observed in the default c172p and in the c182 that at | |||
high altitude airports (e.g. KGCN or KASE), to obtain max | |||
static RPM, it suffices to move the mixture control only a | |||
few mm aft of the full-forward (full-rich) position. | |||
This is unrealistic. In a real aircraft under such conditions, | |||
it would be necessary to pull the mixture control back about | |||
an inch to obtain max RPM. | |||
It's hard to say whether the engine is underreacting to the | |||
altitude, or overreacting to the mixture control. | |||
==== EGT reads high ==== | |||
It is observed in the default c172p and in the c182 that the | |||
EGT reads toward the high end of the scale under all conditions, | |||
including idle. This is unrealistic. | |||
Also, the EGT reads ''off-scale'' high under high-power conditions. | |||
== Missing Features == | == Missing Features == | ||
==== Version number ==== | ==== Version number, please ==== | ||
It would be helpful to have an easy, documented way to ascertain the | It would be helpful to have an easy, documented way to ascertain the | ||
| Line 215: | Line 231: | ||
== Fixed Bugs == | == Fixed Bugs == | ||
==== '''0.9.5 - 0.9.8 - Windows - Crash on start reporting "Could not gen source" | |||
==== 0.9.8- Linux and perhaps Windows crashes when specifiying --lon or --lat ==== | |||
This version of flightgear an issue with starting coordinates that are lie on the boundary before tiles or coordinates. | |||
Workround: Specify the latitude as a slight offset to what you require. Eg instad of --lon=16 make it --lon=16.0001 The difference visually is next to nothing. :-) | |||
* '''This bug has not been observed in 0.9.10.''' | |||
==== 0.9.5 - 0.9.8 - Windows - Crash on start reporting "Could not gen source" ==== | |||
Any further reports or stacktraces on this bug would be appreciated. | Any further reports or stacktraces on this bug would be appreciated. | ||
| Line 223: | Line 248: | ||
* '''This bug has been fixed in 0.9.8a''' | * '''This bug has been fixed in 0.9.8a''' | ||
==== | ==== 0.9.7 - ? Linux - Joystick crash with correct config files ==== | ||
Workround: Comment out any unused axes (and, possibly buttons) in the config file - if your joystick has 3 axes, comment out axes 4 through end. | Workround: Comment out any unused axes (and, possibly buttons) in the config file - if your joystick has 3 axes, comment out axes 4 through end. | ||