* Hans Fugal -- Saturday 13 October 2007:
> Also, I don't know if you're taking wind speed into account
> but that could be an important consideration.
No, that's not done yet. Would be easy to add, but this would
then have to depend on the size/mass of the aircraft, so we'd
need this info in the
Am Samstag 13 Oktober 2007 schrieb Melchior FRANZ:
> You are a bit behind ... :-)
Dang, my last cvs up was 2 days ago. Probably I should setup a 30 min cron
job... ;-)
> > Taking wind into account is impossible with the current startup [...]
>
> Behind again ... that works already. Look into $
You are a bit behind ... :-)
* Thomas Förster -- Saturday 13 October 2007:
> The weights may be set using the property tree:
>
> /tmp/runway-search/length [...]
That's now:
/sim/airport/runways/search/length-weight (0.01)
/sim/airport/runways/search/width-weight(0.01)
/sim/airport/
Am Samstag 13 Oktober 2007 schrieb Hans Fugal:
> It would be nice if the weightings could vary depending on the
> aircraft. For example, a J3 Cub would care a lot more about wind
> alignment and be perfectly happy with a grass strip, but a big jet
> would need the long/wide runway no matter what th
It would be nice if the weightings could vary depending on the
aircraft. For example, a J3 Cub would care a lot more about wind
alignment and be perfectly happy with a grass strip, but a big jet
would need the long/wide runway no matter what the wind. Also, I don't
know if you're taking wind speed
* Thomas Förster -- Friday 12 October 2007:
> Using the proposed change it is possible to get the original
> behaviour of the method (FGRunwayList::search) with a weight
> set of (0,0,0,1).
The idea was to hard-code the weights once we are happy with
the results, which is why I didn't consider th
Am Donnerstag 04 Oktober 2007 schrieb Melchior FRANZ:
> The last point is done with weighting factors, which are for
> now configurable in the property tree and might need some more
> adjustment. Please check problem cases and report any unwanted
> behavior.
I'd prefer the evaluation formula chang
On Thursday 04 October 2007 20:06, Melchior FRANZ wrote:
> I've today changed the runway selection behavior. In the past,
> runway 28R was pre-selected in preferences.xml, and a heading
> of 270 was hard-coded in options.xml.
>
> So, if you started from another airport, fgfs first checked for
> a r
I've today changed the runway selection behavior. In the past,
runway 28R was pre-selected in preferences.xml, and a heading
of 270 was hard-coded in options.xml.
So, if you started from another airport, fgfs first checked for
a runway 28R, and if there was none, chose the runway with
heading clos
9 matches
Mail list logo
