ClassicHasClass wrote:20fps on a POWER5?? Something's really wrong. My Quad G5 in software mode runs Quake at a ripping pace, so CPU rendering should not be the limiting factor. What does xdpyinfo say? Is the MIT-SHM extension installed? Is this xquake or quake.sw?
So, I get fluid gameplay, but only at 320x200 (that's the standard resolution), anything up from there slows down REALLY fast. At 640x400 it's a slideshow. I can see the frames redrawing from top down.
Resizing is interesting, though. Resizing is content-aware. The health bar on the bottom remains the same size (it's probably a bitmap) whilst the rest of the render area increases.
Answering your questions:
- According to X Display Info, I have MIT-SHM installed and more other 16 extensions: BIG-REQUESTS, DAMAGE, LBX, RECORD, SCREEN-SAVER, SECURITY, SHAPE, XC-APPGROUP, XC-MISC, XFILES, XInputExtension, XTEST, XTestExtension1, aixCursorExtension, xColormapExtension, xDirectAccessExtension.
- I'm running quake.sw.wimp. Quake.sw exits with the error we discussed previously: UMSobj.dll could not be loaded.