Re: [Flightgear-devel] Threshold bug when using custom scenery enable

[Peter B. <smo...@ad...>]

Sorry about the duplicate email, looks like the first email finally showed up from a week ago.

Yves,  as you said, KSFO is part of the default scenery.  I'm not following your thought on the forum thread.  As far as I can tell this issue has nothing to do with an "airport check".  I provided data to show the issue/bug.

The issue, to paraphrase, is that when using Martin Spott's recommendation that those "using terrasync should also use --prop:/sim/paths/use-custom-scenery-data=true", causes a spawn issue.  If you noticed in the data provided, this is an issue with not only an early 2.0.0 release, but also with 1.9.1.

Syd- thanks for providing a path on tower data for custom-scenery.

Peter.


On Feb 2, 2010, at 4:55 AM, HB-GRAL wrote:

> Peter Brown schrieb:
>> Changing tower height in apt.dat file does not affect viewpoint.
> 
> Peter,
> 
> Changes of properties like viewpoint in apt.dat takes no effect.
> 
> Using a wide range of custom scenery is also not a good starting point 
> for debugging a release like the pre-alpha on OSX. But KSFO is part of 
> the default scenery, yes.
> 
> There is a recent thread about "new" airports in "Scenery Enhancement". 
> You can use this also for posting "airport checks" or "updates".
> http://www.flightgear.org/forums/viewtopic.php?f=5&t=6749
> 
> Thanks - Yves
> 
> ------------------------------------------------------------------------------
> The Planet: dedicated and managed hosting, cloud storage, colocation
> Stay online with enterprise data centers and the best network in the business
> Choose flexible plans and management services without long-term contracts
> Personal 24x7 support from experience hosting pros just a phone call away.
> http://p.sf.net/sfu/theplanet-com
> _______________________________________________
> Flightgear-devel mailing list
> Fli...@li...
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel