On Monday 03 October 2005 19:57, Melchior FRANZ wrote: > * Melchior FRANZ -- Monday 03 October 2005 19:47: > > * Durk Talsma -- Monday 03 October 2005 18:08: > > > > (B) which bugs need to be fixed (and by whom :-)? > > > > > > - Setting a wrong path for --fg-scenery results in an abort > > > > I'll look into this. > > It behaves exactly as it is supposed to: If no paths are given, > the default is used. If paths are given, fgfs uses all that do > actually contain scenery. (It doesn't complain about paths that > don't!) But if a user specifies one or more paths but *none* > contains valid scenery, it aborts with this error message: > > Fatal error: No valid scenery path defined! >
Hmm, I think there's more to it than meets the eye: I had FlightGear die right after I had upgraded my Linux box, but before I discovered I had not yet moved the scenery tree over from my backup drive. I have specified: --fg-scenery=/home/durk/FlightGear-Scenery-0.9.7/ When this path exists everything works fine, but if I move FlightGear scenery to some other path, I get Could not find VVNS Could not find VVNT Aborted [EMAIL PROTECTED]:~/src/FlightGear-0.9/source-devel> (With the two "Could not find" Messages coming from the Traffic manager) Problem is not that FlightGear refuses to run without scenery( which makes sense), but that the error message I'm seeing in this case isn't particularly insightful. I think the problem here is not that FlightGear scans directories that don't contain scenery, but that FlightGear is trying to open a directory that doesn't exist. HTH, Durk _______________________________________________ Flightgear-devel mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
