On Wednesday 24 October 2007 00:15, Vivian Meazza wrote:
Not here, I'm afraid. Very good frame rates using the Buccaneer (70+) but
there are still noticeable pauses over land. None over the ocean tiles. The
pauses, or hesitations do not seem to be associated with any Subsystem
Timing Alert,
Georg Vollnhals
Sent: 23 October 2007 23:34
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] FlightGear/Plib periodic stutter notes
Vivian Meazza schrieb:
Not here, I'm afraid. Very good frame rates using the
Buccaneer (70+)
but there are still noticeable
Durk
Sent: 24 October 2007 07:22
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] FlightGear/Plib periodic stutter notes
On Wednesday 24 October 2007 00:15, Vivian Meazza wrote:
Not here, I'm afraid. Very good frame rates using the
Buccaneer (70+)
but there
Heiko Schulz
Sent: 23 October 2007 23:55
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] FlightGear/Plib periodic stutter notes
Hi,
Couldn't test it, waiting that someones will do a
precompiled binary for windows.
But it sounds good, very good though at least
Mike Yukish wrote:
More questions!
So how do I change the direction in which I am viewing and the position
that I am viewing from? I did not see them in the list of properties, which
seemed like a good guess on where they'd be. The camera balls on aircraft
typically are hanging below the
The Seneca is special in that it attaches listeners to YASim
internal properties, which are updated multiple times per
frame, unlike most other listeners, which run *at most* once
per frame, but actually very rarely.
Oh - wasn't it using JSBSim as fdm!?
I hope that the stuttering is fixed
I was just a bit worried since it seems that there was always a
problem when it tried to download that specific file.. - But as i
think about it- you may actually be right... i dont know enough about
how its being loaded so who knows :-)
Okay, i have to give it a try as soon as i get home to my
* Torsten Dreyer -- Wednesday 24 October 2007:
The Seneca is special in that it attaches listeners to YASim
internal properties, which are updated multiple times per
frame, unlike most other listeners, [...]
Oh - wasn't it using JSBSim as fdm!?
Indeed. I remembered that wrongly because
Hi guys,
Thanks to the person who gave me pointers on how to correct the plib compile
problem. I still have another problem though. I get the following error when
I try to compile FlightGear-0.9.11-pre1
est-epsilon.c:13:19: error: GL/glut.h: No such file or directory
est-epsilon.c: In function
On 10/24/07, Nick Othieno [EMAIL PROTECTED] wrote:
I checked for the file glut.h in the FlightGear-0.9.11-pre1 directoty
structure but it isn't there. Does anyone have ideas? I thought of excluding
the whole test directory from the compile but I'm not sure of the effect.
Install glut
glut.h comes with your glut installation. If you don't have glut
installed, try freeglut at http://freeglut.sourceforge.net/ If you're
in Linux the header files will probably be stored in /usr/share/include
or similar depending on distro.
Jonathan Wagner
Nick Othieno wrote:
Hi guys,
Heiko,
I applied the patches to plib branch (I get runtime errors with FG link
against OSG 2.2 that I haven't figured out):
http://www.rato.us/flightgear/builds/plib/20071024plibexe.zip
-Reagan
On 10/23/07, Heiko Schulz [EMAIL PROTECTED] wrote:
Hi,
Couldn't test it, waiting that someones
Ill write as soon as i know anything.
Nope the problem still exists - still breaks down the same place.. :-(
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now
Hello Nick,
seems you are about to go a long way.
For windows ( and free Microsoft compiler ) you might find useful the
following page http://www.sim-ai.org/FlightGearlesson.htm ( one of the
draft of set of lessons ) where all code is already compiled and tested (
for where to get compiler
On Wednesday 24 October 2007 11:21, Melchior FRANZ wrote:
[snip...]
Listeners should be used on properties to get notice about
occasional changes. In cases where we *know* when the property
changes -- once per loop or more often -- we can have the same
result cheaper with a loop. (Listeners
Hi Sergey,
Thanks. I have just sorted out that problem. I run FC5 and it seems the
freeglut rpm did not install the glut sources so I just compiled and
installed it. However, after doing that, I run into this error:
gl-info.o: In function `main':
/root/FlightGear-0.9.11-pre1/tests/gl-info.c:61:
Hi Nick
I used freeglut http://freeglut.sourceforge.net/ with FlightGear
Regards
Sergey
On 10/24/07, Nick Othieno [EMAIL PROTECTED] wrote:
Hi Sergey,
Thanks. I have just sorted out that problem. I run FC5 and it seems the
freeglut rpm did not install the glut sources so I just compiled and
On 10/24/07, Nick Othieno [EMAIL PROTECTED] wrote:
It is still a GLUT error but I don't know how to sort it out. What is the
irc channel url? I want to set it up on gaim.
Did you re-run configure (with the correct options, if you didn't
install glut in a standard location)? Looks like it is
This is starting to enter the realm of my own opinions so please keep that
in mind.
Nasal was never intended to do work at this low level. However, the fact
that it can be used to successfully model an advanced flight control system
[mostly successfully] says a lot about the capabilities of
* leee -- Wednesday 24 October 2007:
the FDM operates at a fixed rate (I believe the default is 120 Hz)
but nearly everything else, afaikt, operates at the frame rate,
which varies.
Yes, but most Nasal code does things that influence visuals/sound
(like instrument stuff, view handling, etc.),
Hi Curt,
thought I'd better switch the subject line:)
Using C/C++ for this sort of subsystem is probably the best choice and
would certainly be the best way to go once an effective framework had
been developed but at the stage I was working at, I was just trying to
find out if the ideas and
On Wednesday 24 October 2007 18:30, Melchior FRANZ wrote:
* leee -- Wednesday 24 October 2007:
the FDM operates at a fixed rate (I believe the default is 120 Hz)
but nearly everything else, afaikt, operates at the frame rate,
which varies.
Yes, but most Nasal code does things that
* leee -- Wednesday 24 October 2007:
the A/P controllers and filters, which were the real problem, are
independent of Nasal and would remain a problem until they could
guarantee a fixed rate regardless of the frame rate.
The FDM doesn't run at a fixed rate, either, AFAIK. Yes, it runs
120
FYI: this bug is now fixed in CVS, albeit in a different
way, so it's a good idea to revert that last patch in your
local copies.
m.
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find
On Wednesday 24 October 2007 19:15, Melchior FRANZ wrote:
* leee -- Wednesday 24 October 2007:
the A/P controllers and filters, which were the real problem, are
independent of Nasal and would remain a problem until they could
guarantee a fixed rate regardless of the frame rate.
The FDM
Csaba Halász wrote:
Don't know if Melchior and Andy have arrived at anything while I was
away, but here is what I found.
Yup, that's exactly it. New nasal objects are added to a temporary
bin when they are created, because further allocation might cause a
garbage collection to happen before
On 10/24/07, leee wrote:
Hmm... I always thought that it ran asynchronously from the rest of FG,
at a steady rate. Surely this can't be a good thing?
It really seems to me that the only subsystem in FG where variable
timing won't cause a problem is the display, where it doesn't matter if
Thanks for the info. I successfully compiled. Now when I run fgfs, I get the
following error:
Model Author: Unknown
Creation Date: 2002-01-01
Version: $Id: c172p.xml,v 1.18 2007-01-15 12:50:45 ehofman Exp $
Description: Cessna C-172
Audio initialization failed!
Could not
On Wednesday 24 October 2007 19:41, Curtis Olson wrote:
On 10/24/07, leee wrote:
Hmm... I always thought that it ran asynchronously from the rest of
FG, at a steady rate. Surely this can't be a good thing?
It really seems to me that the only subsystem in FG where variable
timing won't
29 matches
Mail list logo
