Hi all
Ok, can we have a decision that SimGear/FlightGear is not supporting OSX 10.5
on intel anymore ? FG 2.8 is doable, and maybe 2.10 with some further tweaks
too, but after looking to what's coming up with "next" I see that more and more
tweaks are needed and that core developers do not tak
Hi Thorsten
Since work has eaten up most of my free time, i did not update fgdata since
today and want to report that the flickering in the airfield are is gone.
Looks great now and transition and landmass works up to level 5 with
atmospheric light scattering enabled.
(without atmospheric light sc
Hi Torsten
What does mean "no public answer" in this list for this decision ?
-Yves
Am 15.02.2013 um 16:16 schrieb Torsten Dreyer :
> Hi all,
>
> at one point during every ILS approach you reach the decision altitude
> with two options: "continue approach" or "go around". Being the copilot
-Original Message-
From: James Turner
Sent: Tuesday, September 18, 2012 12:42 PM
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] Aircraft Checklists
On 18 Sep 2012, at 11:56, Stuart Buchanan wrote:
> Feedback and comments are welcome as always, particularly if an
On 15 Feb 2013, at 15:35, Anders Gidenstam wrote:
> The user interface issue can be handled by hiding the controls from those
> who do not want the complexity. (Hidden by default, obviously.)
Exactly.
James
--
Free
On Fri, 15 Feb 2013, Renk Thorsten wrote:
>
> Okay, after sleeping over this and going over all the feedback on this
> list:
...
> But having a dropdown menu for season selection to drive a continuous
> season model by pixel postprocessing just makes no sense, it's a waste
> of perfectly good
I would just add a quick last minute request to the developers (or anyone
else). We haven't organized an effort to collect screen shots for the
v2.10 release yet and I'd like to do that now. If anyone is
interested/willing to submit v2.10 screen shots (based on the release
candidates or other pre
Hi all,
at one point during every ILS approach you reach the decision altitude
with two options: "continue approach" or "go around". Being the copilot
on our approach into the 2.10 release, I'd call out "minimum, approach
lights in sight, continue!"
If no one shouts out loudly _NOW_, I'm going
On Fri, Feb 15, 2013 at 9:33 AM, Erik Hofman wrote:
> On 02/15/2013 10:00 AM, Renk Thorsten wrote:
>> So I will remove the option from GIT again and clear out the *-autumn.png
>> textures in the next days and develop this further for my own private
>> enjoyment (with the understanding that I'll
On 02/15/2013 10:00 AM, Renk Thorsten wrote:
> So I will remove the option from GIT again and clear out the *-autumn.png
> textures in the next days and develop this further for my own private
> enjoyment (with the understanding that I'll make it available on request to
> anyone interested), w
On Fri, 15 Feb 2013 08:48:59 +, James wrote in message
<954f9f95-7614-4c0e-a82f-3b589fa4e...@mac.com>:
>
> On 14 Feb 2013, at 18:58, HB-GRAL wrote:
>
> > With simple -DCMAKE_INSTALL_PREFIX it finds the "custom location"
> > of the headers and libs without any other option, but when I add
Hi James
Thanks, yes, am aware of this kind of separation. But I thought: "Why does
cmake configuration make it possible to link against an osg include and lib dir
for every part, while simgear has only a an option for headers and not the libs
?". And then when you set the simgear include dir,
Okay, after sleeping over this and going over all the feedback on this list:
My original idea was that the whole concept of a continuous season model in
combination with a user-customizable environment by pixel processing is a big
thing - I doubt many other simulators have something like this (
On 14 Feb 2013, at 18:58, HB-GRAL wrote:
> With simple -DCMAKE_INSTALL_PREFIX it finds the "custom location" of the
> headers and libs without any other option, but when I add
> -DSIMGEAR_INCLUDE_DIR=/path/to/include it takes the headers from this
> location, but not the libs anymore, it fall
It seems we have some cases where the ufo trick ctrl-alt-click does not report
the correct landclass - I would assume that the underlying call is geodinfo()
going wrong.
http://www.flightgear.org/forums/viewtopic.php?f=5&t=19113
The theme seems to be that if I have two different materials def
15 matches
Mail list logo
