Manuel Teira wrote: > Have you got errores related to the glide library? > Perhaps you should comment out the line: > #define HasGlide3 YES > in the host.def file. > Or perhaps would be good to comment it out in our mach64 branch.
oops. That's likely the problem. I got so used to configure-like scripts to determine what I have installed that I just skipped the Glide stuff in host.def. This might actually help, yes. :-) > What I made for the tests was using: > export LD_PRELOAD=/usr/X11R6-DRI/lib/libGL.so ok, sure that'll work. > > That is probably due to my card not being an AGP variant (also my > > mainboard does have a - currently empty - AGP slot). > > I don't know. We are not using any AGP feature just now. What processor does > your computer have? I'm getting about 215-220 fps in hw mode and no more than > 100 (not exactly) in software mode. ah, this is gears fps now, not gltron, right? ok gears does 160 software now on my Duron 800, while on Mach64-accel it does 260. gltron does 5-15 on mach64, 5-15 on plain mesa, too; although it subjectively seems to be a bit jerkier. Anyway, with the old Utah code I got more (at least 20fps, but on a K6-2 333) but that has time. I'm more concerned about glxgears: in software mode, it shows the three gears moving; in hardware mode, it just shows a huge close-up of the red one moving. Strange, since gltron looks almost equivalent under both modes, with hardware having a bit better texture filtering IMHO. BTW, why does mach64 module insertion fail when agpgart isn't installed if it doesn't use any features from AGP? HTH, Yours Malte #8-) PS: no need to Cc me, I'm on this list. _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
