Re: [Flightgear-devel] Little flaws with Win32 package
Martin Spott a écrit : Hello, I just downloaded the Win32 package and took it for a test-ride. There are three things I'd like to mention: 1.) The Isle of Alcatraz doesn't look as I'm used to it from FlightGear. To my knowledge Frederic adapted the terrain to include the heliport, this is now missing. Heliport are no longer in the new Scenery ( 0.9.8 ) 2.) On Windows I usually place e system.fgfsrc file in the 'data/' directory. This usually works fine but there is a flaw that already was present in the 0.9.6 Win32 binary: The --aircraft=-flag is not being honoured, I always get the c172. Everything else looks good. System.fgfsrc is no longer overwritten but it is still read by flightgear. So you can get old value you don't want anymore -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Little flaws with Win32 package
Frederic Bouvier wrote: Heliport are no longer in the new Scenery ( 0.9.8 ) Too bad :-( System.fgfsrc is no longer overwritten but it is still read by flightgear. This is what I meant: I run FlightGear and it actually reads most of the values in my manually written 'system.fgfsrc', except a single one (as far as I can tell), which is the aircraft to use. I've already moved the --aircraft=-clause to different positions but this didn't make any difference. Cheers, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Little flaws with Win32 package
Martin Spott wrote : System.fgfsrc is no longer overwritten but it is still read by flightgear. This is what I meant: I run FlightGear and it actually reads most of the values in my manually written 'system.fgfsrc', except a single one (as far as I can tell), which is the aircraft to use. I've already moved the --aircraft=-clause to different positions but this didn't make any difference. From the beginning, fgrun was starting fgfs with 2 command line options : --fg-root and --aircraft because you need the first to find system.fgfsrc and the second because it was not used in this file. -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Little flaws with Win32 package
Frederic Bouvier wrote: Martin Spott wrote : This is what I meant: I run FlightGear and it actually reads most of the values in my manually written 'system.fgfsrc', except a single one (as far as I can tell), which is the aircraft to use. I've already moved the --aircraft=-clause to different positions but this didn't make any difference. From the beginning, fgrun was starting fgfs with 2 command line options : --fg-root and --aircraft because you need the first to find system.fgfsrc and the second because it was not used in this file. I never talked about 'fgrun', I am talking about FlightGear itself, alias 'fgfs.exe'. How do I manage to let FlightGear on Windows read the aircraft name from the 'system.fgfsrc' ? Is the use of 'system.fgfsrc' still a 'supported' option with FlightGear on Windows ? If yes, then I think FlightGear on Windows simply has a bug because it ignores the aircraft name. If not, is there an official replacement for this configuration file ? Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Little flaws with Win32 package
Quoting Martin Spott : Frederic Bouvier wrote: Martin Spott wrote : This is what I meant: I run FlightGear and it actually reads most of the values in my manually written 'system.fgfsrc', except a single one (as far as I can tell), which is the aircraft to use. I've already moved the --aircraft=-clause to different positions but this didn't make any difference. From the beginning, fgrun was starting fgfs with 2 command line options : --fg-root and --aircraft because you need the first to find system.fgfsrc and the second because it was not used in this file. I never talked about 'fgrun', I am talking about FlightGear itself, alias 'fgfs.exe'. How do I manage to let FlightGear on Windows read the aircraft name from the 'system.fgfsrc' ? Is the use of 'system.fgfsrc' still a 'supported' option with FlightGear on Windows ? If yes, then I think FlightGear on Windows simply has a bug because it ignores the aircraft name. If not, is there an official replacement for this configuration file ? I was just writting about my experience on the problem, and this is not a recent issue, although I silently worked around. But are you sure it is specific to windows ? -Fred ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Little flaws with Win32 package
Frederic Bouvier wrote: I was just writting about my experience on the problem, and this is not a recent issue, although I silently worked around. But are you sure it is specific to windows ? It's a bit complicated to make a 'fair' comparison with other platforms because on Unix the file has a different name (.fgfsrc) and a different location ($HOME). I am using $HOME/.fgfsrc on Unix already for a looong time (maybe since 0.7.3 if the feature was already present in this release) and I know it now works at least on four different Unices (well, not surprising), Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Little flaws with Win32 package
Fred wrote: Quoting Martin Spott : Frederic Bouvier wrote: Martin Spott wrote : This is what I meant: I run FlightGear and it actually reads most of the values in my manually written 'system.fgfsrc', except a single one (as far as I can tell), which is the aircraft to use. I've already moved the --aircraft=-clause to different positions but this didn't make any difference. From the beginning, fgrun was starting fgfs with 2 command line options : --fg-root and --aircraft because you need the first to find system.fgfsrc and the second because it was not used in this file. I never talked about 'fgrun', I am talking about FlightGear itself, alias 'fgfs.exe'. How do I manage to let FlightGear on Windows read the aircraft name from the 'system.fgfsrc' ? Is the use of 'system.fgfsrc' still a 'supported' option with FlightGear on Windows ? If yes, then I think FlightGear on Windows simply has a bug because it ignores the aircraft name. If not, is there an official replacement for this configuration file ? I was just writting about my experience on the problem, and this is not a recent issue, although I silently worked around. But are you sure it is specific to windows ? Same under Cygwin - it's been like it for as long as I can remember - I thought it was a feature not a bug, and have lived with it. Regards, Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
