do you mean some FDM/autopilot-specific "debug" properties that are not generally accessible ?
If that's the case, they should definitely be made available through the property tree.
Could you provide an example that's easy to reproduce ?
EDIT: Assuming you are referring to the AP: http://wiki.flightgear.org/Autopilot_Co ... ence#Debug
It seems you are right, the autopilot's debug mode only writes to the console - but that should be simple to change if you can build from source, and it would seem like a good idea in my opinion, you should probably file a feature request: http://code.google.com/p/flightgear-bug ... %20request
https://gitorious.org/fg/flightgear/tre ... /Autopilot
- Code: Select all
component.cxx:33: _debug(false),
component.cxx:68: if ( nodeName == "debug" ) {
component.cxx:69: _debug = configNode->getBoolValue();
digitalfilter.cxx:430: if(_debug) {
flipflop.cxx:464: if(_debug) {
pidcontroller.cxx:123: if( _debug ) cout << "Updating " << get_name()
pidcontroller.cxx:129: if ( _debug ) cout << " input = " << y_n << " ref = " << r_n << endl;
pidcontroller.cxx:133: if ( _debug ) cout << " ep_n = " << ep_n;
pidcontroller.cxx:134: if ( _debug ) cout << " ep_n_1 = " << ep_n_1;
pidcontroller.cxx:138: if ( _debug ) cout << " e_n = " << e_n;
pidcontroller.cxx:145: if ( _debug ) cout << " ed_n = " << ed_n;
pidcontroller.cxx:149: if ( _debug ) cout << " Tf = " << Tf;
pidcontroller.cxx:154: if ( _debug ) cout << " edf_n = " << edf_n;
pidcontroller.cxx:167: if ( _debug ) {
pidcontroller.cxx:179: if ( _debug ) cout << " max saturation " << endl;
pidcontroller.cxx:182: if ( _debug ) cout << " min saturation " << endl;
pidcontroller.cxx:187: if ( _debug ) cout << " output = " << u_n << endl;
pisimplecontroller.cxx:67: if ( _debug ) cout << "Updating " << get_name() << endl;
pisimplecontroller.cxx:72: if ( _debug ) cout << "input = " << y_n
pisimplecontroller.cxx:86: if ( _debug ) cout << "prop_comp = " << prop_comp
pisimplecontroller.cxx:90: if ( _debug ) cout << "output = " << clamped_output << endl;
Another issue is that the code uses std::cout directly and not the SG_LOG() mechanism. I would usggest to turn the debug variables into property objects and expose them via the property tree if enabled: http://wiki.flightgear.org/Howto:Use_Pr ... ee_Objects