Thanks Tim!
On Wed, 15 Aug 2007, Reagan Thomas wrote:
It looks like this fix needs to be applied to the weather interpolation
in the plib branch also.
Yes, it is needed also in the plib branch. I have tested the patch there
too.
Cheers,
Anders
--
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed; thanks.
Tim
Anders Gidenstam wrote:
On Sun, 12 Aug 2007, Hans Fugal wrote:
That's because there is no custom comparison predicate for comparing
bucket*. vectorbucket* is just a list of pointers, and so uses the
sort order for
Tim Moore wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Committed; thanks.
Tim
It looks like this fix needs to be applied to the weather interpolation
in the plib branch also.
Anders Gidenstam wrote:
On Sun, 12 Aug 2007, Hans Fugal wrote:
That's because there is no custom
--- Georg Vollnhals wrote:
I applied your patch and just made a flight from EDDV to EDDW (with
--enable-real-weather-fetch) through several weather-zones (which I
could recognize by the changing cloud display).
First you cured the faulty behaviour with your patch :-). And the
weather
On Wed, 8 Aug 2007, Stuart Buchanan wrote:
I'd be very grateful if you could help me diagnose the problem, as I did
quite a lot of testing, but didn't encounter this myself.
One possibility is that my interpolation is fighting with something else
trying to write to the weather properties.
On 8/12/07, Anders Gidenstam [EMAIL PROTECTED] wrote:
On Wed, 8 Aug 2007, Stuart Buchanan wrote:
I'd be very grateful if you could help me diagnose the problem, as I did
quite a lot of testing, but didn't encounter this myself.
One possibility is that my interpolation is fighting with
On Sunday 12 August 2007 13:48, Anders Gidenstam wrote:
On Wed, 8 Aug 2007, Stuart Buchanan wrote:
I'd be very grateful if you could help me diagnose the problem, as I did
quite a lot of testing, but didn't encounter this myself.
One possibility is that my interpolation is fighting with
On Sun, 12 Aug 2007, Hans Fugal wrote:
That's because there is no custom comparison predicate for comparing
bucket*. vectorbucket* is just a list of pointers, and so uses the
sort order for pointers. You'd have to set up an STL functor to sort
them, which is ugly and difficult (but certainly
Anders Gidenstam schrieb:
On Sun, 12 Aug 2007, Hans Fugal wrote:
That's because there is no custom comparison predicate for comparing
bucket*. vectorbucket* is just a list of pointers, and so uses the
sort order for pointers. You'd have to set up an STL functor to sort
them, which is ugly
Hi Hans, Georg,
--- Hans Fugal wrote:
Hi Stuart,
On 8/8/07, Stuart Buchanan wrote:
I'd be very grateful if you could help me diagnose the problem, as I
did quite a lot of testing, but didn't encounter this myself.
Happy to help.
One possibility is that my interpolation is fighting
Hi Stuart,
I saw the variable wind in the METAR after I had posted, it is indeed
a red herring. It happens (as you can see with Georg's post) no matter
what the wind.
We have some more information from IRC. The properties you asked for
don't change, as you're aware, but some other properties
Hi All,
--- Hans Fugal wrote:
I did some more investigating, and discovered that it is still
happening even fair weather, it's just that the wind speed is low
enough that the effect isn't very pronounced. Also, taxi up to a
windsock and watch the effect.
I'm very sorry you are seeing
On Wed, 8 Aug 2007, Stuart Buchanan wrote:
I'd be very grateful if you could help me diagnose the problem, as I did
quite a lot of testing, but didn't encounter this myself.
One possibility is that my interpolation is fighting with something else
trying to write to the weather properties.
Hans Fugal wrote:
Semantically, am I right that for weather scenarios, METAR is the real
weather, Thunderstorm is thunderstorm-like weather (no relation to
real weather?), fair is easy flying (again, no relation to real
weather?), and none means no scenario (manual control?). That's what I
think
On 8/8/07, Harald JOHNSEN [EMAIL PROTECTED] wrote:
This is right, except that in the 'none' scenario the weather is still
updated by the metar if metar is enabled.
I can not remember if this is a bug or a feature.
If I may vote, I call it a bug. If there is no difference between
none and
Hi Stuart,
On 8/8/07, Stuart Buchanan [EMAIL PROTECTED] wrote:
I'd be very grateful if you could help me diagnose the problem, as I did
quite a lot of testing, but didn't encounter this myself.
Happy to help.
One possibility is that my interpolation is fighting with something else
trying
Could you explain what you are seeing in terms of wind direction and
strength? Is it:
- oscillating in direction and/or speed
- rotating continually?
- chaotic?
Are you seeing the problem generally, or only when the METAR changes as
you fly from one zone to another?
Generally,
Sorry, my FIRST reply was sent unfinished by accident!
Here is the right one :-)
--
Due to the special weather conditions tonight (only IFR possible) the
formerly described effect was
Laurence Vanek schrieb:
Hans Fugal wrote:
Flying in the vicinity of KCSQ just now (KCSQ 062055Z AUTO 16006KT
10SM CLR 26/23 A2979 RMK AO2) in both the pa28-161 and j3cub, I
noticed some kind of weather-related problems. I'm afraid it was
probably weather interpolation-related.
My plane
I did some more investigating, and discovered that it is still
happening even fair weather, it's just that the wind speed is low
enough that the effect isn't very pronounced. Also, taxi up to a
windsock and watch the effect.
Incidentally, I was trying to add a layer of clouds with
Flying in the vicinity of KCSQ just now (KCSQ 062055Z AUTO 16006KT
10SM CLR 26/23 A2979 RMK AO2) in both the pa28-161 and j3cub, I
noticed some kind of weather-related problems. I'm afraid it was
probably weather interpolation-related.
My plane was being tossed around like a salad, but as you can
Hans Fugal wrote:
Flying in the vicinity of KCSQ just now (KCSQ 062055Z AUTO 16006KT
10SM CLR 26/23 A2979 RMK AO2) in both the pa28-161 and j3cub, I
noticed some kind of weather-related problems. I'm afraid it was
probably weather interpolation-related.
My plane was being tossed around like
22 matches
Mail list logo
