Re: [Dri-users] Re: Savage4 - I think it is on its way!!!

[Paulo R. D. <pr...@uo...>]

Em Qui 26 Fev 2004 20:08, Felix K=FChling escreveu:
> On Thu, 26 Feb 2004 19:36:16 -0300
>
> Paulo wrote:
> > Felix wrote:
> > > Paulo wrote:
> > > > Felix wrote:

<snip>

> > Before, glxgears used to give me 100 frames in 5 seconds -> 38 FPS; Now
> > it is giving me 500 frames in 5 seconds -> 100 FPS.
> >
> > Obviously MUCH better! In any case, I've heard of better performances
> > (300 to 500 FPS). So, is that what I should expect (the 100 FPS), or can
> > it be improved? (here it is a PIII 500 Katmai - 32Mb Agp Savage4 - 256 =
Mb
> > pc100 ram)
> >
> > Well, in any case, glxinfo tells me "Direct Rendering: YES".
>
> That's great. The driver performance is still bad. In glxgears all it
> has to do is push geometry to the hardware as fast as possible. This is
> where your relatively slow CPU is probably the bottle neck. You can try
> playing with compiler optimization options in host.def.
>
> The driver performance will increase in the future and you're going to
> see much higher numbers here. But the real strenght of hardware
> acceleration is with complex textures and lighting like in real games.

Hi Felix! Hi Alex!

=46riday morning got the updated dri driver from the cvs tree and recompile=
d it=20
with sse optimization. It really improved the stats at glxgears!

Before I had 100 FPS on average on glxgears; now I Have 210 -220! :

paulo@LS:~$ glxgears
1064 frames in 5.0 seconds =3D 212.800 FPS
1100 frames in 5.0 seconds =3D 220.000 FPS
1100 frames in 5.0 seconds =3D 220.000 FPS
1100 frames in 5.0 seconds =3D 220.000 FPS
1109 frames in 5.0 seconds =3D 221.800 FPS

The fog problems was solved indeed.

Also made some new tests with some 3D accelerated games:

In TUXRACER almost everything goes smooth if I don't use the shadow options=
=2E=20
If I use, it gets much slower and crashes at a certain point (some objects,=
=20
like the speed drawings, disappear; later, if I give "esc", the menu also=20
disappear, but the game continues to work). Apart from that, just noticed t=
he=20
names of the race circuits are not ok (can't read them...). Also noticed th=
at=20
if I play windowned and move the window, the image get "cut")

CUBE (3d game) will crash without giving me image (but the program goes on=
=20
because I have sound on the backgrount. Actually is a reasonable crash,=20
because I have to restart X. However, this can be due to the installation.=
=20
Gonna give you a try=20

ULTIMA1 is running slow, but seem to run ok (apart from the mouse, which is=
=20
always "late", but I think that is due to the image speed, which is still=20
slow for that game).

By the way, I could also run QUAKE2; It is still very (REALLY) slow (not=20
playable), but at least opened and worked in OpenGL mode (and also in=20
SDL_OpenGL modes). As strange as this may seem, it did not work with X11 -=
=20
got a segmentation fault!

On the other hand, if was possible to run ENEMY TERRITORY - WOLF3D!!! Took=
=20
some time for ideal settings (fastest), but coud made it through, even play=
=20
on-line. It froze in certain games (and actually some big crashes, no crtl
+alt+del, no ctr+alt+F1...F6...F12, no killall), but I think I managed to=20
solve it disabling openGL extentions (Does it make sense?)
Also noticed the brightness control does not seem to work.
Just to be sure, at this stage, we only have software acceleration with the=
=20
dri drivers, correct (the game did not detect hardware acceleration; had to=
=20
manually allow software acceleration)?

I intead to get blender, to make some tests on it too.

<snip>

> > The idea would be to include this extra details into the Building
> > instructions, and alleviate the people who is developing, in order to l=
et
> > them focus in what really still has to be developped/improved.
>
> Ok. Sounds good. The whole DRI website (almost) is a Wiki, which means
> anybody can edit it and add information. All the pages have a link in
> the bottom that says "EditText of this page". Feel free to add some
> savage-specific details in the build instructions or wherever you see
> fit.

Ok, will work on it!

Best regards,

Paulo