> Try adding --prop:sim/paths/use-custom-scenery-data=false to the command
> line. I had the same issue, and thanks to help from list members that
> was and still is the only way my custom scenery can work with
> git/2.4.0...
I don't have a clear understanding why, but that fixes the issue.
* Tho
Hi there
From: "thorsten.i.r...@jyu.fi"
To: FlightGear developers discussions
Sent: Thursday, 18 August 2011 5:08 PM
Subject: Re: [Flightgear-devel] Two strange issues
>> 2) I have the Corse custom scenery
>>
>> http://helijah.fr
>> 2) I have the Corse custom scenery
>>
>> http://helijah.free.fr/flightgear/scenes.html#Corse
>>
>> installed under my FG 2.0.0 FGData. With my GIT version, I don't
>> actually
>> have any scenery under FGData but instead use the commandline option
>>
>> --fg-scenery=/usr/share/FlightGear-2.0.0/S
On Aug 16, thorsten.i.r...@jyu.fi wrote:
Hello
> 2) I have the Corse custom scenery
>
> http://helijah.free.fr/flightgear/scenes.html#Corse
>
> installed under my FG 2.0.0 FGData. With my GIT version, I don't actually
> have any scenery under FGData but instead use the commandline option
>
> -
Two things which might be worth mentioning (both with recent GIT, pulled
and compiled ~ a week ago)
1) One of my rendering performance benchmark tests is to use the ufo
transport it, using the location dialog, exactly 30.000 ft over the
starting position (then increase FOV to 120 deg and create w
5 matches
Mail list logo