Syd,
Syd Adams wrote:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/b1900d
In directory baron.flightgear.org:/tmp/cvs-serv18391
Modified Files:
b1900d-set.xml b1900d.xml b1900dsplash.rgb instrumentation.xml
Removed Files:
b1900d-sound.xml
Log Message:
Converting to
Martin Spott wrote:
Syd,
Converting to OSG , a lot of small updates stll to do...
Added a simple nasal gpws since the mk-viii appears to misbehave...
Did you already communicate the issue about the MK-VIII to other
developers in order to get it fixed ?
Yes, please report any
On 22 Sep 2008, at 08:20, Erik Hofman wrote:
Did you already communicate the issue about the MK-VIII to other
developers in order to get it fixed ?
Yes, please report any problems that (seems to) have been introduced
recently, there was a lot of needed overhauling and just leaving it
buggy
On mercredi 17 septembre 2008, gerard robin wrote:
Hello,
Running without any problem with FG on a 32 bits computer (which my usual
computer)
recently, I have had to build FlightGear on a 64 bit computer with FC9.
Both computers have the same GPU (Nvidia 7800 GS AGP 8).
I was disappointed
Martin Spott wrote:
Syd,
Converting to OSG , a lot of small updates stll to
do...
Added a simple nasal gpws since the mk-viii
appears to misbehave...
Did you already communicate the issue about the
MK-VIII to other
developers in order to get it fixed ?
Yes,
Heiko Schulz wrote:
So much as I know James Turner is working on that.
And the MKVIII was never ever working right, I can understand Syd doing a
workaround.
Last time I heard he was awaiting feedback.
Erik
-
This
On Monday 22 September 2008 12:16:13 gerard robin wrote:
Again on that topic, i was wrong about 64 bit , which has nothing to do
with the stutter/jitter within FG.
That's true (since we've seen the same stuttering on 32 bit machines as well).
However, even though in your case disabling fancy
On Mon, Sep 22, 2008 at 7:54 AM, AJ MacLeod wrote:
On Monday 22 September 2008 12:16:13 gerard robin wrote:
Again on that topic, i was wrong about 64 bit , which has nothing to do
with the stutter/jitter within FG.
That's true (since we've seen the same stuttering on 32 bit machines as
On Thu, 2008-09-18 at 16:45 -0400, Geoff wrote:
Hello all -
I have added a menu item to the Environment which brings up a dialog
with some data fields for the user to fill in.
My question is: what do I do when the property field doesn't exist?
How do I create a new one and where can I
On Mon, Sep 22, 2008 at 8:05 AM, Geoff wrote:
On Thu, 2008-09-18 at 16:45 -0400, Geoff wrote:
Hello all -
I have added a menu item to the Environment which brings up a dialog
with some data fields for the user to fill in.
My question is: what do I do when the property field doesn't
Heiko Schulz wrote:
And the MKVIII was never ever working right, I can understand Syd doing a
workaround.
Well, participating in a 'club' like this one and not giving reasonable
feedback doesn't count as good habits
BTW, a quick search on The Net revealed this thread - I suspect you
On lundi 22 septembre 2008, Curtis Olson wrote:
I am hearing a pretty distinct glitch in the audio about once per second
... it's not so much of a hard break, but disruption in continuity. I'm
not sure if this is related to a pause in FlightGear, or the openal drivers
on Fedora 9, or what?
Well, participating in a 'club' like this one and
not giving reasonable
feedback doesn't count as good habits
Maybe- But I think Syd will have a lot reasons for that. Nasal scripting is a
lot of easier than C++ - so it is a nice workaround. And very often better than
hardcoded.
O.k.
Yep, it's entirely possible that I messed up aspects of
the GPWS, but
I need a better test case than 'acting weird'. Most
of all, I need to
know an aircraft where it definitely worked correctly in
the past,
because it's never worked 'well' for me in any
version of FG. I'm not
Heiko Schulz wrote:
The last errors I had were:
-Bank-Angle-Callouts with real zero-angle after lift off or shortly above rwy
while landing.
- the callouts 50 40 30 20 10 could be never heard at all- even
with a very low sink rate
Low-Terrain-warning on a corrct ILS-glidepath
2008/9/21 Stuart Buchanan [EMAIL PROTECTED]
Tried apply the patch, but got
patch: malformed patch at line 50: Index: Environment/fgclouds.cxx
And, can you make some screenshots, please?
--
---
WBR, Vadym.
-
This
Vadym Kukhtin wrote:
2008/9/21 Stuart Buchanan [EMAIL PROTECTED]
Tried apply the patch, but got
patch: malformed patch at line 50: Index: Environment/fgclouds.cxx
I didn't try it myself, but in general I'd say: If you require external
help to get the patch applied cleanly, then this
Heiko Schulz wrote:
But the real problem is, that nobody really knows how the stuff is
really working and how to activate them.
Well, this sounds like a case for a knowledgeable person to explain
instead of silently working around it
Martin.
--
Unix _IS_ user friendly - it's
AJ wrote
On Monday 22 September 2008 12:16:13 gerard robin wrote:
Again on that topic, i was wrong about 64 bit , which has nothing to do
with the stutter/jitter within FG.
That's true (since we've seen the same stuttering on 32 bit machines as
well).
However, even though in your
Hi Vivian,
Vivian Meazza wrote :
As you know, I am. I have profiled the cvs-head. Nasal/hash.c seems to
be a _very_ significant CPU hog, but I can't link it to the staggers. I
note however that when I profile an old FG/osg from last Apr, it is stagger
free, and hash.c doesn't figure in the
Hi Fred,
Fred wrote:
Hi Vivian,
Vivian Meazza wrote :
As you know, I am. I have profiled the cvs-head. Nasal/hash.c seems to
be a _very_ significant CPU hog, but I can't link it to the staggers. I
note however that when I profile an old FG/osg from last Apr, it is
stagger
free,
Vivian Meazza wrote:
As you know, I am. I have profiled the cvs-head. Nasal/hash.c seems to be a
_very_ significant CPU hog, but I can't link it to the staggers. I note
however that when I profile an old FG/osg from last Apr, it is stagger free,
and hash.c doesn't figure in the profiling.
`Did you already communicate the issue about the MK-VIII to other
evelopers in order to get it fixed ?
Martin.
A long long time ago I tried to contact Jean for pointers no
response...
Well, this sounds like a case for a knowledgeable person to explain
instead of silently
Syd wrote:
In the meantime , IRC is a much freindlier , helpful place.
Unfortunately IRC (like the forum) is not the place where problems are
solved, only the developers mailinglist is. This is because not everyone
can follow all he places where discussions are taking place.
Erik
Syd,
Syd wrote:
`Did you already communicate the issue about the MK-VIII to other
evelopers in order to get it fixed ?
[..]
Well, this sounds like a case for a knowledgeable person to explain
instead of silently working around it instead of silently working around
it
So I
Hi!
Here are some fixes for the mingw platform that I had to make for a
successful build.
Note, in 2 places I have changed a #include windows.h to a #include
Winsock2.h, but that should be ok. For safety, somebody using msvc
build please check.
As a result, a current mingw build (includes osg)
On lundi 22 septembre 2008, Vivian Meazza wrote:
Hi Fred,
Fred wrote:
Hi Vivian,
Vivian Meazza wrote :
As you know, I am. I have profiled the cvs-head. Nasal/hash.c seems to
be a _very_ significant CPU hog, but I can't link it to the staggers. I
note however that when I profile
Hi Erik
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] FlightGear on 32 bits versus 64 bits
system
Vivian Meazza wrote:
As you know, I am. I have profiled the cvs-head. Nasal/hash.c seems to
be a
_very_ significant CPU hog, but I can't link it to the staggers. I
gerard
On lundi 22 septembre 2008, Vivian Meazza wrote:
Hi Fred,
Fred wrote:
Hi Vivian,
Vivian Meazza wrote :
As you know, I am. I have profiled the cvs-head. Nasal/hash.c seems
to
be a _very_ significant CPU hog, but I can't link it to the
staggers. I
note
On 22 Sep 2008, at 22:25, Vivian Meazza wrote:
AJ and I _think_ we are talking about the same problem. We might not
be,
although the description of the symptoms, which we have discussed many
times, seems to be the same. The underlying cause might not be the
same. It
might be the code,
On lundi 22 septembre 2008, Vivian Meazza wrote:
gerard
On lundi 22 septembre 2008, Vivian Meazza wrote:
Hi Fred,
Fred wrote:
Hi Vivian,
Vivian Meazza wrote :
As you know, I am. I have profiled the cvs-head. Nasal/hash.c seems
to
be a _very_ significant
James
On 22 Sep 2008, at 22:25, Vivian Meazza wrote:
AJ and I _think_ we are talking about the same problem. We might not
be,
although the description of the symptoms, which we have discussed many
times, seems to be the same. The underlying cause might not be the
same. It
might
On 22 Sep 2008, at 23:05, Vivian Meazza wrote:
A binary search, which I'm also trying, takes days. At some point we
left
OSG 2.4, used an interim version, then migrated to osg 2.6. An osg
rebuild
here takes well over an hour. So far, I've come about halfway
forward from
Apr, which
On Mon, Sep 22, 2008 at 5:23 PM, James Turner wrote:
On 22 Sep 2008, at 23:05, Vivian Meazza wrote:
A binary search, which I'm also trying, takes days. At some point we
left
OSG 2.4, used an interim version, then migrated to osg 2.6. An osg
rebuild
here takes well over an hour. So
On 23 Sep 2008, at 20:26, Syd wrote:
So I gather your telling me I can't change my aircraft ? The gpws
issues
have been known for a long time , and I,m sure you well know that .
I wont post bugs here because of exactly this My past questions
were largely ignored , my minor patches
James Turner wrote:
The problem seems to be very bad in the case of the GPWS, because it's
actually a very complex instrument, and the author (who seems to
be ... absent?) clearly put in a lot of very accurate functionality,
but almost no documentation. Because it's so complex, I assume
36 matches
Mail list logo
