On Sun, 2 Jan 2005 16:57:17 -0000
Bill Rankin wrote:
>
> Hi,

Hi.  Please try and choose informative subject lines so people who
don't follow everything in the mailing list can decide whether to go
ahead and read your post . . .

 
> I have been having difficulties with scenery files when I download them.
>  They only seem to work when I expand them to
>  flightgear/scenery/terrain.  Is this the correct place for them?

Scenery/Terrain is the correct location, yes.


>  Also
>  when I expand them, somtimes they work and othertimes not.

Uh, OK.  Without more information than that, it's difficult to know
what to say in reply.  What do you mean by "not working"?  How are
you expanding them?  Where are you placing them?  How are you telling
FlightGear where to find them?  How does FlightGear fail?  Does it
provide any error messages?  If so, what?  If not, have you tried
increasing the level of detail of messages it gives (through the
command line parameters)?  Please help us help you.


>  Where can
>  I get cities like New York with good graphics?

I'm not sure what you mean by this.  If you're asking about ground
scenery like buildings and detailed roads and so forth, you can't.
Where they exist (e.g. the San Francisco bay area), stuff like ground
structures exist because users like you and me have stepped forward
to create them and make them available.  Nobody has done this with
NYC, so NYC doesn't have such structures available.  This is definitely
an area where users can become contributors to the project; and if it
interests you, I encourage you to jump in!

-c

-- 
Chris Metzler                   [EMAIL PROTECTED]
                (remove "snip-me." to email)

"As a child I understood how to give; I have forgotten this grace since I
have become civilized." - Chief Luther Standing Bear

Attachment: pgpDG8LOldqiH.pgp
Description: PGP signature

_______________________________________________
Flightgear-users mailing list
Flightgear-users@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to