Re: [Flightgear-devel] Threshold bug when using custom scenery enable
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=5t=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 Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Threshold bug when using custom scenery enable
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=5t=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 Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- 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 Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] Threshold bug when using custom scenery enable
Thanks again Syd. As Martin said, displacements must be zero, unless it is known to have a displaced threshold or stopway. Runway spawn issue: Many of the threshold.xml files have offsets, which cause the crash on spawn at airports like KSFO, where it drops you in the water short of 28R. 91 meters short, to be exact. Both Scenery/Airports/ and Scenery-TerraSync/Airports have this offset. At JFK it was 1000 meters. threshold lon-122.357141284717/lon lat37.6135315946418/lat rwy28R/rwy hdg-deg297.90/hdg-deg displ-m91/displ-m stopw-m0/stopw-m /threshold Tower viewpoint issue: twr.xml files are incorrect, showing either sub-terrain viewpoints or ground zero viewpoints. KJFK: twr lon-73.781647001/lon lat40.64341/lat elev-m0.00/elev-m /twr Proper elevation should be 87.78 meters. KSLC is off by 1300 meters. Who or how can these files be corrected? (I am assuming they were auto-generated) Thanks, Peter On Jan 31, 2010, at 5:58 PM, Peter Brown wrote: Hey guys, I'm finding an issue using --prop:/sim/paths/use-custom-scenery-data=true Thresholds on a number of test airports are off by a large degree, and the tower viewpoint is an issue at some. When use-custom-scenery-data=false spawn locations and tower viewpoints are correct. Test photos are linked here: http://s512.photobucket.com/albums/t325/barefootr/Flightgear/Threshold%20Bug/ KSFO spawns you in the water off 28R. Tower viewpoint appears correct. -- 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 Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] Threshold bug when using custom scenery enable
Hey guys, I'm finding an issue using --prop:/sim/paths/use-custom-scenery-data=true Thresholds on a number of test airports are off by a large degree, and the tower viewpoint is an issue at some. When use-custom-scenery-data=false spawn locations and tower viewpoints are correct. Test photos are linked here: http://s512.photobucket.com/albums/t325/barefootr/Flightgear/Threshold%20Bug/ KSFO spawns you in the water off 28R. Tower viewpoint appears correct. KSLC appears to spawn same as normal, but tower viewpoint is far underground. Changing tower height in apt.dat file does not affect viewpoint. KBTV spawns off the end of runway 33, similar to KSFO. Tower viewpoint appears correct. KJFK spawns far off the end of 31L, and tower viewpoint is at zero (0) altitude. (Tower height is 320' in apt.dat, and shows correct when --prop:/sim/paths/use-custom-scenery-data=false) Oddly, other runway spawn locations appear to be unaffected. Issue has tested valid so far using: - Mac OS 10.6.2 (Snow Leopard) and Tat's 2.0.0-pre1(273) - Mac OS 10.4.11 and Tat's 2.0.0-pre1(273) Anyone know what's going on? Thanks, Peter-- 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 Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
