FlightGear Newsletter November 2015: Difference between revisions

Tags: Mobile edit Mobile web edit
Line 34: Line 34:
The fuel consumption of engines is now calculated to a reasonable degree of accuracy based on a minimal number of inputs. The turboprop engine is now transformed from a turbine-simulated turboprop configuration to a true JSBSim turboprop engine with propeller. Support has also been added for the electric engine.
The fuel consumption of engines is now calculated to a reasonable degree of accuracy based on a minimal number of inputs. The turboprop engine is now transformed from a turbine-simulated turboprop configuration to a true JSBSim turboprop engine with propeller. Support has also been added for the electric engine.


The number of systems has been extended considerably. New systems supported include:  
The number of systems has been extended considerably. Every system adds its own lift, drag and/or side forces, and pitch, roll and/or yaw moments if selected. New and updated systems include:  
* Conventional controls (with or without yaw damper)
* Conventional controls (with or without yaw damper)
* Flaps
* Flaps
Line 44: Line 44:
* Catapult system
* Catapult system


Every system adds its own lift, drag and/or side forces, and pitch, roll and/or yaw moments if selected.
Version 3.1.0 adds code that estimates CLde, Cma, CMadot, Cmq, Cmde, CYbeta, Cnbeta, Cnr, Cndr, Clbeta, Clr and Clp based on wing geometry. Extra is support for  CYp, CYr, CYdr and Cnp based on wing geometry which previous versions did not specify. And after a request from Necolatis the Turbine engine tables are now adjusted for bypass ratio.
 
Version 3.1.0 adds code that estimates CLde, Cma, CMadot, Cmq, Cmde, CYbeta, Cnbeta, Cnr, Cndr, Clbeta, Clr and Clp based on wing geometry.
 
Also CYp, CYr, CYdr and Cnp based on wing geometry was added which previous versions did not specify.


For this to work properly you have to provide factual data. Do not try to estimate it yourself. If some data is unknown leave it blank and AeromatiC++ will make it's own estimation or reverts to the table lookup method provided by David.
For this to work properly you have to provide factual data. Do not try to estimate it yourself. If some data is unknown leave it blank and AeromatiC++ will make it's own estimation or reverts to the table lookup method provided by David.
160

edits