* gerard robin -- 8/26/2008 11:23 AM: > Won't it be possible to get with a generic Nasal script? > > with the closest Carrier: > The Catapults position with heading. > The wire positions Left/right position.
Could be problematic. The involved subsystems are handled at different places in the main loop, which can easily cause synchronization problems. (aircraft -> FDM update, carrier position -> AI update, Nasal loops -> event handler, visuals -> view manager update). As Czaba wrote, letting the FDM do that (in connection with the fgfs interface code) is more promising. > Like we have a generic aar.nas (though it is not usable for me, too generic ) > > we could have, a carrier.nas. I intend to merge Generic/aar.nas with Nasal/fuel.nas (which are almost the same already), and to offer a simple interface for special needs. The detection of a tanker (not necessarily a flying one) is a generic job, and so is refueling. The part that may differ is what happens with fuel that entered the aircraft. And for that we could just write the fuel amount to a property. An aircraft could then attach a listener to that which takes the fuel and does whatever it likes, and finally resets the property to zero. m. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
