On Sunday 30 March 2003 15:10, David Megginson wrote:
David Luff writes:
OK, that's it!!! - ATC did *not* break TuxRacer ;-)
Are you sure?
All the best,
David
LOL!
Well .. it may not have!
It could have possibly been something that I installed to enable TerraGear to
be installed.
One of the jobs of the ATC manager is to spread the ATC load by only updating a
maximum of one ATC station each frame, and it is assumed that the manager itself
will run at full simulation fidelity. Updating only once every 2 seconds would mean
a noticable lag between selecting a frequency
On 3/30/03 at 2:33 PM Curtis L. Olson wrote:
My concern is that if the atc manager update is taking me from 60hz
down to 20hz means it could be consuming on the order of 30
milleseconds per call. Simply calling it once every 2 seconds will
impose a 30ms hitch in the frame rate every 2 seconds
On 3/31/03 at 10:51 AM [EMAIL PROTECTED] wrote:
Could the ATC manager be implemented as a low-priority thread which is
woken up every so often (few seconds) to update the list of distances to
the ground stations, and additionally if a frequency is changed? The
realtime loop would then always have
On Mon, 31 Mar 2003 01:32:57 -0700,
WillyB [EMAIL PROTECTED] wrote in message
[EMAIL PROTECTED]:
On Sunday 30 March 2003 15:10, David Megginson wrote:
David Luff writes:
OK, that's it!!! - ATC did *not* break TuxRacer ;-)
Are you sure?
LOL!
Well .. it may not have!
..fwiw, I
Erik Hofman wrote:
With the capital letter?
It would be winderfull if you would use the FGSubsystem class and rename
the to init() and update()
Never mind. I see you are using that already.
Good work.
Erik
___
Flightgear-devel mailing list
[EMAIL
OK, the line of code causing the frame rate hit was the following:
if((fabs(xyp.y() - xyc.y()) ((runway.length/2.0) + 5.0))
(fabs(xyp.x() - xyc.x()) (runway.width/2.0))) {
return(true);
}
return false;
To simplify things, I broke it down into a few more lines:
double
On Monday 31 March 2003 05:29, Jim Wilson wrote:
WillyB [EMAIL PROTECTED] said:
On Sunday 30 March 2003 15:10, David Megginson wrote:
David Luff writes:
OK, that's it!!! - ATC did *not* break TuxRacer ;-)
Are you sure?
All the best,
David
LOL!
Well .. it
On 3/31/03 at 2:38 PM David Luff wrote:
Replacing the offending line:
return((ldiff rlen) (wdiff rwidth));
with the somewhat more verbose
if(ldiff rlen) {
return(wdiff rwidth);
} else {
return(false);
}
cures it completely! Am I doing something really daft, or is this a
David Luff writes:
I'm doing something daft - forget this post - the above both drop the frame
rate. The reason the return(false) fix fixes it is because then the
function doesn't get called any more!
Where's that brown paper bag when you need it??
A long time ago, when faced with things
On 3/31/03 at 4:52 PM David Luff wrote:
I'm doing something daft - forget this post - the above both drop the
frame
rate. The reason the return(false) fix fixes it is because then the
function doesn't get called any more!
And here's the root cause - I was reading in the almost-one-megabyte
David Luff [EMAIL PROTECTED] wrote:
On 3/30/03 at 2:33 PM Curtis L. Olson wrote:
I understand that ATC is a work in progress, but something needs to be
done before I go into a complete panic. :-)
OK, I've committed an emergency fix - perhaps you could test again when
Minnesota wakes up and
On Monday 31 March 2003 09:31, Andy Ross wrote:
David Luff wrote:
William McRaven wrote:
I downloaded the CVS last week .. tues or wed .. and installed it.
The frame rate went to.. very bad. basically made flightgear
unflyable.. It also made regular flightgear unflyable .. the
WillyB [EMAIL PROTECTED] said:
On Sunday 30 March 2003 15:10, David Megginson wrote:
David Luff writes:
OK, that's it!!! - ATC did *not* break TuxRacer ;-)
Are you sure?
All the best,
David
LOL!
Well .. it may not have!
It could have possibly been something that I
David Luff wrote:
On 3/31/03 at 10:51 AM [EMAIL PROTECTED] wrote:
Could the ATC manager be implemented as a low-priority thread which is
woken up every so often (few seconds) to update the list of distances to
the ground stations, and additionally if a frequency is changed? The
realtime loop
Interesting
I downloaded the CVS last week .. tues or wed .. and installed it.
The frame rate went to.. very bad. basically made flightgear unflyable..
It also made regular flightgear unflyable .. the screen jumping every 1 or 2
seconds.. and also other 3d programs started doing the same..
Curtis L. Olson writes:
Just as a random stab in the dark I commented out ...
globals-get_ATC_mgr()-update(delta_time_sec);
... from the main loop and my frame rate at least doubled ... ?!?
If we take the ATC manager out of globals and add it to the main
subsystem manager
David Megginson writes:
If we take the ATC manager out of globals and add it to the main
subsystem manager (instead of updating manually), we can set it up to
update, say, every 2 seconds instead of every frame.
My concern is that if the atc manager update is taking me from 60hz
down to 20hz
At 3/29/03, you wrote:
Curtis L. Olson writes:
I returned from being gone for the week, did a cvs update to get all
the latest changes and now I'm seeing about 1/3 the frame rate I'm
accustom to seeing. I now am getting something in the 18-25 range
which is pretty horrible for my hardware.
Curtis L. Olson wrote:
David Megginson writes:
If we take the ATC manager out of globals and add it to the main
subsystem manager (instead of updating manually), we can set it up to
update, say, every 2 seconds instead of every frame.
My concern is that if the atc manager update is
David Megginson wrote:
Curtis L. Olson writes:
Just as a random stab in the dark I commented out ...
globals-get_ATC_mgr()-update(delta_time_sec);
... from the main loop and my frame rate at least doubled ... ?!?
If we take the ATC manager out of globals and add it to
William McRaven wrote:
Interesting
I downloaded the CVS last week .. tues or wed .. and installed it.
The frame rate went to.. very bad. basically made flightgear unflyable..
It also made regular flightgear unflyable .. the screen jumping every 1 or 2
seconds.. and also other 3d
David Luff writes:
OK, that's it!!! - ATC did *not* break TuxRacer ;-)
Are you sure?
All the best,
David
--
David Megginson, [EMAIL PROTECTED], http://www.megginson.com/
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
I returned from being gone for the week, did a cvs update to get all
the latest changes and now I'm seeing about 1/3 the frame rate I'm
accustom to seeing. I now am getting something in the 18-25 range
which is pretty horrible for my hardware.
I've done a complete reboot to rule out my machine
Curtis L. Olson writes:
I returned from being gone for the week, did a cvs update to get all
the latest changes and now I'm seeing about 1/3 the frame rate I'm
accustom to seeing. I now am getting something in the 18-25 range
which is pretty horrible for my hardware.
I've done a complete
PM
To: [EMAIL PROTECTED]
Subject: [Flightgear-devel] major frame rate drop?
I returned from being gone for the week, did a cvs update to get all
the latest changes and now I'm seeing about 1/3 the frame rate I'm
accustom to seeing. I now am getting something in the 18-25 range
which is pretty
26 matches
Mail list logo
