Hi there,
READ ALLOW $FG_ROOT/*
READ ALLOW $FG_HOME/*
READ ALLOW $FG_AIRCRAFT/*
READ ALLOW $FG_SCENERY/*
Those are in my IOrules, so really that *should* cover everything, but when
trying to run the UFO I got denied access to ~/.fgfs and another folder within
the Scenery folder. I added those
I have FlightGear 2.0.0 installed and working. However, I need the
latest code to integrate some changes to be submitted later once
everything is tested.
When I build the latest pull from Git (SimGear/FlightGear and using the
latest fgdata), Everything seems to startup fine except I just
Where is the scenery located?
Try --prop:sim/paths/use-custom-scenery-data=false
Scott.
On Sun, 2011-07-03 at 00:50 -0700, Chris Wilkinson wrote:
Hi there,
READ ALLOW $FG_ROOT/*
READ ALLOW $FG_HOME/*
READ ALLOW $FG_AIRCRAFT/*
READ ALLOW $FG_SCENERY/*
Those are in my
Hi Scott,
That prop was set to true, so specifying false on the command line fixes the
missing object problem.
jetways.nas contains reference to that prop, but nothing else in fgdata seems
to. Where is fg looking for scenery if the prop is set to true I wonder?
Thanks mate,
Best regards
On Sun, 03 Jul 2011 02:20:48 -0700, Bruce wrote in message
4e103470.3070...@celebritycc.com:
I have FlightGear 2.0.0 installed and working. However, I need the
latest code to integrate some changes to be submitted later once
everything is tested.
When I build the latest pull from Git
Le 03/07/2011 11:20, Bruce Hellstrom a écrit :
I have FlightGear 2.0.0 installed and working. However, I need the
latest code to integrate some changes to be submitted later once
everything is tested.
When I build the latest pull from Git (SimGear/FlightGear and using
the latest
On 03.07.2011 02:52, Scott wrote:
On Sat, 2011-07-02 at 18:39 -0600, Ron Jensen wrote:
On Saturday 02 July 2011 17:52:23 Chris Wilkinson wrote:
I re-read the messages on starting and I see...
loadxml: reading '' denied (unauthorized access)
This has nothing to do with Nasal IORules. There
On 03.07.2011 14:37, Citronnier - Alexis Bory wrote:
Le 03/07/2011 11:20, Bruce Hellstrom a écrit :
Warning: TangentSpaceGenerator: unknown primitive mode 9
Ignore that message. It's not related.
This is on Linux and I'm using the same dependent versions I was
using for 2.0.0 including
Let's start our traditional discussion about what aircraft should be in the
base package of the next release (2.4.0).
We currently have
- 777-200
- A6M2
- b1900d
- bo105
- c172p
- CitationX
- Dragonfly
- dhc2
- f-14b
- Cub
- SenecaII
- sopwithCamel
- ufo
- ZLT-NT
Should we change this setup?
Torsten
Let's start our traditional discussion about what aircraft should be in
the
base package of the next release (2.4.0).
We currently have
- 777-200
- A6M2
- b1900d
- bo105
- c172p
- CitationX
- Dragonfly
- dhc2
- f-14b
- Cub
- SenecaII
- sopwithCamel
- ufo
- ZLT-NT
Hi Bruce,
this is how I configure osg (3.0.0 ATM):
reconfigure.sh --
#!/bin/sh
export CFLAGS=-g -O3 -fPIC
export CXXFLAGS=-g -O3 -fPIC
cmake -D CMAKE_BUILD_TYPE:STRING=Release -D \
CMAKE_INSTALL_PREFIX:PATH=/opt ../../osg/
reconfigure.sh
Chris Wilkinson wrote:
What I do when I update fgdata is I keep a backup copy of the fresh
pull, along with a backup copy of the old fgdata complete with my
custom stuff. When I say I 'merge' the folders I take a copy of the
fresh pull, copy that to a location to use as my 'live' folder,
Torsten Dreyer wrote:
Should we change this setup?
I'm in favour of leaving the selection as-is - simply for the practical
purpose of saving us from the usual flame war :-)
Cheers,
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
There is nothing contradictory. Prior to the latest git pull (for me, was
couple of months ago) flying at KSFO I remember seeing A/C sitting at the
terminals and a lot of placed objects like power pylons etc around the vicinity
of KSFO. When I try KSFO now with
On Sunday, July 03, 2011 10:28:41 AM Roland Häder wrote:
Hi Bruce,
this is how I configure osg (3.0.0 ATM):
reconfigure.sh --
#!/bin/sh
export CFLAGS=-g -O3 -fPIC
export CXXFLAGS=-g -O3 -fPIC
cmake -D CMAKE_BUILD_TYPE:STRING=Release -D \
Chris Wilkinson wrote:
How should default and custom scenery be arranged?
In different directories, that's what --fg-scenery=path is for -
see:
http://www.flightgear.org/Docs/getstart/getstartch3.html#x8-450003.5.1
and
Is FG compatible with OSG3?
Hal
I have successfully compiled and launched it. So it is compatible. :)
Roland
signature.asc
Description: This is a digitally signed message part
--
All of the data generated in your IT
Thanks to everyone who replied. I'm pretty good at managing different
versions of FG on the same machine, but this is the first time I had to
deal with a different version of OSG.
I compiled OSG 3.0.0 and set it to install the libraries and such to the
same prefix I use for the latest FG/SG
While I do not disagree with a habit of keeping default and custom scenery
separate, I foresee a problem arising from doing so. This is because I do not
have custom scenery for all of the area I like to fly in (which covers
Australasia and the Pacific Islands). Most of that regions scenery I
Ok, I'm up and running on OSG 3.0.0. It seems the segmentation fault
was due to me not doing a complete make distclean before trying to
reconfigure FG/SG.
Now once I got past that, I had the same issue with no display except
the sky color. Turns out the issue was with something left over in
20 matches
Mail list logo
