[Solved] Problems with Quake 3

[Sodki]

Now that we have a brand new Quake 3 ebuild in portage marked ~ppc, I've decided to take a chance and emerge it. After copying the necessary files from the CD, I've fired up the beast. I had a few problems, so here they are, to see if other people have them too. The first thing I've noticed was that the introductory movie had some glitches, black squares appearing and disappearing. In the menu, the mouse pointer doesn't work and there are some items I can't see. For example, in Setup -> Controls, the mouse speed bar is missing and the joystick threshold bar is on the upper left corner. I also can't play a single player game, because the screen gets stuck on the map initialization screen, although I hear myself getting shot down. So... am I the only one having these problems?

Edit: My problem seems to be be solved by upgrading quake3 to version 1.33_alpha255. Now everything works.

[Fugee47]

when i start quake3 i get following error on my ibook:


...loading libGL.so.1: Calling SDL_Init(SDL_INIT_VIDEO)...
SDL_Init(SDL_INIT_VIDEO) passed.
Initializing OpenGL display
...setting mode 6: 1024 768
SDL_SetVideoMode failed: Couldn't find matching GLX visual
SDL_SetVideoMode failed: Couldn't find matching GLX visual
Using 4/4/4 Color bits, 16 depth, 0 stencil display.
GL_RENDERER: Mesa GLX Indirect


***********************************************************
You are using software Mesa (no hardware acceleration)!
Driver DLL used: libGL.so.1
If this is intentional, add
"+set r_allowSoftwareGL 1"
to the command line when starting the game.
***********************************************************
...WARNING: could not set the given mode (6)
Calling SDL_Init(SDL_INIT_VIDEO)...
SDL_Init(SDL_INIT_VIDEO) passed.
Initializing OpenGL display
...setting mode 3: 640 480
SDL_SetVideoMode failed: Couldn't find matching GLX visual
SDL_SetVideoMode failed: Couldn't find matching GLX visual
Using 4/4/4 Color bits, 16 depth, 0 stencil display.
Received signal 11, exiting...
----- CL_Shutdown -----
RE_Shutdown( 1 )


now the parts of my xorg.conf:

Section "Device"
.........
Identifier "Card0"
Driver "radeon"
VendorName "ATI Technologies Inc"
BoardName "Radeon 9200 Mobility"
BusID "PCI:0:16:0"
Option "UseFBDev"
Option "AGPMode" "4"
EndSection


Section "Screen"
Identifier "Screen0"
Device "Card0"
Monitor "Monitor0"

SubSection "Display"
Viewport 0 0
Depth 24
EndSubSection
EndSection



DRI is disabled !!

maybe someone can help me ???

[HighOnBonsai]

[Murel]

Sodki, I'm having the exact same problem as you, except I didn't notice black boxes during the intro. But everything else, yeah, exactly the same. I'm using the ~amd64 build. I'm not really sure what to do about it. If anyone has any ideas that would be pretty cool.

edit: Ha, and then I emerged quake3-bin (the binaries from idsoftware, not compiling it myself) and am getting the error that Fugee47 is getting, where it says that my 3d acceleration is off and I'm using the mesa stuff. I'm using a Radeon 9600 and I know the computer can see it (fglrxinfo and lsmod both report it, and tuxracer runs with no problems). I just don't know.

[Sodki]

[Murel]

Yeah, all the graphics are normal and the mouse works.

There's some issue with the bots though. I just played the tutorial level. If you play on baby difficulty, the bot never shoots you, but you can't kill him either no matter how many times you follow behind him and shoot him in the back with a shotgun. On any other difficulty, the bot will shoot you and the shots seem almost instantly fatal, like a few shots from the starting machine gun will kill you.

In other words, still buggy. Graphics look good though

[Sodki]