[Flightgear-devel] Problem with --airport-id=KDCA

2002-06-13 Thread Jay Hlavaty
Well, duh, after trying uppercase airport identifiers, I see that you are absolutely right -- they work fine.

However, I must confess that it seems inconsistent.  According to the log, part of the startup processing is able to correctly identify kdca in lower case -- note the correct position information even with LC!  It looks like the airport location processing can handle lowercase, but the runway processing cannot?  (Haven't checked source yet).

BTW, are all airport identifiers A-Z or 0-1?  Do you think that it would be a good idea to just convert lowercase to upper for --airport-id option or is it better to just make the docs/command line help a bit clearer for this command? For the clueless outthere, myself included. 8-(

Thanks also for the scenery pointer, I think that I've got the right scenery downloaded (w080n40), though I forgot to mention that, sorry!

Position for kdca is (-77.0377, 38.8521)

TIA, Ima

* [EMAIL PROTECTED] (ima sudonim) [2002.06.12 21:37]:
> Way cool app, ya'll, but I'm having some problems with airport ids.
> 
> Attempting to run ./fgfs with any --airport-id option causes errors as 
> shown below.
> The runway information is bad, I'm guessing.  I am using base 7.11.pre1 
> (the only one supported by the latest cvs sources that I dled).  
> Downloaded everything from CVS again and recompiled.  Am still getting 
> the same error.
> 
> I'm new at this and am unsure how to even begin.  I've tried KJFK, KDCA 
> (washington, DC) and others to the same effect.  If I use the default 
> airport (KSFO), things start OK:
> 
> *KSFO info is:
> NewAirportInit KSFO
> Attempting to set starting position from runway code KSFO heading 270
> Runway 01L heading = 27.7 diff = 117.7
> Runway -01L heading = 207.7 diff = 62.3
> Runway 01R heading = 27.71 diff = 117.71
> Runway -01R heading = 207.71 diff = 62.29
> Runway 10L heading = 117.9 diff = 152.1
> Runway -10L heading = 297.9 diff = 27.9
> Runway 10R heading = 117.9 diff = 152.1
> Runway -10R heading = 297.9 diff = 27.9
> closest runway = 10L + 180
> runway =  -122.375, 37.6211 length = 1808.99 heading = 117.9
> Position for KSFO is (-122.357, 37.6135) new heading is 297.9
> Searching for airport code = KSFO
> idx = 11133
> Position for KSFO is (-122.375, 37.619)
> 
> *KDCA info is:
> NewAirportInit kdca

Note that you are not using all caps.  Try running with "KDCA" like you
have in the Subject.  I'm not at home right now, so I can't test this.
-- 
Cameron Moore
[ My grandfather died when he was just an infant. ]










[Flightgear-devel] problem with --airport-id=KDCA

2002-06-12 Thread ima sudonim

Hi,

Way cool app, ya'll, but I'm having some problems with airport ids.

Attempting to run ./fgfs with any --airport-id option causes errors as 
shown below.
The runway information is bad, I'm guessing.  I am using base 7.11.pre1 
(the only one supported by the latest cvs sources that I dled).  
Downloaded everything from CVS again and recompiled.  Am still getting 
the same error.

I'm new at this and am unsure how to even begin.  I've tried KJFK, KDCA 
(washington, DC) and others to the same effect.  If I use the default 
airport (KSFO), things start OK:

*KSFO info is:
NewAirportInit KSFO
Attempting to set starting position from runway code KSFO heading 270
Runway 01L heading = 27.7 diff = 117.7
Runway -01L heading = 207.7 diff = 62.3
Runway 01R heading = 27.71 diff = 117.71
Runway -01R heading = 207.71 diff = 62.29
Runway 10L heading = 117.9 diff = 152.1
Runway -10L heading = 297.9 diff = 27.9
Runway 10R heading = 117.9 diff = 152.1
Runway -10R heading = 297.9 diff = 27.9
closest runway = 10L + 180
runway =  -122.375, 37.6211 length = 1808.99 heading = 117.9
Position for KSFO is (-122.357, 37.6135) new heading is 297.9
Searching for airport code = KSFO
idx = 11133
Position for KSFO is (-122.375, 37.619)

*KDCA info is:
NewAirportInit kdca
Attempting to set starting position from runway code kdca heading 270
closest runway =  + 0
runway =  278224, 5.39338e-315 length = 8.89328e-315 heading = 180
Position for kdca is (277864, 4.52183e-05) new heading is 2.96439e-321
Searching for airport code = kdca
idx = 9802
Position for kdca is (-77.0377, 38.8521)

What am I doing wrong? TIA

BTW, how do I build a debug version of FGFS and how can I load a source 
file to examine in GDB. 8-)

Thanks! Ima


vv- some log information related to kdca

[localhost:fgdev/src/flightgear] root# src/main/fgfs --airport-id=kdca
Using Mac OS X hack for initializing C++ stdio...
FlightGear:  Version 0.7.11pre1
Built with GNU C++ version 2.95

Scanning for root: command line
fg_root = /Users/joeh/Desktop/FlightGear/fgdev/lib/base
Reading global preferences
Finished Reading global preferences
Reading default aircraft: c172 from 
/Users/joeh/Desktop/FlightGear/fgdev/lib/base/Aircraft/c172-set.xml
Processing command line arguments
Finished command line arguments
Opening a window: 800x600
Rage 128 OpenGL Engine
Max texture size = 1024
Depth buffer bits = 16
NewAirportInit kdca
Attempting to set starting position from runway code kdca heading 270
closest runway =  + 0
runway =  278224, 5.39338e-315 length = 8.89328e-315 heading = 180
Position for kdca is (277864, 4.52183e-05) new heading is 2.96439e-321
Searching for airport code = kdca
idx = 9802
Position for kdca is (-77.0377, 38.8521)
Initializing Time
Current greenwich mean time = Wed Jun 12 23:44:42 2002

Current local time  = Wed Jun 12 19:44:42 2002

snip

Panel visible = 0
Loading deferred texture
Tile not found (Ok if initializing)
Attempting to schedule tiles for bogus latitude and
longitude.  This is a FATAL error.  Exiting!
scheduling needed tiles for 277864 4.52183e-05
load() base = /Users/joeh/Desktop/FlightGear/fgdev/lib/base/Scenery
Loading tile 
/Users/joeh/Desktop/FlightGear/fgdev/lib/base/Scenery/w060n00/w056n00/2037376
Tile not found (Ok if initializing)
load() base = /Users/joeh/Desktop/FlightGear/fgdev/lib/base/Scenery
Loading tile 
/Users/joeh/Desktop/FlightGear/fgdev/lib/base/Scenery/w060n00/w056n00/2037384
Refreshing timestamps for 277864 0.0625
Attempting to schedule tiles for bogus latitude and
longitude.  This is a FATAL error.  Exiting!
scheduling needed tiles for 277864 4.52183e-05
Tile not found (Ok if initializing)
load() base = /Users/joeh/Desktop/FlightGear/fgdev/lib/base/Scenery
Loading tile 
/Users/joeh/Desktop/FlightGear/fgdev/lib/base/Scenery/w060s10/w056s01/2037369
Updating light parameters.
   Sun angle = 117.739
   ambient = 0.15  diffuse = 0  sky = 0.09
Tile not found (Ok if initializing)
load() base = /Users/joeh/Desktop/FlightGear/fgdev/lib/base/Scenery
Loading tile 
/Users/joeh/Desktop/FlightGear/fgdev/lib/base/Scenery/w060n00/w056n00/2037385


My gunzipped default.apt airport information has KDCA as
A KDCA  38.852087 -077.037712 16 CYN Washington National

runways.mk4 has (around KDCA, unsure what the file's structure is):

KDCA

No airports except the default work for me.




___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



Re: [Flightgear-devel] problem with --airport-id=KDCA

2002-06-12 Thread Jim Wilson

ima sudonim [EMAIL PROTECTED] said:

/Users/joeh/Desktop/FlightGear/fgdev/lib/base/Scenery/w060n00/w056n00/2037384
 Refreshing timestamps for 277864 0.0625
 Attempting to schedule tiles for bogus latitude and
 longitude.  This is a FATAL error.  Exiting!
 scheduling needed tiles for 277864 4.52183e-05
 Tile not found (Ok if initializing)
 load() base = /Users/joeh/Desktop/FlightGear/fgdev/lib/base/Scenery
 Loading tile 

Thanks for the compliments.  Looks like you need to download some scenery data
(only KSFO area is in the base package).

Here is the link:

http://www.flightgear.org/Downloads/world-scenery.html

Click on the square that represents the region you wish to download.

Best,

Jim

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



Re: [Flightgear-devel] problem with --airport-id=KDCA

2002-06-12 Thread Cameron Moore

* [EMAIL PROTECTED] (ima sudonim) [2002.06.12 21:37]:
 Way cool app, ya'll, but I'm having some problems with airport ids.
 
 Attempting to run ./fgfs with any --airport-id option causes errors as 
 shown below.
 The runway information is bad, I'm guessing.  I am using base 7.11.pre1 
 (the only one supported by the latest cvs sources that I dled).  
 Downloaded everything from CVS again and recompiled.  Am still getting 
 the same error.
 
 I'm new at this and am unsure how to even begin.  I've tried KJFK, KDCA 
 (washington, DC) and others to the same effect.  If I use the default 
 airport (KSFO), things start OK:
 
 *KSFO info is:
 NewAirportInit KSFO
 Attempting to set starting position from runway code KSFO heading 270
 Runway 01L heading = 27.7 diff = 117.7
 Runway -01L heading = 207.7 diff = 62.3
 Runway 01R heading = 27.71 diff = 117.71
 Runway -01R heading = 207.71 diff = 62.29
 Runway 10L heading = 117.9 diff = 152.1
 Runway -10L heading = 297.9 diff = 27.9
 Runway 10R heading = 117.9 diff = 152.1
 Runway -10R heading = 297.9 diff = 27.9
 closest runway = 10L + 180
 runway =  -122.375, 37.6211 length = 1808.99 heading = 117.9
 Position for KSFO is (-122.357, 37.6135) new heading is 297.9
 Searching for airport code = KSFO
 idx = 11133
 Position for KSFO is (-122.375, 37.619)
 
 *KDCA info is:
 NewAirportInit kdca

Note that you are not using all caps.  Try running with KDCA like you
have in the Subject.  I'm not at home right now, so I can't test this.
-- 
Cameron Moore
[ My grandfather died when he was just an infant. ]

___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel



[Flightgear-devel] Problem with --airport-id=KDCA

2002-06-12 Thread ima sudonim
 Well, duh, after trying uppercase airport identifiers, I see that you are absolutely right -- they work fine.

However, I must confess that it seems inconsistent.  According to the log, part of the startup processing is able to correctly identify kdca in lower case -- note the correct position information even with LC!  It looks like the airport location processing can handle lowercase, but the runway processing cannot?  (Haven't checked source yet).

BTW, are all airport identifiers A-Z or 0-1?  Do you think that it would be a good idea to just convert lowercase to upper for --airport-id option or is it better to just make the docs/command line help a bit clearer for this command? For the clueless outthere, myself included. 8-(

Thanks also for the scenery pointer, I think that I've got the right scenery downloaded (w080n40), though I forgot to mention that, sorry!

Position for kdca is (-77.0377, 38.8521)

TIA, Ima

*  (ima sudonim) [2002.06.12 21:37]:
> Way cool app, ya'll, but I'm having some problems with airport ids.
> 
> Attempting to run ./fgfs with any --airport-id option causes errors as 
> shown below.
> The runway information is bad, I'm guessing.  I am using base 7.11.pre1 
> (the only one supported by the latest cvs sources that I dled).  
> Downloaded everything from CVS again and recompiled.  Am still getting 
> the same error.
> 
> I'm new at this and am unsure how to even begin.  I've tried KJFK, KDCA 
> (washington, DC) and others to the same effect.  If I use the default 
> airport (KSFO), things start OK:
> 
> *KSFO info is:
> NewAirportInit KSFO
> Attempting to set starting position from runway code KSFO heading 270
> Runway 01L heading = 27.7 diff = 117.7
> Runway -01L heading = 207.7 diff = 62.3
> Runway 01R heading = 27.71 diff = 117.71
> Runway -01R heading = 207.71 diff = 62.29
> Runway 10L heading = 117.9 diff = 152.1
> Runway -10L heading = 297.9 diff = 27.9
> Runway 10R heading = 117.9 diff = 152.1
> Runway -10R heading = 297.9 diff = 27.9
> closest runway = 10L + 180
> runway =  -122.375, 37.6211 length = 1808.99 heading = 117.9
> Position for KSFO is (-122.357, 37.6135) new heading is 297.9
> Searching for airport code = KSFO
> idx = 11133
> Position for KSFO is (-122.375, 37.619)
> 
> *KDCA info is:
> NewAirportInit kdca

Note that you are not using all caps.  Try running with "KDCA" like you
have in the Subject.  I'm not at home right now, so I can't test this.
-- 
Cameron Moore
[ My grandfather died when he was just an infant. ]