Birger Brunswiek wrote:
Using FlightGear's 0.9.5 http jpg server I, sometimes, get incompletely
rendered images. The scenery around is missing some of the triangles
and they appear as grey, blueish spots
This resembles me of rendering errors with not-that-uptodate
XFree86/DRI drivers for ATI
Ampere K. Hardraade wrote:
On October 13, 2004 09:44, Frederic Bouvier wrote:
You can't ask too much from an Intel Graphic processor. IIRC, it doesn't
use dedicated memory for textures and buffers, but rather your main memory.
My notebook, that features an ATI IGP, has a bios parameter to
Ampere K. Hardraade wrote:
I know. I am proposing that it may be a good idea to cut it down further so
that the archive is around 40MB.
I've just did some googling today, and I found that I am not the only one who
see the size of the archive as a problem.
I've been thinking about it and am
Martin Spott wrote:
Birger Brunswiek wrote:
Using FlightGear's 0.9.5 http jpg server I, sometimes, get incompletely
rendered images. The scenery around is missing some of the triangles
and they appear as grey, blueish spots
This resembles me of rendering errors with not-that-uptodate
XFree86/DRI
Erik Hofman wrote:
Martin Spott wrote:
This resembles me of rendering errors with not-that-uptodate
XFree86/DRI drivers for ATI Radon. I remember that they got replicated
in screenshots, probably in these JPEG images as well,
Probably, they all use the same function now.
Aaah, I found
Martin Spott wrote:
Erik Hofman wrote:
Update of /var/cvs/FlightGear-0.9/data/Aircraft/737/Models
In directory baron:/tmp/cvs-serv23677/Aircraft/737/Models
Modified Files:
B737-300.ac
Log Message:
This one includes the smooth shaded 737 and tu154B as well as the adf
instrument using the
Gerhard Wesp wrote:
The parameters you need appear to be all there. Of course, nothing is
documented so you're on your own...
Documentation is also accepted for inclusion in CVS ...
Erik
___
Flightgear-devel mailing list
[EMAIL PROTECTED]
Hi all!
I've added some digital low-pass filters to the autopilot code. You can now
define four different types of digital filters inside the autopilot
configuration file. The outputs from these filters could then be used as
inputs to PID controllers.
I've sent a readme file to Erik that
Mathias Fröhlich wrote a long time ago:
Sent: 08 July 2004 10:38
To: FlightGear developers discussions
Subject: Re: [Flightgear-devel] status of aircraft carrier
On Mittwoch, 7. Juli 2004 21:32, Vivian Meazza wrote:
It would be a shame if we can't model individual wires, then we could
* Curtis L. Olson -- Wednesday 13 October 2004 23:47:
I haven't looked closely at the display list stuff. Are we being
careful to free the display lists when we free the associated objects
and remove them from the scene graph? Is this something that plib
should automatically handle (but
Melchior FRANZ wrote:
* Curtis L. Olson -- Wednesday 13 October 2004 23:47:
I haven't looked closely at the display list stuff. Are we being
careful to free the display lists when we free the associated objects
and remove them from the scene graph? Is this something that plib
should
Martin Spott wrote:
Erik Hofman wrote:
Martin Spott wrote:
This resembles me of rendering errors with not-that-uptodate
XFree86/DRI drivers for ATI Radon. I remember that they got replicated
in screenshots, probably in these JPEG images as well,
$ lspci|grep VGA
01:00.0 VGA compatible
Hello,
apparently people are downloading from the CD-Images/ directory like
mad (about 200 FlightGear-Win32-0.9.5.img these days). Wouldn't it make
sense to remove this outdated beast from the servers ?
Martin.
--
Unix _IS_ user friendly - it's just selective about who its friends are !
The Max is 8Mb. The other settings will make you cry.
Is there anyway I can boost the memory allocaated for the frame buffer?
Ampere
On October 14, 2004 02:59, Frederic Bouvier wrote:
Look in your *BIOS* settings. It isn't the AGP Aperture, it is the amount
of main memory dedicated to
14 matches
Mail list logo
