On Thu, 28 Jul 2005 00:38:38 +0200
Roland Scheidegger <[EMAIL PROTECTED]> wrote:
> Aapo Tahkola wrote:
> >>That's true, but to avoid the huge drops you could also just decrease
> >>texture detail. Or implement the second texture heap in main memory and
> >>use gart texturing (though you'd also n
Aapo Tahkola wrote:
That's true, but to avoid the huge drops you could also just decrease
texture detail. Or implement the second texture heap in main memory and
use gart texturing (though you'd also need to manually increase the gart
size). There are some problems with that for r200, and the s
On Mon, 27 Jun 2005 01:57:56 +0200
Roland Scheidegger <[EMAIL PROTECTED]> wrote:
> Ben Skeggs wrote:
> > S3TC does seem to be the killer for UT2004. I started porting over the
> > S3TC stuff from the r200 driver a while
> > back, but haven't had a lot of time recently to fix a couple of issues
>
Ben Skeggs wrote:
S3TC does seem to be the killer for UT2004. I started porting over the
S3TC stuff from the r200 driver a while
back, but haven't had a lot of time recently to fix a couple of issues
with it. Overall fps doesn't seem to take a
huge gain, but the sudden drops to 1-2fps in certai
Adam K Kirchhoff wrote:
FYI
I've had a chance today to test the r300 driver (using a Radeon
9550) with every 3d game and application I have installed. This
includes UnrealTournament, ut2004, q3a, RTCW, Rune, Tribes2, Orbz,
MarbleBlast (both from GarageGames), neverball, neverputt, NWN,
FYI
I've had a chance today to test the r300 driver (using a Radeon
9550) with every 3d game and application I have installed. This
includes UnrealTournament, ut2004, q3a, RTCW, Rune, Tribes2, Orbz,
MarbleBlast (both from GarageGames), neverball, neverputt, NWN, doom3,
blender, ppracer,
On Saturday 15 January 2005 19:16, D. Hageman wrote:
> On Sat, 15 Jan 2005, Adam Jackson wrote:
> > On Saturday 15 January 2005 13:56, D. Hageman wrote:
> >> GL_MAX_VIEWPORT_DIMS=4096/4096
> >> GL_RENDERER = Mesa X11
> >
> >
> >
> > You're using the wrong libGL.
>
> Inde
I was finally able to coerce it into working. I am not sure what I did
different to make it work. Getting it to work doubled the FPS from
glxgears.
At any rate, the results from glxgears are below:
Using 8 maximum texture units..
GL_MAX_VIEWPORT_DIMS=4096/4096
GL_RENDERER = Mesa DRI R300 200
On Sat, 15 Jan 2005, Adam Jackson wrote:
On Saturday 15 January 2005 13:56, D. Hageman wrote:
I just got done with the second try at this. I pulled the Mesa and
r300_driver cvs trees this morning and recompiled. The only hitch was
that apparently some changes have happened to the radeon and r200
On Saturday 15 January 2005 13:56, D. Hageman wrote:
> I just got done with the second try at this. I pulled the Mesa and
> r300_driver cvs trees this morning and recompiled. The only hitch was
> that apparently some changes have happened to the radeon and r200 driver
> in the Mesa tree that does
I haven't enabled any debugging other then running glxgears with
LIBGL_DEBUG to see if it wasn't finding the r300_dri.so.
[drm] Initialized drm 1.0.0 20040925
ACPI: PCI interrupt :01:00.0[A] -> GSI 16 (level, low) -> IRQ 169
[drm] Initialized radeon 1.12.1 20041216 on minor 0:
agpgart: Found
On Sat, 15 Jan 2005, D. Hageman wrote:
I am running the latest CVS x.org.
It shows that the highly experimental warning and all of that in the logfile.
I keep thinking that I have fumbled the ball somewhere on the compile and
install, but I just can't see it at the moment. I haven't given up yet
I am running the latest CVS x.org.
It shows that the highly experimental warning and all of that in the
logfile.
I keep thinking that I have fumbled the ball somewhere on the compile and
install, but I just can't see it at the moment. I haven't given up yet
though. ;-)
On Sat, 15 Jan 2005, Pe
Did you get latest CVS x.org source with support for r300 ? Or did you
patch it with ati.patch from r300_driver ?
D. Hageman wrote:
<
I just got done with the second try at this. I pulled the Mesa and
r300_driver cvs trees this morning and recompiled. The only hitch was
that apparently some c
On Fri, 14 Jan 2005, Vladimir Dergachev wrote:
On Fri, 14 Jan 2005, D. Hageman wrote:
I took the time to compile the r300 driver and give it a whirl.
The machine is a Dell Laptop (Inspiron 9100) with a ATI Radeon Mobility
9600 M10. It has a device ID of 0x4e50.
glxgears runs with a 370-380 FPS.
On Fri, 14 Jan 2005, D. Hageman wrote:
I took the time to compile the r300 driver and give it a whirl.
The machine is a Dell Laptop (Inspiron 9100) with a ATI Radeon Mobility 9600
M10. It has a device ID of 0x4e50.
glxgears runs with a 370-380 FPS.
Hmm.. There are two possibilities:
1. I have
I took the time to compile the r300 driver and give it a whirl.
The machine is a Dell Laptop (Inspiron 9100) with a ATI Radeon Mobility
9600 M10. It has a device ID of 0x4e50.
glxgears runs with a 370-380 FPS.
r300_demo --triangles and --tex-triangles does not give me the same view
as the scree
If you are one of the developers working on the r300 code and you feel the
need to have tests run on a FireGL T2, contact me.
I installed xorg cvs with all the patches some days ago, the card is
recognized and DRI is active (at least the logs claim so). The Xorg setup
is running very stable even
18 matches
Mail list logo
