Menu
▾
▴
#132 $FG_SCENERY ignored in OS X and Linux (and WIndows?)
Originally created by: Armande.... (code.google.com)@gmail.com
On OS X (Snow Leopard) and Linux (Fedora 12), FlightGear seems to
completely ignore the $FG_SCENERY variable. The only way to tell
FlightGear where to look for scenery is via the --fg-scenery command-line
switch.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
The code is still there to look for the environment variable - did this definitely work in the past? The code in
question hasn't changed much in years, so some idea when this stopped working would be useful. One
possibility is that specifying --fg-root on the command-line is over-writing this value, but that's a complete
guess.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: zakalawe@mac.com
(No comment was entered for this change.)
Labels: Sim
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: Armande.... (code.google.com)@gmail.com
Re: Comment 1
Even if I remove my ~/.fgfsrc file, my ~/.fgfs/ directory, unsetenv FG_ROOT, and not
use --fg-root, I still get nothing. However, if I use --fg-scenery=$FG_SCENERY,
everything's okay. It's strange.
As I recall, it worked before. However, at that time I also kept my extra scenery in
$FG_ROOT/Scenery-Terrasync; I moved it to ~/Scenery-Terrasync. I'd be willing to
believe that the move might have broken something. On the other hand, I can't see it
explaining how --fg-scenery=$FG_SCENERY works.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: anders.g... (code.google.com)@gmail.com
Are you using ~/ when you set FG_SCENERY? If it isn't expanded before being stored in FG_SCENERY that will fail as FlightGear doesn't expand ~/ while when put on the command line with --fg-scenery=$FG_SCENERY the shell might. I use $HOME/ when setting up my FG_SCENERY variable and that works fine.
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: anders.g... (code.google.com)@gmail.com
No further info from the reporter and as FG_SCENERY certainly works on Linux I close this issue.
Status: Invalid
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Status: Temp
View and moderate all "codetickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: bre... (code.google.com)@gmail.com
(No comment was entered for this change.)
Status: Invalid