On Wed, 2002-03-13 at 18:03, Michael Thaler wrote: > On Wed, Mar 13, 2002 at 04:33:10PM +0000, Jose Fonseca wrote: > > > I would also like to point out that at this moment the > > mach64-0-0-3-branch, from where this snapshot was taken, is perfectly > > usable with almost the same level of functionality given by the previous > > mach64-0-0-2-branch except some remaining glitches. > > Thank you Jose. I installed the mach64-0-0-3 branch from CVS and > compilied it. Everything went fine. I installed it and tested it with > glxgears and Unreal Tournement. > > glxgears showed around 280 Frames per second which is much faster then > with the mach64-0-0-2 branch. (I think I got around 180 or less, I do > not exactly remember). > > ut gave me about the same framerate then the mach64-0-0-2 branch, I > think, but the textures look antialiased now. I still ran your > UnrealTournement.ini with a resoltion of 640x480 but I will experiment > and turn some stuff on and see how fast it is then. >
hmm.. not sure if there was anything that caused that texture antialiasing... > A bug I saw is the following. When I run glxgears and destroy the > window, the window vanished, but the graphics inside the > glxgears-window is painted on the windows behind. Moving the windows > does not make the graphic disappear, but selecting text with the mouse > does. > This also happens with me in some applications (glxgears quite often), and since mach64-0-0-2-branch. It seems that X doesn't get notified that that area is dirty, or the application draws another frame before quitting when it shouldn't. > I will do some more testing with ut, turning stuff on and report what > I will find. > > Thank you and the others that worked on the mach64 for your excellent > work! > Michael Jose Fonseca _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
