Presently QtJSBSim is set up to use two-engined aircraft. The code which communicates with JSBSim assumes two engines. The JSBSim/aircraft directory in QtJSBSim has a single-engine airplane in it, the P-47D, which will load without crashing, but won't run properly because of the mismatch in the number of engines.
There are plenty of ready-made JSBSim aircraft models which were meant for use in FlightGear, and these can be adapted to run on JSBSim standalone with a little editing:
1) Remove any references to properties which don't exist in the JSBSim property tree.
2) Forward declare properties in "Systems" files where needed.
3) Some Systems files have no use outside of FlightGear, so they should not be used in standalone
QtJSBSim assumes the aircraft configuration file name will be the same as the aircraft directory name. For instance a directory named 747 should have in it a configuration file named 747.xml.
For display purposes the aircraft as shown in FlightGear doesn't have to match the aircraft that is running in QtJSBSim. For instance, I can run the 737 model in QtJSBSim and have FlightGear showing it as a B-52.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm thinking now that I should remove the P-47 model and just stick with the 737. I'd like to simplify things a bit. QtJSBSim is really a technology demonstrator. It's not meant to be a full-featured flight simulator.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Presently QtJSBSim is set up to use two-engined aircraft. The code which communicates with JSBSim assumes two engines. The JSBSim/aircraft directory in QtJSBSim has a single-engine airplane in it, the P-47D, which will load without crashing, but won't run properly because of the mismatch in the number of engines.
There are plenty of ready-made JSBSim aircraft models which were meant for use in FlightGear, and these can be adapted to run on JSBSim standalone with a little editing:
1) Remove any references to properties which don't exist in the JSBSim property tree.
2) Forward declare properties in "Systems" files where needed.
3) Some Systems files have no use outside of FlightGear, so they should not be used in standalone
QtJSBSim assumes the aircraft configuration file name will be the same as the aircraft directory name. For instance a directory named 747 should have in it a configuration file named 747.xml.
For display purposes the aircraft as shown in FlightGear doesn't have to match the aircraft that is running in QtJSBSim. For instance, I can run the 737 model in QtJSBSim and have FlightGear showing it as a B-52.
I'm thinking now that I should remove the P-47 model and just stick with the 737. I'd like to simplify things a bit. QtJSBSim is really a technology demonstrator. It's not meant to be a full-featured flight simulator.