[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* 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.
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 {
setprop(/ai/models/ship/controls/glide-path, 0);
setprop(/sim/sound/volume, 0.6);
setprop(/sim/rendering/clouds3d-cache-size, 4096);
}
settimer(INIT, 0);
]]
/script
/local
/nasal
[1] OK, that's a lie. I *had* that in my ~/.fgfsrc, but I dropped that file
because fgrun overwrote it (which is fixed now), so I moved it into my
~/bin/fgfs wrapper as command line option. But that's just a minor detail. :-)
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
Le lundi 13 juin 2005 16:58 +0200, Melchior FRANZ a crit :
* 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.
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 {
setprop(/ai/models/ship/controls/glide-path, 0);
setprop(/sim/sound/volume, 0.6);
setprop(/sim/rendering/clouds3d-cache-size, 4096);
}
settimer(INIT, 0);
]]
/script
/local
/nasal
[1] OK, that's a lie. I *had* that in my ~/.fgfsrc, but I dropped that file
because fgrun overwrote it (which is fixed now), so I moved it into my
~/bin/fgfs wrapper as command line option. But that's just a minor detail.
:-)
I would have to be please to you and say yes that's OK
Sorry i cannot.
sometime ago i tried it and again i get== follow me==
1/ with command line
fgfscvs --airport=LFNH --aircraft=P38-L --config=
$FG_HOME/.fgfs/preferences.xml
everything good :-)
2/ with .fgfsrc
--config=$FG_HOME/.fgfs/preferences.xml
--nmea=socket,out,0.5,servlinux,5500,udp
--airport=LFNH
--geometry=1280x896
--enable-real-weather-fetch
--timeofday=afternoon
i get the message:
Error loading config file: Failed to open file
at $FG_HOME/.fgfs/preferences.xml
very bad :-(
I am probably wrong somewhere :-?
thanks
--
Gerard
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* 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 when you give it on the command line. Just write it out: --config=/home/robin_hood/.fgfs/preferences.xml m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
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 - that would be reasonable since why would you set one and not the other - a feature rather than a bug? V. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* 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 with clouds off. This should, of course, be a separate variable. It's not like we can't afford two extra bytes on today's machines. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
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 aren't expanded in the config file (AFAIK). That's done by the shell when you give it on the command line. Just write it out: --config=/home/robin_hood/.fgfs/preferences.xml m. i did not use robin_hoodbecause of copyright but again the same message: 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 --nmea=socket,out,0.5,servlinux,5500,udp --airport=LFNH --geometry=1280x896 --enable-real-weather-fetch --timeofday=afternoon Oh... i did not say before , i had tried it... i know just a bit about Linux (since 1995) beuh and before that time UNIX... again beh . -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* 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. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
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 just doesn't exist or has wrong permissions. m. Yes Existing, good permissions I did also something which is verboten i have tried under root itself. Whoua the bad boy.. I'll give up. only one question: Without your wrapper, does the system working ? -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
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=/home/tux-le-boss/.fgfs/preferences.xml Well, then this file just doesn't exist or has wrong permissions. m. Yes Existing, good permissions I did also something which is verboten i have tried under root itself. Whoua the bad boy.. I'll give up. only one question: Without your wrapper, does the system working ? I forgot to say, existing and good permissions, i prove it: Command fgfscvs --airport=LFNH --aircraft=P38-L --config=/home/tux-le- boss/.fgfs/preferences.xml Working positive result So. -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* 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, then this file just doesn't exist or has wrong permissions. Without your wrapper, does the system working ? It works with my wrapper, and it works with that --config line in my ~/.fgfsrc. Try this: $ strace -fF -eopen fgfs 21|grep tux and see which error code it returns. Isn't really a topic for devel ... m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
Le lundi 13 juin 2005 18:53 +0200, Melchior FRANZ a crit : strace -fF -eopen fgfs 21|grep tux The answer is: 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/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/tux-le-boss/.fgfsrc, O_RDONLY) = 5 open(/home/tux-le-boss/.fgfs/preferences.xml , O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) at /home/tux-le-boss/.fgfs/preferences.xml Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
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: $ strace -fF -eopen fgfs 21|grep tux Gerard: open(/home/tux-le-boss/.fgfs/preferences.xml , O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory) Ding ding ding! We have a winner! :) Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* 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. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
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 message, but one of the operating system. m. Not so Quick.. Oh do you remember i told you : fgfscvs --airport=LFNH --aircraft=P38-L --config=/home/tux-le- boss/.fgfs/preferences.xml Working positive result Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
Gerard wrote: Melchior wrote: Yes, and I was right: this file just doesn't exist! This is not an fgfs message, but one of the operating system. Not so Quick.. Oh do you remember i told you : You can't really argue with a syscall result. The file isn't there. Maybe there are some other conditions (lack of x permissions in a directory on the path?) that will produce an ENOENT instead of an EPERM, so it's not impossible that the file is present. But the bottom line is that fgfs can't read the file. We can't debug this for you; you need to figure out your system configuration first. Try, as the user running fgfs, things like: ls -l /home/tux-le-boss/.fgfs/preferences.xml cat /home/tux-le-boss/.fgfs/preferences.xml /dev/null more /home/tux-le-boss/.fgfs/preferences.xml You will eventually discover what the problem is. Again, the syscall result is telling: you can argue on the mailing list until you collapse from exhaustion and you will never convince the OS that the file is there. :) Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* 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 fgfs --config=/home/tux-le-boss/.fgfs/preferences.xml 21|grep tux Should be from the same machine, of course, and with the (non)file unchanged. m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
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 these come from? Ralf ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* 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 from? Arghh. Good catch! Apparently, fgfs doesn't strip that. And Gerard uses a crappy editor. Add this to your ~/.vimrc and become a happier man: set listchars=tab:¦¯,trail:×,extends:»,precedes:« or this: set listchars=tab:°`,trail:°,extends:,precedes: m. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
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 filename? Are these actually in the original report? Where could these come from? Ralf Yes I did observe it, after modification == no change, it could have been a good explanation. thanks -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* 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. :-) ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* 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 from?
Arghh. Good catch! Apparently, fgfs doesn't strip that. And Gerard
uses a crappy editor.
Maybe this should be changed like so:
diff -u -p -U1 -r1.67 options.cxx
--- options.cxx 25 Feb 2005 21:20:17 - 1.67
+++ options.cxx 13 Jun 2005 18:39:45 -
@@ -1537,3 +1537,3 @@ fgParseOptions (const string path) {
// catch extraneous (DOS) line ending character
-if ( line[line.length() - 1] 32 ) {
+while ( line[line.length() - 1] = 32 ) {
line = line.substr( 0, line.length()-1 );
or more efficient ... :-)
m.
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
Le lundi 13 juin 2005 19:58 +0200, Melchior FRANZ a crit : * 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 fgfs --config=/home/tux-le-boss/.fgfs/preferences.xml 21|grep tux Should be from the same machine, of course, and with the (non)file unchanged. m. I had a little break for dinner, now: the answer for Entertain: $ strace -fF -eopen fgfscvs --config=/home/tux-le- boss/.fgfs/preferences.xml 21|grep tux-le 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/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/tux-le-boss/.fgfsrc, O_RDONLY) = 5 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/.fgfs/preferences.xml, O_RDONLY|O_LARGEFILE) = 5 -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
* 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-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
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 filename? Are these actually in the original report? Where could these come from? Ralf Yes now that is good, my first correction introduced probably an other blank. After using Emacs no Problem (ahrrg kedit), i continu to learn where are the traps. I can give to Ralf the prize, if everybody agree. And many thanks to everybody. -- Gerard ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: writing rules with --prop for nasal in fgfsrc
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 2f585eeea02e2c79d7b1d8c4963bae2d
