Erik Hofman writes:
> Ronny Standtke wrote:
> > Hi everybody,
>
> > I could not get the scenario to start from chosen coordinates. I downloaded
> > and installed the local area (e000n40.tar.gz) and started FlightGear, e.g.
> > like this:
> > $ fgfs --lat=47 --lon=7.5
> > After the progrum run I discovered by browsing the internal properties that
> > the longitude and the latitude where correct but the altitude was at -9999
> > feet so I started FlightGear like this:
> > $ fgfs --lat=47 --lon=7.5 --altitude=4000
> > But this didnt change a thing.
>
> You need to add -in-air to disable the ground initialization
> routines.
Specifying --altitude=4000 implies --in-air so that shouldn't be
needed.
> BTW. There is a discussion about this subject in the
> flightgear-devel mailing list right now. Maybe you should subscribe
> to that list as well?
Recently?
I believe the issue here is that if you start exactly on a tile
boundary, the ground intersection code might not pick up an
intersection. This doesn't ever seem to surface in flight because if
you do happen to hit it exactly, you won't be there for more than one
frame. If you nudge the startup location a bit so you are not on a
tile boundary, that should do the trick.
fgfs --lat=47.001 --lon=7.501 --altitude=4000 --vc=90
Note that you can specify an initial aircraft speed in knots with the
--vc= option. Otherwise it's like you are dropped out of the sky
which often isn't what you want.
Regards,
Curt.
--
Curtis Olson HumanFIRST Program FlightGear Project
Twin Cities curt 'at' me.umn.edu curt 'at' flightgear.org
Minnesota http://www.flightgear.org/~curt http://www.flightgear.org
_______________________________________________
Flightgear-users mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-users
