On 5/7/07, Adam Dershowitz wrote:
I have dug into this a little further and found something odd.
I found that the NMEA data is driven by /velocities/speed-east-fps
and /velocities/speed-north-fps. So I calculated these and added
them to my csv data file, and the playback config file. The oddity
is that even though my file now has them, these values are not
changing in FG. They remain 0. I am using the null FDM and a the
generic protocol, and all else seems to be working correctly, except
on the NMEA data, that is used by Atlas among other things, the
heading and speed are showing as zero.
Any ideas why I can't get the generic protocol to change these two
velocities when it can change other values just fine?
I don't recall about this specific set of properties, but you have to be
careful ... some fdm properties are derived from other properties and auto
calculated. I believe that most of the logic for what is computed from what
can be found in src/fdm/flight.[ch]xx
This code traces back to some of the earliest days of FlightGear so it's a
bit clunky in spots, but it works.
Regards,
Curt.
--
Curtis Olson - University of Minnesota - FlightGear Project
http://baron.flightgear.org/~curt/ http://www.humanfirst.umn.edu/
http://www.flightgear.org
Unique text: 2f585eeea02e2c79d7b1d8c4963bae2d
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
