Curtis L. Olson writes:
Is there anything strange in your .fgfsrc or system.fgfsrc files?
I don't have a .fgfsrc or a system.fgfsrc file anywhere on my
computer. Should I?
Cheers - Dave
--
[EMAIL PROTECTED]
___
Flightgear-devel mailing list
Hi Folks,
Just a quick question, since my latest cvs update, flightgear seems to be
ignoring my .fgfsrc file. Has this file been depricated or is this just
temporarily?
Cheers,
Durk
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http
I just commit a change in fgrun CVS that use command line options to
start fgfs. That means that user preferences ( ~/.fgfsrc on linux,
system.fgfsrc on Windows ) are not overwritten anymore.
Regards,
-Fred
___
Flightgear-devel mailing list
* Gerard Robin -- Monday 13 June 2005 20:53:
I had a little break for dinner, now:
the answer for Entertain:
It's not funny any more, now that we know that you fooled us by adding
two spaces to the ~/.fgfsrc config line. ;-)
m.
___
Flightgear
Michael Basler writes:
We were planning to drop system.fgfsrc -- I thought we already had,
but I guess it's still lurking. The processing order, from memory, is
$FG_ROOT/preferences.xml
$HOME/.fgfsrc
command line
I don't fully understand this. Until now
David,
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of David
Megginson
We were planning to drop system.fgfsrc -- I thought we already had,
but I guess it's still lurking. The processing order, from memory, is
$FG_ROOT/preferences.xml
$HOME/.fgfsrc
command line
I
Hello,
is it feasible to improve the parser that reads ~/.fgfsrc to enable
it to read multiple parameters on one line ?
For instance I'd like to take the Beaver for a ride and I always suse
the same starting point, then I'd love place this into my ~/.fgfsrc:
--aircraft=dhc2F --lon=-123.96350
* Gerard Robin -- Monday 13 June 2005 18:34:
Le lundi 13 juin 2005 à 18:24 +0200, Melchior FRANZ a écrit :
* Gerard Robin -- Monday 13 June 2005 17:56:
Error loading config file: Failed to open file
with .fgfsrc
--config=/home/tux-le-boss/.fgfs/preferences.xml
Well
(No
such file or directory)
open(/home/tux-le-boss/.fgfsrc, O_RDONLY) = 3
open(/home/tux-le-boss/.fgfsrc.servlinux.gours, O_RDONLY) = -1 ENOENT (No
such file or directory)
open(/home/tux-le-boss/.fgfsrc.servlinux.gours.gz, O_RDONLY) = -1 ENOENT (No
such file or directory)
open(/home/tux-le-boss/.fgfsrc
Hello,
I'd like to put some comments into the ~/.fgfsrc file. But when I write:
--airport-id=CYVK # Vernon
then the string # Vernon gets interpreted, too and I'm sitting on an
airfiled I've never seen before. Is it possible to extend the parser to
allow such notation ?
Thanks,
Martin
Ooh, never mind, I just found the problem on my side. Please ignore...
On Tuesday 15 June 2004 19:05, Durk Talsma wrote:
Hi Folks,
Just a quick question, since my latest cvs update, flightgear seems to be
ignoring my .fgfsrc file. Has this file been depricated or is this just
temporarily
Something wrong ?
in fgfsrc in have:
--geometry=1280x896
--enable-real-weather-fetch
--timeofday=afternoon
--prop:/nasal/local/script=![CDATA[ INIT = func { setprop
(/sim/rendering/clouds3d-cache-size, 4096); } ]]
nasal does give error message: Nasal parse error: parse error in /nasal
[0
* Gerard Robin -- Monday 13 June 2005 17:21:
2/ with .fgfsrc
--config=$FG_HOME/.fgfs/preferences.xml
i get the message:
Error loading config file: Failed to open file
at $FG_HOME/.fgfs/preferences.xml
Shell variables aren't expanded in the config file (AFAIK). That's done
by the shell
* Gerard Robin -- Monday 13 June 2005 17:56:
Error loading config file: Failed to open file
at /home/tux-le-boss/.fgfs/preferences.xml
with .fgfsrc
--config=/home/tux-le-boss/.fgfs/preferences.xml
Well, then this file just doesn't exist or has wrong permissions.
m
Norman Vine writes:
Curtis L. Olson writes:
David Megginson writes:
I just checked in changed to fix the init-order problem for *-set.xml
files. My solution was blunt but effective. I simply parse all of
the system.fgfsrc, $HOME/.fgfsrc, and command-line options twice --
once
On Fri, 11 Feb 2005 16:14:15 +0100
Ron Lange wrote:
sorry, not the *commandline* below causes fg to break but similar
.fgfsrc file...
fgfs --airport=EDHI --aircraft=bo105 --enable-game-mode
#
Again, only a present
Hm...hmmm...since putting one flag per line in .fgfsrc wasn't satisfying
(not starting from EDHI nor with the bo-105...) I put all flags in one
row. Then everything goes as desired but the game mode...after adding
enabel-game-mode the segfault appeared.
Regards
Ron
Martin Spott schrieb:
Jorge
/preferences.xml in my ~/.fgfsrc[1]
(where $FG_HOME is set to $HOME/.fgfs/), and this ~/.fgfs/preferences.xml
file says (among many other things):
nasal
local
script![CDATA[
INIT = func {
setprop(/ai/models/ship/controls/glide-path, 0
Le lundi 13 juin 2005 17:35 +0200, Melchior FRANZ a crit :
* Gerard Robin -- Monday 13 June 2005 17:21:
2/ with .fgfsrc
--config=$FG_HOME/.fgfs/preferences.xml
i get the message:
Error loading config file: Failed to open file
at $FG_HOME/.fgfs/preferences.xml
Shell variables
Only if you want to override default values ... did you try the
--trace option to see where the values where getting set and to what
values?
Curt.
D Luff writes:
Curtis L. Olson writes:
Is there anything strange in your .fgfsrc or system.fgfsrc files?
I don't have a .fgfsrc
David Megginson
Norman Vine writes:
I think preferences.xml and the aircraft-set.xml files pretty much
cover any functionality that was intended to handle.
PLEASE DO NOT REMOVE the .fgfsrc option until
such time has we have a 'options editor'
I have not suggested doing
was supposed to be 1) preferences.xml, 2) system.fgfsrc,
and finally 3) command line.
We were planning to drop system.fgfsrc -- I thought we already had,
but I guess it's still lurking. The processing order, from memory, is
$FG_ROOT/preferences.xml
$HOME/.fgfsrc
command line
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_
Jorge Van Hemelryck wrote:
Could you make sure that there is only one option per line in the
.fgfsrc file ? It looks like the parser is trying to set the airport
from the string EDHI --aircraft=bo105 --enable-game-mode...
Aaah, your comment reminds me that the parser is unable to parse
Gerard Robin asked
Something wrong ?
in fgfsrc in have:
--geometry=1280x896
--enable-real-weather-fetch
--timeofday=afternoon
--prop:/nasal/local/script=![CDATA[ INIT = func { setprop
(/sim/rendering/clouds3d-cache-size, 4096); } ]]
nasal does give error message: Nasal parse
Le lundi 13 juin 2005 18:24 +0200, Melchior FRANZ a crit :
* Gerard Robin -- Monday 13 June 2005 17:56:
Error loading config file: Failed to open file
at /home/tux-le-boss/.fgfs/preferences.xml
with .fgfsrc
--config=/home/tux-le-boss/.fgfs/preferences.xml
Well, then this file
Hello,
Have been reading the thread on the unreadable preferences file, and
noticed a small detail that may be a clue. In the subject line of
writing rules ... in fgfsrc, I see an odd block character just before
the f in fgfsrc. It appears in messages from Gerard and Andy, but
not those from
* WillyB -- Friday 20 June 2003 00:59:
you said 'personal preferences.xml'
$ fgfs --config=/your/personal/preferences.xml
or
$ cat ~/.fgfsrc
--config=/your/personal/preferences.xml
$ fgfs
(mine is called ~/.fgfs/preferences.xml. I have some other
personal fgfs config stuff
Martin Spott wrote:
snip
2.) How do I engage the parking brake for the default aircraft from the
command line right from the beginning ?
Thanks,
Martin.
--prop:/controls/gear/brake-parking=1.0
You can also put this in your .fgfsrc, which is what I do.
Josh
Le lundi 13 juin 2005 07:13 -0700, Andy Ross a crit :
--prop:/sim/rendering/clouds3d-cache-size=4096
It should work but the program overload the data, only one way the nasal
way
thanks
--
Gerard
___
Flightgear-devel mailing list
the data.
I have since a long time --config=$FG_HOME/preferences.xml in my ~/.fgfsrc[1]
(where $FG_HOME is set to $HOME/.fgfs/), and this ~/.fgfs/preferences.xml
file says (among many other things):
nasal
local
script![CDATA[
INIT = func
* Gerard Robin -- Monday 13 June 2005 19:19:
open(/home/tux-le-boss/.fgfs/preferences.xml , O_RDONLY|O_LARGEFILE) = -1
ENOENT (No such file or directory)
Yes, and I was right: this file just doesn't exist! This is not an
fgfs message, but one of the operating system.
m.
Hi,
Gerard Robin wrote:
open(/home/tux-le-boss/.fgfs/preferences.xml , O_RDONLY|O_LARGEFILE) = -1
ENOENT (No such file or directory)
^^
Did you see those blanks at the end of the filename? Are these actually
in the original report? Where could
* Melchior FRANZ -- Monday 13 June 2005 20:24:
Add this to your ~/.vimrc and become a happier man:
set listchars=tab:¦¯,trail:×,extends:»,precedes:«
or this:
set listchars=tab:°`,trail:°,extends:,precedes:
followed by
set list
of course, ...
m. :-)
(/home/tux-le-boss/.fgfsrc, O_RDONLY) = 3
open(/home/tux-le-boss/.fgfsrc.servlinux.gours, O_RDONLY) = -1 ENOENT
(No such file or directory)
open(/home/tux-le-boss/.fgfsrc.servlinux.gours.gz, O_RDONLY) = -1
ENOENT (No such file or directory)
open(/home/tux-le-boss/.fgfsrc, O_RDONLY) = 3
open(/home
Gerard Robin schrieb:
I can give to Ralf the prize, if everybody agree.
Thanks, too much honor ;-)
Ralf
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Curtis L. Olson writes:
David Megginson writes:
I just checked in changed to fix the init-order problem for *-set.xml
files. My solution was blunt but effective. I simply parse all of
the system.fgfsrc, $HOME/.fgfsrc, and command-line options twice --
once before loading the *-set.xml
David,
The idea was that system.fgfsrc is system-wide, while .fgfsrc is
per-user. For Windows, perhaps we should look for fgfs.cfg in My
Documents or wherever (is there any concept of separate user
directories yet?).
Win XP and 2000 allow management of separate user directories under
be
sufficient for most (all?) Windows users. You still can allow and
parse a .fgfsrc under $HOME for Unix users, though.
What we probably need to do, then, is remove the old system.fgfsrc
code, and instead load a file named system.fgfsrc (or perhaps
fgfs.cfg) when a Unix system would load $HOME/.fgfsrc
...
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
help
Valid commands are:
cd dir cd to a directory, '..' to move back
data switch to raw data mode
dump dump current state (in xml)
[...]
The fgfsrc default browser
, that
$HOME/.fgfsrc on Unix a read more than once as well.
See, as nice as the XML configuration system is, it _must_ bring such
a 'feature' to the developer. In order to figure which command line
paramters you are allowed to use you have first to determine $FG_ROOT.
If $FG_ROOT is defined by the $HOME
in the context of the claim, that
$HOME/.fgfsrc on Unix a read more than once as well.
See, as nice as the XML configuration system is, it _must_ bring such
a 'feature' to the developer. In order to figure which command line
paramters you are allowed to use you have first to determine $FG_ROOT
sorry, not the *commandline* below causes fg to break but similar
.fgfsrc file...
fgfs --airport=EDHI --aircraft=bo105 --enable-game-mode
#
Again, only a present .fgfsrc with similar content causes a segfault,
the commandline let
highlighting,
textures, enhanced lighting, etc. etc.. It would still either fail
to start, or start and be unusably slow.
Can you be more specific? What command are you using to start up
fgfs, and what are the contents of your .fgfsrc?
Previous times that stuff like this has happened, it's
Le lundi 13 juin 2005 15:16 +0100, Vivian Meazza a crit :
Gerard Robin asked
Something wrong ?
in fgfsrc in have:
--geometry=1280x896
--enable-real-weather-fetch
--timeofday=afternoon
--prop:/nasal/local/script=![CDATA[ INIT = func { setprop
(/sim/rendering/clouds3d-cache
Le lundi 13 juin 2005 16:32 +0200, Gerard Robin a crit :
Le lundi 13 juin 2005 15:16 +0100, Vivian Meazza a crit :
Gerard Robin asked
Something wrong ?
in fgfsrc in have:
--geometry=1280x896
--enable-real-weather-fetch
--timeofday=afternoon
--prop:/nasal/local/script
Le lundi 13 juin 2005 18:34 +0200, Gerard Robin a crit :
Le lundi 13 juin 2005 18:24 +0200, Melchior FRANZ a crit :
* Gerard Robin -- Monday 13 June 2005 17:56:
Error loading config file: Failed to open file
at /home/tux-le-boss/.fgfs/preferences.xml
with .fgfsrc
--config
Norman Vine writes:
I think preferences.xml and the aircraft-set.xml files pretty much
cover any functionality that was intended to handle.
PLEASE DO NOT REMOVE the .fgfsrc option until
such time has we have a 'options editor'
I have not suggested doing so; I'm suggesting only
to add two lines
to the ~/.fgfsrc ?
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--
___
Flightgear-devel mailing list
[EMAIL PROTECTED
on or with the
engine off.
I'm not surprised you couldn't replicate it. I found a pesky old
.fgfsrc file containing:
[EMAIL PROTECTED]
I'll get my coat :-/
All the best,
Matthew.
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org
Erik Hofman wrote:
+ OpenAL setup for general use (Linux)
+ -
+ As of July 2004 it is best to add at least the following line to your
+ ~/.fgfsrc file on Linux because it wil find out what audio backend to
+ use, starting with the most appropriate
Martin Spott wrote:
Erik Hofman wrote:
+ OpenAL setup for general use (Linux)
+ -
+ As of July 2004 it is best to add at least the following line to your
+ ~/.fgfsrc file on Linux because it wil find out what audio backend to
+ use, starting with the most
visibility type=boolfalse/visibility
/menubar
/sim
...
/PropertyList
or simply start fgfs with this option (or put it into ~/.fgfsrc):
--prop:/sim/menubar/visibility=0
m.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http
Andy Ross a crit :
--prop:/sim/rendering/clouds3d-cache-size=4096
It should work but the program overload the data, only one way the
nasal way
That sounds like a bug to me. The command line should be overwriting
anything in the configuration files. Is the cloud code (over-)writing
this
* Rodrigo Flores -- Saturday 19 November 2005 16:18:
Finally, the old fonts in the FG 0.9.8 format are still there, couldn´t
see the fonts showed in the Concorde screenshot.
You have to switch the GUI style with Shift-F10, or put this into your
~/.fgfsrc or use it on the command line
panel
pathAircraft/c172/Panels/c172-vfr-panel.xml/path
visibilitytrue/visibility
/panel
Let's say that I want to use a different C172 panel by default. If I
simply add
-prop:/sim/panel/path=Aircraft/c172/Panels/c172r-panel.xml
to my .fgfsrc, I'll get the alternative C172 panel
to the subfiles of the
original. Second, a read-only site-wide preferences.xml should be very
minimalist so that it isn't too difficult to use the .fgfsrc and command
line settings.
What about allowing the user to specify a .xml file to load instead
of the defaults for each of the config files? ie
that runs
fgfs. Try running fgfs directly instead. From a command window enter fgfs
--help or fgfs --help --verbose. This will give you lists of the command line
options. Under windows you could then just create a shortcut with the
parameters you want specified.
Or you can use an .fgfsrc file
I'm getting a segfault in a newly-compiled-from-cvs FlightGear:
[EMAIL PROTECTED] jonathan]$ ls ~/.fgfsrc
ls: /home/jonathan/.fgfsrc: No such file or directory
[EMAIL PROTECTED] jonathan]$ fgfs --log-level=bulk
yadda yadda
Looking for bindings for joystick Saitek Saitek X45
cut
Trying Saitek
not feel it should be in the CVS just yet?
pps:
Dear David,
Oh, I see. In Unix, we have (or had) two files:
system.fgfsrc in $FG_ROOT
.fgfsrc in $HOME
The idea was that system.fgfsrc is system-wide, while .fgfsrc is
per-user. For Windows, perhaps we should look for fgfs.cfg in My
Documents
snippets from the log
$ src/Main/fgfs 21 | tee log
FlightGear: Version unknown version
Built with GNU C++ version 3.3
Scanning command line for: --fg-root=
Scanning D:\home\nhv/.fgfsrc for: --fg-root=
fg_root = d:/home/nhv/FlightGear
Reading global preferences
Finished Reading global preferences
--verbose. This will give you lists of the command line options. Under windows you could then just create a shortcut with the parameters you want specified.Or you
can use an .fgfsrc file (fgrun used to create one of these, not sure if it still does). IIRC it is called system.fgfsrc under windows. It can be used
Erik Hofman writes:
First of all, I doubt if many *users* would want to change the panel,
etc of already exsisting aircraft. This is probably just for (aircraft)
developers of FlightGear.
Certainly they won't as long as every aircraft, panel, etc. is in the
base package, but I can
Cameron Moore writes:
I keep my setup pretty clean (no .fgfsrc or mods to base package). RL
is keeping me very busy right now, so I wanted to mention this sooner
rather than later. If noone can reproduce this, let me know and I'll
try to find time to investigate some more. Thanks
files and settings in .fgfsrc.
Best,
Jim
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
Hi All,
Just wondering if anyone else uses this stick successfully?
It works perfectly here under windoz but after *hours* of changing the
.fgfsrc and starting and stopping fg for each change, I am getting a
little discouraged.
Thanks take care, Vikki.
--
Victoria Welch, WV9K/7, SysAdmin
Victoria Welch writes:
Presuming that the cvs version of plib did something, I'll try hacking
around with the values in .fgfsrc and see what happens. It looks enough
like it did that I have no confidence of success here, but one never
knows.
When you run js_demo in the plib distro
) preferences.xml, 2) system.fgfsrc,
and finally 3) command line.
We were planning to drop system.fgfsrc -- I thought we already had,
but I guess it's still lurking. The processing order, from memory, is
$FG_ROOT/preferences.xml
$HOME/.fgfsrc
command line
All the best,
David
--
David Megginson
Major A [EMAIL PROTECTED] wrote:
Now I know why: I set --prop:/environment/turbulence-norm=1.0 in my
~/.fgfsrc and obviously this has impact even at ground level :-)
Well... have you tried, BTW, to take off with the TSR.2 with
crosswind?
I did quite a few times and I'm pretty fine
Now that I have FlightGear linking, I have found another problem that
has cropped up recently (I'm not sure when, exactly). It seems as if
the 3D panel is always active. Since I always run FlightGear with the
--disable-panel in my .fgfsrc file, this causes problems. If I don't
run
these things. If
available, a big moon and sun switch would go into my .fgfsrc file right away
(still mulling the possibilities if we supported modifying and saving default
settings from the PUI interface).
Best,
Jim
___
Flightgear-devel mailing list
[EMAIL
755
To run it cd to the dir you put it in and run
./fgfs-start.sh
Hope you all like it, it saves me from editing my .fgfsrc file all the time
and remembering all the the command line options I usully use.
You can edit the directories for your installation of FlightGear - as
explained in the file
WillyB [EMAIL PROTECTED] wrote:
Hope you all like it, it saves me from editing my .fgfsrc file all the time
and remembering all the the command line options I usully use.
Nice. You still can save a bit of work on maintaining the script by
replacing the manually edited aircraft selection list
;)
And secondly, I find that when this entry is amended by my fgfsrc, which maps
the rudder to axis 2 and the throtle to axis 3, the engine[1] entry is still
active - I turn the rudder and the throttle[1] responds (as well as the
rudder).
I notice that the keyboard is already mapped to use
autopilot/control
, not the dir where data and
whatever is in. Your FG_ROOT is useless, but you are
probably setting the root correctly in ~/.fgfsrc anyway,
so you will only run into troubles if you run other
programs that depend on FG_ROOT, such as metar.
m
If it doesn't need to be in a user friendly way you could specify
something like this in your ~/.fgfsrc file:
--prop:/jsbsim/config/integrator=mytype
--prop:/jsbsim/config/logging=true
--prop:/jsbsim/config/atmosphere=mars
That would require _no_ action from the FlightGear side.
Erik
,
launched from a menu within flightgear. Presumably the required changes to
axis responses can be made within the property tree by such a tool and saved
in fgfsrc or some other file?
Thanks,
Chris
___
Flightgear-devel mailing list
[EMAIL PROTECTED
on the aircraft, either with the engine on or with the
engine off.
I'm not surprised you couldn't replicate it. I found a pesky old
.fgfsrc file containing:
[EMAIL PROTECTED]
I'll get my coat :-/
Lol... nah don't go. We've all done something like that.
Well, maybe not everyone
Jim Wilson wrote:
My preference would probably be Alex's original patch.
_My_ preference would be to put as default what the BO-maintainer
prefers as his _personal_ choice and add an optional property,
reverting the default behaviour, that every user can put into his
~/.fgfsrc
When we've got
to let
'metar' honour the respective parameters in a ~/.fgfsrc file (proxy
settings for example) in the same the way, 'fgfs' does !?
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends
On Sunday, 12 December 2004 19:29, Paul Surgeon wrote:
What do people think about having a ~/.fgfs folder?
I need a place to be able to read and write user data.
.fgfsrc could also live in there too.
After chatting with Melchior a bit :
Can I add a FG-HOME environment variable in case HOME
Paul Surgeon wrote:
What do people think about having a ~/.fgfs folder?
I need a place to be able to read and write user data.
.fgfsrc could also live in there too.
After chatting with Melchior a bit :
Can I add a FG-HOME environment variable in case HOME does not exist?
The order of preference
On Sunday 12 December 2004 18:29, Paul Surgeon wrote:
What do people think about having a ~/.fgfs folder?
I need a place to be able to read and write user data.
.fgfsrc could also live in there too.
I would prefer a folder called ~/.flightgear instead of ~/.fgfs.
This is an usability issue
What do people think about having a ~/.fgfs folder?
I need a place to be able to read and write user data.
.fgfsrc could also live in there too.
After chatting with Melchior a bit :
Can I add a FG-HOME environment variable in case HOME does not exist?
The order of preference will be :
1. FG_HOME
Hi,
I just ran into the following issue:
In my .fgfsrc I have specified
--fg-scenery=/home/durk/FlightGear-Scenery-0.9.5/
Which is a directory I had just deleted a few minutes earlier, because of an
upgrade to Scenery-0.9.[78].
As a result, FlightGear quit with a segmentaton fault
Gerard Robin wrote:
Something wrong ?
--prop:/nasal/local/script=![CDATA[ INIT = func { setprop
(/sim/rendering/clouds3d-cache-size, 4096); } ]]
nasal does give error message: Nasal parse error: parse error in /nasal
[0]/local[0], line 1
The --prop argument is not an XML parser. Just
Melchior FRANZ
* Gerard Robin -- Monday 13 June 2005 16:32:
Le lundi 13 juin 2005 à 15:16 +0100, Vivian Meazza a écrit :
--prop:/sim/rendering/clouds3d-enable=1
--prop:/sim/rendering/clouds3d-cache-size=4096
Does not work the program overload the data.
You need to have both -
* Vivian Meazza -- Monday 13 June 2005 17:37:
You need to have both - that would be reasonable since why would you set one
and not the other - a feature rather than a bug?
It's at least a usability bug. The clouds code interprets cache_size=0 as
turn off rendering. So you can't have a value set
Gerard:
--config=/home/tux-le-boss/.fgfs/preferences.xml
Error loading config file: Failed to open file
at /home/tux-le-boss/.fgfs/preferences.xml
Melchior:
Well, then this file just doesn't exist or has wrong permissions.
Gerard:
Yes Existing, good permissions
Melchior:
Try this:
$
Le lundi 13 juin 2005 19:31 +0200, Melchior FRANZ a crit :
* Gerard Robin -- Monday 13 June 2005 19:19:
open(/home/tux-le-boss/.fgfs/preferences.xml , O_RDONLY|O_LARGEFILE) = -1
ENOENT (No such file or directory)
Yes, and I was right: this file just doesn't exist! This is not an
fgfs
* Gerard Robin -- Monday 13 June 2005 19:41:
Not so Quick..
Oh do you remember i told you :
I do remember. But I don't believe you.
fgfscvs --airport=LFNH --aircraft=P38-L --config=/home/tux-le-
boss/.fgfs/preferences.xml
Entertain us and post the output of
$ strace -fF -eopen
* Ralf Gerlich -- Monday 13 June 2005 20:07:
Gerard Robin wrote:
open(/home/tux-le-boss/.fgfs/preferences.xml , [...]
^^
Did you see those blanks at the end of the filename? Are these actually
in the original report? Where could these come
Le lundi 13 juin 2005 20:07 +0200, Ralf Gerlich a crit :
Hi,
Gerard Robin wrote:
open(/home/tux-le-boss/.fgfs/preferences.xml , O_RDONLY|O_LARGEFILE) =
-1 ENOENT (No such file or directory)
^^
Did you see those blanks at the end of the
Le lundi 13 juin 2005 20:07 +0200, Ralf Gerlich a crit :
Hi,
Gerard Robin wrote:
open(/home/tux-le-boss/.fgfs/preferences.xml , O_RDONLY|O_LARGEFILE) =
-1 ENOENT (No such file or directory)
^^
Did you see those blanks at the end of the
/FlightGear
or ~./flightgear/
When using the latter one, we could also start to put the .fgfsrc config file
into ~./flightgear/
I thought about a dedicated account for terrasync (non-root),
with right permissions only to the /var/share/FlightGear/Scenery/Terrain
(or WorldScenery/Terrain
After noting Sid Boyce note concerning freeglut on the users list where
~/.fgfsrc was the issue, I renamed that file and fgfs worked. Then I
checked which option in fgrun would cause the freeglut abort. The only
problem option I found is
--enable-clouds3d
Same result from the command line
to have the exterior view on the panel system.
Hi Bruce,
Try adding this option to your ~/.fgfsrc or the command line:
--prop:/sim/rendering/draw-otw=false
Curt.
--
Curtis Olsonhttp://www.flightgear.org/~curt
HumanFIRST Program http://www.humanfirst.umn.edu/
FlightGear Project http
alternative is to use aliases in the
aircraft config files, so that we have something like this:
snip
and so on. Then, in .fgfsrc, the user can specify
--prop:/sim/aircraft/c172/panel/path=Aircraft/c172/Panels/c172r-panel.xml
I prefer not to use the property manager at startup because
should be very minimalist
so that it isn't too difficult to use the .fgfsrc and command line settings.
What about allowing the user to specify a .xml file to load instead
of the defaults for each of the config files? ie
fgfs --keyboard-prefs=~/.fgfs/my-keyboard.xml
and the like?
That'd make
Yes seems straightforward.
adding
--nmea=file,out,60,/home/mat/Flightgear/data/Protocol/recordednmea
to fgfsrc
created the recordednmea file OK
First few and last couple of lines from a climb to around 6000 feet
heading west looked like this:
$GPRMC,041051,A,4340.0891,N,00713.5881,E
1 - 100 of 211 matches
Mail list logo
