On Monday, November 05, 2012 20:25:13 James Turner wrote:
Hmmm, no is the quick answer - if you can wait a little, I'll try to
replicate this tomorrow.
Regards,
James
Found the reason myself: in Instrumentation/gps.cxx line 771:
if (_last_speed_kts 60) {
// need valid leg course and
Could someone provide me with some clues here? Is there any specific
thing the GPS needs to sequence to the next waypoint?
Short reply since I'm at FSWeekend still - can reply in more detail
tomorrow. The most likely answer is that the route-manager or GPS is not
activated -
On Sunday, November 04, 2012 09:49:25 James Turner wrote:
Short reply since I'm at FSWeekend still - can reply in more detail
tomorrow. The most likely answer is that the route-manager or GPS is not
activated - activating GPS leg mode should set the route-manger mode
automatically, I think.
On 5 Nov 2012, at 18:08, Adrian Musceac wrote:
To be more precise, the gps sequencing problem only appears at the second
waypoint in the list.
With loglevel info, I get the following messages at waypoint #1:
GPS doing overflight sequencing
'saw current WP changed, now 1'
GPS waypoint
On 3 Nov 2012, at 08:24, Adrian Musceac kanto...@gmail.com wrote:
Hi all,
I've written a little interface to control Flightgear via an OpenStreetMap
interface (at the moment, it can place the ufo at any position on the map,
place some virtual radio stations on the ground near the ufo,
Hi all,
I've written a little interface to control Flightgear via an OpenStreetMap
interface (at the moment, it can place the ufo at any position on the map,
place some virtual radio stations on the ground near the ufo, and also place
waypoints for the ufo to follow along a path on the map).
6 matches
Mail list logo
