Hello, About Carrier capabilities with JSBSim , we have had a talk about it. Was said that we could not get the same features than we have with YASim. Since JSBSim with the "external_reactions / forces" offer a real flexibility ( magnitude, azimuth, direction, timing, BODY, LOCAL, WIND), it was a pity to be unable to use the catapult feature, like in reality, only because we don't have, in real time, the right coordinates of the catapult on a moving carrier. I have just included with the Crusader (CVS) that feature.
So, now, every carrier capabilities can be used with JSBSim FDM. :) :) For instance the Crusader can land an take off on/from any carriers, Nimitz, Foch, Eisenhower, Clem ......from any catapult. ==>The process is, carrier deck geometry description based => systems/carrier_geometry.xml file. That file contains, every existing and coming class ship carrier wich are ( or will be) within cvs, nothing difficult, the coordinates position and the relative heading of each catapult on the deck it could be easily updated) ==>The real time calculation of the position of the closest carrier , and the catapults involved, is done with a Nasal script => systems/carrier.nas file. That nasal script is a scratch it should be improved it does use, mainly, a generic script geo.nas ( data/Nasal folder, thanks to Anders who point me on it ) Carrier.nas, when the gears are in touch with solid, poll every carrier from AI, looking at the carrier which is at a distance of 150 meter or less ( we presume that we are on that carrier) then the right geometry is selected and stored. Anything else is a loop which, permanently update, the catapults coordinates, and real heading, which are then stored in properties, used by the FDM. ==>The last main file, which is part of the FDM systems/cat_external_data.xml, does comparisons with the aircraft position and each catapult position on the deck in order to identify which catapult the aircraft is on ( on_area ), if found, the right heading is then stored. These three files are generic and could be used by any JSBSim aircrafts. The following, is the usual process ( within JSBSim) The Launchbar can be locked ( if requested by the "pilot" ), the external_reactions (customized to the Aircraft) will operate to hold the Aircraft in place. The Catapult could be, then, acted with the force according to the external_reactions (customized to the Aircraft) , the direction will be given in real time coming from the previous process. That process will offer a lot of advantage,, coming from the know how, in real time, of the deck description, and the flexibility of JSBSim. We will be able: => to process an automatic taxiing from any place on the deck, to any chosen catapult, => to animate any specific crew on the deck, =>to raise the right JBD according to the catapult involved ...................and so on ( i start working on it with the Clem and Foch) I hope this useful. Cheers -- Gérard http://pagesperso-orange.fr/GRTux/ J'ai décidé d'être heureux parce que c'est bon pour la santé. Voltaire ------------------------------------------------------------------------- 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 Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
