Hi,
I've tried different solutions with the source into
simgear/scene/model/animation.cxx (mostly reverting some changes), even
if I haven't found anything that I was able to clearly identify as the
origin of my problem.
So I'm now using a workaround: I add a binding in each involved action
Hello all,
I am trying to get SimGear 1.9.0 built, in order to build TerraGear
to try some scenery building. I patched the sources to get around the
alut problem, but then found that the OpenAL framework is PPC only. I
downloaded again from http://mac.softpedia.com/get/Development/
On Wed, Dec 16, 2009 at 5:31 PM, Alexis Bory - xiii wrote:
Yes he dares !
http://flightprosim.com/screenshots/SNAG-0281.jpg
Now I'm winding! (Picture my right arm making a reverse windmill motion)
:-)
I bet he didn't get permission from google to post/use google map imagery
(like we did on
Alexis Bory - xiii wrote:
http://flightprosim.com/screenshots/SNAG-0281.jpg
In the meantime the link has already been replaced with another
screenshot - still based on copyrighted material
Holy cow, I'm impressed to see this guy is managing to to drop one
clanger after another :-)
On Thu, 17 Dec 2009, Martin Spott wrote:
Alexis Bory - xiii wrote:
http://flightprosim.com/screenshots/SNAG-0281.jpg
In the meantime the link has already been replaced with another
screenshot - still based on copyrighted material
Holy cow, I'm impressed to see this guy is managing to
I couldn't find the cause in simgear/scene/model/animation.cxx because
the solution is in $FG_SRC/src/Input/FGMouseInput.cxx :).
Attached a patch to get the old behaviour back.
Can it be commited please?
Thank you for interest.
regards
seb
Sébastien MARQUE wrote :
Hi,
I've tried different
I had a squawk here from a (real) King Air pilot because on an ILS approach,
our glideslope indicator doesn't become active/in-range until about 7-8
miles out. Beyond this range the indicator just stays centered at zero.
With a standard 3 degree glide slope, 7 miles out equates to about 2000'
On 17 Dec 2009, at 18:44, Curtis Olson wrote:
I don't have personal knowledge of what is correct, but this change to
glideslope range impacts our ability to practice ILS approaches and I have a
current King Air pilot complaining about the behavior. Pulling out some old
approach plates
This one is interesting too ...
Says Flightgear in the Window title :)
http://flightprosim.com/screenshots/SNAG-1420.jpg
On 12/17/09, Curtis Olson curtol...@gmail.com wrote:
On Wed, Dec 16, 2009 at 5:31 PM, Alexis Bory - xiii wrote:
Yes he dares !
Hi guys ,
I'ma bit concerned about the material animation being part of the shader
group ... I have no instrument lights if shaders are off , which is a bad
idea in my opinion ...
I see other odd effects with liveries too .
Am I worrying needlessly , or just not understanding the current
On Thu, Dec 17, 2009 at 1:25 PM, James Turner wrote:
On 17 Dec 2009, at 18:44, Curtis Olson wrote:
I don't have personal knowledge of what is correct, but this change to
glideslope range impacts our ability to practice ILS approaches and I have a
current King Air pilot complaining about
Consulting my course material for passing the ATPL tests in Europe I
read that the glide path is required to be usable up to a distance of 10
NM (which I interpret from the touch down zone not the distance to an
DME that may or may not be at destination). This distance should be
valid +-8
I would assume he must be on the FG-devel mailing list?
Peter
Peter Brown
FG Farmboy
On Dec 17, 2009, at 10:35 AM, Martin Spott wrote:
Alexis Bory - xiii wrote:
http://flightprosim.com/screenshots/SNAG-0281.jpg
In the meantime the link has already been replaced with another
On Thu, Dec 17, 2009 at 9:21 PM, adams@gmail.com wrote:
Hi guys ,
I'm a bit concerned about the material animation being part of the shader
group ... I have no instrument lights if shaders are off , which is a bad
idea in my opinion ...
I see other odd effects with liveries too .
Am I
14 matches
Mail list logo
