Hi John, I ran into the same problem with using generic instruments when developing the bluebird over 2 years ago. Some instruments rely on properties that are only updated by the FDM, and the ufo doesn't. So I wrote my own nasal to fill in those gaps, and/or I made my own instruments by modifying a line or two from the generic version.
In another case, the instrument(s) look to the property systems/electrical/outputs and so does not work because the ufo does not have an electrical bus. :) Another property the ufo fdm does not update is altitude-agl etc. etc. So you can't change the FDM and expect everything that rely on a specific FDM, to keep working. Stewart John Denker wrote: > Here's a mystery for you: Please take a look at > http://www.av8n.com/fly/fgfs/img48/null-fdm-instruments.png > > Most of the instruments are working, but the rate-of-turn > indicator and the Nav 1 CDI/GS needles are frozen. You > can see from the property browser that the Nav receiver is > properly tuned up and is trying to drive the needles. > > This is observed during playback using the null FDM. The > same sort of frozen instruments are observed using the UFO > FDM. > > > I have debugged this as far as I can. I'm stuck. I don't > have any good hypotheses as to why some instruments are > working while some parts of other instruments are not > working. > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
