Andrew wrote: > Oh yeah. Duh. I knew that. :) I *will* try that someday, but I'm > lacking the required second machine at the moment. > > > Just need to get the "turbine data" across the > > link (Assuming that YASIM is generating N1, N2, EGT, EPR, oil > > pressure, fuel flow, etc) > > Sure thing: > > /engines/engine[n]/n1 > /engines/engine[n]/n2 > /engines/engine[n]/epr > /engines/engine[n]/egt-degf > /engines/engine[n]/fuel-flow-gph > Double Duh!! After downloading and compiling the latest CVS, (my last update was mid -dec) I added my latest changes to the interface and it naturally bombed, big time. When I realized that the FGEngInterface class was gone my first reaction was OH NO!!! I should have looked at the opengc.cxx source first before replacing it. :-O Whoever made the changes in opengc.cxx to properties, thank you.
I've duplicated a lot of the navigation code on the opengc side which reduces the interface immensely and makes building the FMC a lot easier. for example, the FMC does such things as auto-tuning to select VOR stations in range to update current position against the flight plan, displays routes, waypoints, airports, and such. There are 12 to 13 different Nav displays including weather radar, lots of eye-candy to build! >zero-offset) with N1 (presuming that's the turbine stage that runs the >oil pump) for a given engine. If you have cruise data for oil >pressure, I'd love to see it. If you want a good source for engine data from taxi to cruise, touch base with [EMAIL PROTECTED] Thanks again John w. _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
