If this is of any help - starting with the ufo on the ground and sitting there
(no movement, controls untouched) the memory grows at a rate of approx.
50kB-100kB per second. Monitored for about a minute.
.fgfsrc is blank and all rendering options unchecked, except "display
framerate"
This is on
Jon S. Berndt schrieb:
>> Given the earlier reported segfault at gluPickMatrix, I decided to try
> some
>> of the test programs in the tests directory in the FlightGear
> distribution.
>> Needless to say, these tests are a wonderful idea and immediately pointed
>> the finger at OpenGL. I got an imm
> Given the earlier reported segfault at gluPickMatrix, I decided to try
some
> of the test programs in the tests directory in the FlightGear
distribution.
> Needless to say, these tests are a wonderful idea and immediately pointed
> the finger at OpenGL. I got an immediate segfault when running gl
Hi Eric , I tried changing GL_DONT_CARE to GL_FASTEST , but noticed no
change , still got 8 fps.
Tried your patch Jean , and its back to 18 fps at night , much much
better , enhanced lights on now drops the framerate to 3
Now I can get back to modelling , thank you guys !
Oh, and Im off t
On Tue, 20 Jun 2006 18:54:43 -0500, Jon wrote in message
<[EMAIL PROTECTED]>:
> Given the earlier reported segfault at gluPickMatrix, I decided to try
> some of the test programs in the tests directory in the FlightGear
> distribution. Needless to say, these tests are a wonderful idea and
> immed
Hi guys , thank you for the tips /patch .
Im going to try them out now... just got home from work.
Hope it improves things , but at least I know now which file to study .
I prefer flyability over pretty lights any day :)
Mind you , I remember when I first got Tie Fighter , and it had gouraud
shadi
Given the earlier reported segfault at gluPickMatrix, I decided to try some
of the test programs in the tests directory in the FlightGear distribution.
Needless to say, these tests are a wonderful idea and immediately pointed
the finger at OpenGL. I got an immediate segfault when running gl-test.
On Tuesday 20 June 2006 08:19, Vivian Meazza wrote:
> Dave Perry
>
> > I have had lock-ups on longer X-C flights with the pa24-250
> > recently that could be from a memory leak. So I used the
> > system monitor to check on VM growth. The only 2D pannel
> > used in the pa24-250 is the radio stack
Curt wrote
>
> Is any information about other multiplayer entities published in the
> property tree somewhere?
>
> Local AIModel based entities publish information about themselves
> (location, orientation, etc.) under the /ai/models tree.
>
> Is there anything similar setup for multiplayer tra
* Curtis L. Olson -- Tuesday 20 June 2006 23:51:
> Local AIModel based entities publish information about themselves
> (location, orientation, etc.) under the /ai/models tree.
>
> Is there anything similar setup for multiplayer traffice?
Umm ... yes: /ai/models/multiplayer/ ?
m.
___
Is any information about other multiplayer entities published in the
property tree somewhere?
Local AIModel based entities publish information about themselves
(location, orientation, etc.) under the /ai/models tree.
Is there anything similar setup for multiplayer traffice?
Curt.
--
Curtis O
Hi,
The comment for fast_log is IMHO incorrect.
/**
* This function is about 3 times faster than the system log() function
* and has an error of about 0.01%
*/
The relative error can be larger than 7% it is almost nowhere about
0.01% when used in the range [ 0.5 - 1[. Try yourself:
Olaf
#inclu
I have been trying to move hotspots around and it seems that only a limited
surface of the "instrument can be designated ... But I don't know what is the
criterion... I guess I'll have to look into the source ... :o( Weell on the up
side, at least I can read the source ;o)
> Message du 20/06/0
Mathias Frölich wrote:
> On flightgear-devel was yesterday a short discussion about YASims agl value.
> It would be nice if YASim could behave like the other FDM's do and like one
> would naive expect, in the sense that
>
> ground elevation + agl = altitude
>
> Currently YASim uses the models refer
Jon S. Berndt wrote:
>> At this point it would probably be a good idea to test Frederic's MSVC8
>> build on your hardware.
>
> Very good idea. Where can I get that?
Ah, found the link again:
ftp://ftp.ihg.uni-duisburg.de/FlightGear/Win32
--
http://www.ehtw.info (Dutch)Future of Enschede A
> At this point it would probably be a good idea to test Frederic's MSVC8
> build on your hardware.
>
> Erik
Very good idea. Where can I get that?
Jon
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforg
Jon S. Berndt wrote:
> Program received signal SIGILL, Illegal instruction.
> 0x69596fff in gluPickMatrix ()
> (gdb) where
> #0 0x69596fff in gluPickMatrix ()
> #1 0x86c8 in ?? ()
> #2 0x020ab628 in ?? ()
> #3 0x6973815b in nvoglnt!DrvCopyContext ()
> #4 0x020ab628 in ?? ()
> #5
> I've been shown this text from the cygwin mailing list:
>
> --- start ---
> Searching the mailing list archives would show that this question has
> already come up (several times this week, in fact). The fault is
> EXPECTED, and HARMLESS - just continue on debugging from that point.
> Basically,
>
>I'd really like to know how many are using cygwin, and if they are also
having any trouble.
>
>Jon
One happy Cygwin user here.
Latest Cygwin update is probably sometime around Easter, but plib, SG,
FG and data are all CVS.
PC is AMD64/Win2K.
Richard
__
Melchior FRANZ wrote:
> * Josh Babcock -- Tuesday 20 June 2006 03:00:
>> If someone would be so kind as to commit this,
>
> Eew. Frankly, that's a hack to work around another hack. The weird
> digit-wise representation in the property tree is bad. A number is
> a number, and should be in the tree
Running flightgear with some information options only results in
correct operation. I get a list of aircraft, for example, or the
version number of FlightGear. However, running flightgear - even
with a **complete fresh installation of cygwin**, produces the
following error:
Program received si
I've been shown this text from the cygwin mailing list:
--- start ---
Searching the mailing list archives would show that this question has
already come up (several times this week, in fact). The fault is
EXPECTED, and HARMLESS - just continue on debugging from that point.
Basically, inside cygwi
* Josh Babcock -- Tuesday 20 June 2006 03:00:
> If someone would be so kind as to commit this,
Eew. Frankly, that's a hack to work around another hack. The weird
digit-wise representation in the property tree is bad. A number is
a number, and should be in the tree as such. The fact that the
dialog
Running flightgear with some information options only results in correct
operation. I get a list of aircraft, for example, or the version number of
FlightGear. However, running flightgear - even with a **complete fresh
installation of cygwin**, produces the following error:
Program received signal
On Mon, 19 Jun 2006 23:12:05 -0700
syd & sandy <[EMAIL PROTECTED]> wrote:
> I know this was discussed a while back , and if there was a solution I
> think I missed it.
> So I'll stick my neck out and ask
> I used to get better framerates night flying, unless I enabled enhanced
> lights.
> N
On Tuesday 20 June 2006 05:21, flying.toaster wrote:
> Here are the "main panel" file and the definition of the 3D plane that
> carries it
> I dunno though if it will be of some help since they are all linked to the
> same property (the starter) but at different locations
These are probably fine
syd & sandy wrote:
> Hi all,
> I used to get better framerates night flying, unless I enabled enhanced
> lights.
> Now it doesnt matter if enhanced lights are enabled or not , I get the
> low framerates as soon as the airport lights come on. Ive got a 1.1 gig
> AMD Athalon , with a Geforce 4 MX
Hi,
I have always noticed this, have commented on it over the last 18 months or
so since I first started with FG after about 2.5 hours fps dropped to
<1fps and aircraft eventually crashed...
I first noticed this on the PA28-161 as it was my aircraft of choice then
latterly on the A10-2D...
Georg Vollnhals wrote
>
>
> > when I try running flightgear. Very, very frustrating. I hate to do
> this,
> > but I guess I will next try to completely delete all cygwin directories.
> > This is just so strange.
> This was the only solution for me which worked!
> >
> > I'd really like to know ho
Dave Perry
> I have had lock-ups on longer X-C flights with the pa24-250 recently
> that could be from a memory leak. So I used the system monitor to check
> on VM growth. The only 2D pannel used in the pa24-250 is the radio
> stack. So I tried commenting out various components of the radio
30 matches
Mail list logo
