Curtis L. Olson wrote:
Geoff Reidy writes:
The major problem I have with fgfs is that I seem to hit a race
condition where all graphics and sound stop for extended periods of time
(up to about 30 secs), long enough for autopilot (or me!) to lose
control and the plane will always crash.
During
Curtis L. Olson [EMAIL PROTECTED] said:
Geoff Reidy writes:
The major problem I have with fgfs is that I seem to hit a race
condition where all graphics and sound stop for extended periods of time
(up to about 30 secs), long enough for autopilot (or me!) to lose
control and the plane
Dave,
On a Geforce3 something, something and a GeForce4 Ti4200 I have
observed that FSAA works fine, except when I try to exit FlightGear,
my entire machine locks up. On GeForce2, you can't FSAA at
resolutions over 800x600 I believe ... and I'll take 1600x1200
over 800x600 FSAA any day ...
The
Curtis L. Olson
Geoff Reidy writes:
The major problem I have with fgfs is that I seem to hit a race
condition where all graphics and sound stop for extended periods of time
(up to about 30 secs),
This most likely relates to freeing tile memory (i.e. moving old tiles
out of the cache
Norman Vine writes:
The same thing happens for me with both Cygwin gcc 2.95.2
and MingW gcc 3.2 both using Doug Lea's malloc routines which
I believe is what most Linux distributions use
CVS version of Cygwin
Implemeting the thread support seems to make this even worse
but this is a
Curtis L. Olson writes:
Norman Vine writes:
The same thing happens for me with both Cygwin gcc 2.95.2
and MingW gcc 3.2 both using Doug Lea's malloc routines which
I believe is what most Linux distributions use
It might be worth verifying that my partial tile free-er routine is
David Findlay wrote:
How do you enable FSAA on Linux with FGFS? Thanks,
David
For NVidia cards you set the environment variable __GL_FSAA_ e.g.
export __GL_FSAA_=4
fgfs
will give 2x2 on a Geforce 2. All the options are listed at
http://download.nvidia.com/XFree86_40/1.0-2960/README.txt
Geoff wrote:
I was getting lockups in some games and fgfs before making my memory
timings a bit more conservative, though it had passed memtest86
previously. Haven't had a lockup for weeks now.
Interesting. You are speaking about the timings of the main memory,
correct? Did the problems you had
Wolfram Kuss wrote:
Geoff wrote:
I was getting lockups in some games and fgfs before making my memory
timings a bit more conservative, though it had passed memtest86
previously. Haven't had a lockup for weeks now.
Interesting. You are speaking about the timings of the main memory,
Dave Perry wrote:
My system is an Athlon XP 1800+ with an Asus A7M266 mother board, 512MB
of PC2100 memory and 3 Seagate Baracuda IV (80GB each). My GF3 is an
Asus V8200 Deluxe. My Linux is a RH7.3 with recent up2date, but I am
running a 2.4.19 kernel compiled from tarball. This kernel
10 matches
Mail list logo
