Hi All, first of all, I'd just like to complement the developers on their outstanding work - I've been playing with FlightGear over the past couple of weeks and found it to be a fantastic piece of software.
I am working on some autopilot control algorithms, completely external to FlightGear, however I would like to use FlighGear to test some of these algorithms and visualise the flight. I am currently able to get data out of flight gear into my autopilot environment using the native-fdm protocol, over a network socket. However, to complete the control loop I need to be able to manipulate the aircraft control surfaces externally. So I have just started investigating the native-ctrls protocol which seems great, except I have some concerns.. The FGNetCtrls structure in net_ctrls.hxx include the following fields which I do NOT want to externally manipulate: // wind and turbulance double wind_speed_kt; double wind_dir_deg; double turbulence_norm; // temp and pressure double temp_c; double press_inhg; // other information about environment double hground; // ground elevation (meters) double magvar; // local magnetic variation in degs. Is there any way I can control the ailerons/elevator/rudder etc. etc. through this protocol, without having to overwrite the current wind speed / direction / temperature etc. They seem out of place since I would have thought they were things which can't be externally controlled - or am I misunderstanding the purpose of these fields, or the purpose of the native-ctrls protocol? Any input would be appreciated Cheers James W ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
