Thank you Thomas for the reply....

Thomas Förster wrote:
Am Dienstag 31 Mai 2005 19:52 schrieb JB:
  
...  I've download 
the latest version and having been having a ball with it, but I've run
into some problems.  Specifically scenery related.  I've downloaded
scenery for Indianapolis and was trying to fly out of Indianapolis Int'l
(KIND), but when FG loads it put's me in the middle of what looks like,
an ocean.  I checked the apt.dat.gz file and KIND is indeed listed, so
why does it put me in the middle of nowhere?
    

Where exactly did you unpack the scenery tar.gz? Usually the Scenery directory 
in $FG_ROOT contains the subdirs Terrain and Objects. You have to unpack into 
the Terrain directory for things to work correctly.

  
I'm using the default scenery directories, and I did unpack the file to the terrain <DIR>.  Like I said, when I do specify KIND airport, It put's me in the middle of an ocean.  What I failed to mention was; if I fly east (KIND is on the city's west side outside the I-465 beltway, I will eventually fly over terrain.  No cityscape, a few scattered generic buildings here and there and what I think might be I-465, which is what I expected.  Those of us who live in "fly over country" ;-) tend to get overlooked in many areas, so I didn't expect much scenery design.  I just wanted to fly out of some local airports, so if and when I do take up the real thing, I'll have some idea what's going on.  And who knows, I might try my hand at building a cityscape....

An even better approach is to install the Scenery elsewhere 
(e.g. /usr/local/FGScenery) and set the configuration options in ~/.fgfsrc 
accordingly. Putting a "--fg-scenery=/usr/local/FGScenery" line in it should 
suffice. That way you don't mix the standard FGFS data with the additional 
sceneries.

  
Well, I don't mind mixing downloaded scenery with base package files, at least in scenery design.  I might try that approach as I get into plane, or more specifically, panel mods, but scenery is scenery, and If I want to try cross country, I'd need them all in the same directory structure anyway. Right?

  
BTW:  Regarding the apt.dat file; FAQ's and other docs list the format
differently than what is in it.  By that I mean, R, A and other record
identifiers listed in the docs are not present in the current file.  Did
the format change and the docs not catch up with it?
    

Exactly. With v0.9.8 FG switched to the format that X-Plane uses which saves 
conversion, as the X-Plane data was used anyway. The file format is 
documented at http://x-plane.org/home/robinp/FileDef.htm

  
Okay, that explains much.  Thanks for the link, that helps.

  
Do I have to rebuild the downloaded scenery file to make it mesh with
the apt.dat file?  If so, how do you do that?  The docs are somewhat
vague in that area.
    

You shouldn't have to. Rebuilding scenery tiles is a slow and tedious process.
  

I read somewhere that for scenery files, there is a hole left where the airport is supposed to go, rather than an overlay on existing terrain.  Is it possible that with the change in the airport data format, that some scenery files from the GUI or FTP sites have not yet been regenerated with the new format thereby leaving this "hole" where an airport should be?

If so, what is the procedure for rebuilding scenery.  One, it would help to start documenting it and the mailing list seems like a good place to start, and two, I have 4 machines on a little home network, one of which is my server, and all it really does is serve up SAMBA disks for the other's, not too taxing, so it wouldn't be a problem for me to have it crunch away on a scenery file for however long it takes.  All I would need is the procedure.

Anyway, thanks again for the info.

JB
Cheers
Thomas 


_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d

  
_______________________________________________
Flightgear-users mailing list
[email protected]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to