I have a similar problem with KSJC. I'm running fgfs 0.91, with the 0.90 base package, the KSJC photo-realistic scenery version 2.0, and lots of scenery for the northern part of the western hemisphere.
It appears that I'm underground. The altimeter reads 0, but the "radar altimeter" reads something a little over 32800 feet. The aircraft is still stuck, even if I supply a "--altitude=30000" parameter. I can use the autopilot to fly to KSJC, though, without trouble if I start at another airport. I didn't submit this yet because my mix of versions could conceivably cause odd behavior, and I haven't looked into it. -Luke On Mon, 2002-12-16 at 18:18, Curtis L. Olson wrote: > Tommy, > > Here's a couple things you could try. > > - specify a starting airport: > > fgfs --airport=ENTC > > We have quite a few Norwegian airports in our database. > > - If you want to specify a lat/lon try avoiding exact whole number > coordinates. Instead of --lat=59 --lon=10 try --lat=59.001 > --lon=10.001 (or better yet, start at an aiport.) > > Regards, > > Curt. > > > Tommy McDaniel writes: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > As I mentioned in another message I just sent to this > > list, I installed the latest FlightGear yesterday. Of > > course, I couldn't go long without trying different > > terrain, and my first try was a piece including > > southeast Norway. The problem is that, when I try > > starting FlightGear up in that tile, there is no > > scenery, it says my coordinates are 0 degrees and 0 > > degrees, and the plane just doesn't do squat. I can > > tell the engine to throttle up, but the RPM indicator > > stays at 0, and the plane just flat doesn't do > > anything but sit there. Also, there seems to be an > > infinite number of "no terrain intersection" messages > > that begin to be output as soon as the plane is ready > > to go (if only it worked), interspersed with > > occassional "Failed to remove nav-vor-ident sound" > > messages and a few others. I looked through the list > > archives, and I found mention from October or so about > > --lon and --lat having problems, and someone > > suggesting that it was only the eastern hemisphere > > that wasn't working, perhaps because FlightGear was > > parsing coordinates in that hemisphere improperly. I > > therefore downloaded the terrain tile that includes > > Orlando, Florida, and lo and behold, it worked like a > > charm. It was suggested that the problem might be in > > options.cxx, and I have indeed looked at the file for > > a few minutes, but can find no particular error. In > > fact, when I run "./fgfs --lon=11 --lat=59 2> > > /dev/null" from the directory FlightGear is in the > > very first output is: > > > > parse_time() = 11 > > parse_time() = 11 > > parse_time() = 59 > > parse_time() = 59 > > > > which seems to correspond to the coordinates I have > > entered. Perhaps someone that knows which variables to > > follow (and knows how to use the debugger, which I > > don't) can check out what's going on here. I have > > plenty of output messages that I can present if > > needed, but I doubt that they will be helpful. If > > there's anything I can do to help out here and restore > > half of the world to FlightGear (assuming that's what > > the problem is), just let me know. I know C and C++, > > for what it matters. > > > > Tommy McDaniel > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.2.1 (GNU/Linux) > > > > iD8DBQE9/fcyVB8FYP9YqDcRAre8AJ0R57OTsWO8lt6i1p3d6MIe+nlDYACffMV9 > > 481jT9li4U0WEFfjxo18LC4= > > =Z9ph > > -----END PGP SIGNATURE----- > > > > > > __________________________________________________ > > Do you Yahoo!? > > New DSL Internet Access from SBC & Yahoo! > > http://sbc.yahoo.com > > > > _______________________________________________ > > Flightgear-devel mailing list > > [EMAIL PROTECTED] > > http://mail.flightgear.org/mailman/listinfo/flightgear-devel -- Luke Scharf, Jack of Several Trades http://www.ccm.ece.vt.edu/~lscharf _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
