Well I checked it locally in my development environment where I am
working on the better exception handling patch, and with the KLAX I
found 2 instances of failure to open
/home/vassilii/flightgear.nobackup/FlightGear/data/Models/fgfsdb/radio-tall.xml
whereas
/home/vassilii/flightgear.nobackup/Flig
On Nov 23, 2005, at 12:14 PM, Martin Spott wrote:
Adam Dershowitz wrote:
2) If I start with --enable-clouds3d then I just don't get any of
the low level clouds to show up at all. In other words, without that
feature, I get clouds at 5,000 feet, but with that flag I don't get
any, but I don'
On Nov 22, 2005, at 11:31 PM, Vassilii Khachaturov wrote:
1) If I fly out of an airport that is located out of the included
sample scenery, then at the command line I get: "Failed to open
file" repeated twice. I am using 0.9.8 scenery in that case, because
that is all that is available. But
Adam Dershowitz wrote:
> 2) If I start with --enable-clouds3d then I just don't get any of
> the low level clouds to show up at all. In other words, without that
> feature, I get clouds at 5,000 feet, but with that flag I don't get
> any, but I don't see any errors either. [...]
Could you
> 1) If I fly out of an airport that is located out of the included
> sample scenery, then at the command line I get: "Failed to open
> file" repeated twice. I am using 0.9.8 scenery in that case, because
> that is all that is available. But there is no indication of what
> files are not openin
I am not sure of the status of each of these.
I am using the release code of 0.9.9 on a Mac 10.4 gcc 4.0.1.
1) If I fly out of an airport that is located out of the included
sample scenery, then at the command line I get: "Failed to open
file" repeated twice. I am using 0.9.8 scenery in th
