--- "Curtis L. Olson" <[EMAIL PROTECTED]> wrote:
> Melchior FRANZ wrote:
>
> >Maybe I missed something, but as far as I've understood this thread
> >is not about renaming $FG_ROOT/Scenery/.
Well ... it could be :)
My aim is to write a section in the Gettings Started Guide so that a new
user can set up their directories and FG_SCENERY variable to the correct
values. This doesn't have to be the same setup as everyone uses (after
all, that's why we have FG_SCENERY)
> >It's only about whether to
> >suggest a standard in the user documentation for where to install
> >additional scenery, especially when using terrasync. Dumping terrasync
> >fetched data into $FG_ROOT/Scenery/ is a Really Bad Idea[TM].
I'm groping in the dark here as I'm not familiar with terrasync. Am I
correct in thinking that someone using terrasync should have their
terrasync data in a different directory from their directly-downloaded
10x10 scenery?
If so, is the convention to name the directories as follows:
$FG_ROOT/data/Scenery - standard SF bay scenery included in base package
$FG_ROOT/Scenery - scenery downloaded in 10x10 chunks
$FG_ROOT/WorldScenery - scenery downloaded by terrasync
or is WorldScenery just a different convention for $FG_ROOT/Scenery?
> Not to get overly pedantic, but someone suggested
> .../.../WorldScenery/{Terrain|Objects} for *nix platforms, and the
> person doing the documentation work said "ok", so my response was a plea
> to keep things consistent across platforms and just use
> $FG_ROOT/data/Scenery as the root of the scenery tree.
Now I'm getting even more confused. I thought $FG_ROOT/data/Scenery was
just to contain the base package scenery for the SF Bay area.
Maybe this is a can of worms I don't have enough understanding to want to
open ...
-Stuart
___________________________________________________________
Yahoo! Model Search 2005 - Find the next catwalk superstars -
http://uk.news.yahoo.com/hot/model-search/
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
