> So then, to migrate changes in JSBSim.cpp to JSBSim.cxx is a manual > process??
This is not something one would normally do. JSBSim.cpp is sort of a "driver" program that initializes an instance of FGFDMExec and then reads a script or an initialization file and just runs (calls a FGFDMExec::Run() repeatedly) - it's batch, not realtime. Useful for testing and educational purposes. JSBSim.cxx also instantiates an instance of FGFDMExec, and calls the Run() method periodically as directed by FlightGear, but it also copies important data between JSBSim and FGFS. > and changes to the other .cpp and .h files are picked up by the > respective makefiles when building fgfs and the standalone jsbsim? And, > finally, is JSBSim.cxx "work-in-progress", i.e. the databus is not fully > populated or there are more e->set_xxx(eng->get(...) )to code? The data bus is probably populated enough for your purposes (?). If not, it can likely be made to do so fast enough. > BTW: has the problem with the c310 twin engine models been resolved? Yes, I believe so. Stupid error. Check the JSBSim web site/page as mentioned below. Jon Jon Berndt Coordinator, JSBSim Project http://jsbsim.sf.net Enter BUG REPORTS at http://sf.net/tracker/?atid=119399&group_id=19399 Enter FEATURE REQUESTS at http://sf.net/tracker/?atid=369399&group_id=19399 _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
