On May 7, 2007, at 3:32 PM, Curtis Olson wrote:
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 da
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 oddit
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 n
I am driving FlightGear using a text file. That data that I have
includes magnetic heading, but not true heading, so I am supplying
that. All seems to be working correctly in FlightGear. But if I try
to display the data using Atlas the heading remains 0 degrees ( --
nmea=socket,out,0.5,1
4 matches
Mail list logo