* Maik Justus -- Sunday 09 December 2007: > With this trick I should be able to transfer the wing-fold > and engine-tilt animation of the v22 over the MP-protocol.
Yeah, that's a typical case for properties where standardization wouldn't make much sense, and generic ones are therefore preferable. Though you wouldn't need the embedded Nasal at all, if you just change the property names to the generic ones everywhere. That's just not an option in the bo105, as I have to post-process the transmitted strings and to load the variant XML file. BTW: in my tests yesterday I noticed that the <unload> part was never called, and so the loop is never stopped. This can lead to collisions when the same aircraft type joins in a second time. This worked when I wrote the Nasal embedding code. Has the MP code been changed to never release once loaded models?! m. ------------------------------------------------------------------------- SF.Net email is sponsored by: Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
