Announcement

Collapse
No announcement yet.

RtCW won't recognize my G400

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • RtCW won't recognize my G400

    I just received my shiny-new copy of Return to Castle Wolfenstein. Alas, it won't recognize/use the hardware acceleration of my Matrox G400 graphics card under (Redhat v7.2) Linux.

    My system is dual-boot but I spend 95% of my time in Linux and want the game to work there. The Win32 version of RtCW does work (albeit a little slowly) on Win2K/SP2. Running the RtCW/Linux (binaries from downloaded wolfmp-linux-1.0.b2.x86.run) gets me the output shown below.

    I am using the latest Matrox drivers in both Win2K and Linux. The game will run in Linux if I opt for software rendering (see the games suggestion in the output below), so this is definately a failure to recognize my G400.

    This is way I am launching the game:

    #!/bin/sh
    WOLFDIR=/usr/local/games/wolfenstein
    export LD_LIBRARY_PATH=$WOLFDIR/main
    cd $WOLFDIR; ./wolf.x86 $*

    Important note: I have no problems whatsoever playing Quake3:Arena on this very same Linux installation. I am attempting to run RtCW in the same video mode that I typically run Q3A in (800x600x32bpp). The Q3A config generates these settings:

    seta r_lastValidRenderer "Mesa DRI G400 20010321 AGP 2x x86/MMX/SSE"
    seta r_glDriver "libGL.so"

    Obviously my G400/XFree86 is functional, otherwise I couldn't play Q3A. So what's the story on RtCW?

    Ok, here's the output I get when running the script shown above:

    ------------------------
    $ ./Wolf +seta r_mode "4"
    Wolf 1.0.b2 linux-i386 Nov 28 2001
    ----- FS_Startup -----
    Current search path:
    /home/steve/.wolf/main
    /usr/local/games/wolfenstein/main/mp_pak2.pk3 (3 files)
    /usr/local/games/wolfenstein/main/mp_pak1.pk3 (308 files)
    /usr/local/games/wolfenstein/main/mp_pak0.pk3 (783 files)
    /usr/local/games/wolfenstein/main/pak0.pk3 (4775 files)
    /usr/local/games/wolfenstein/main
    ./wolf.x86/main

    ----------------------
    5869 files in pk3 files
    execing default.cfg
    couldn't exec language.cfg
    execing wolfconfig_mp.cfg
    couldn't exec autoexec.cfg
    Hunk_Clear: reset the hunk ok
    Joystick is not active.
    Bypassing CD checks
    ----- Client Initialization -----
    ----- Initializing Renderer ----
    -------------------------------
    ----- Client Initialization Complete -----
    ----- R_Init -----
    ...loading libGL.so: Initializing OpenGL display
    ...setting mode 4: 800 600
    Using XFree86-VidModeExtension Version 2.1
    XF86DGA Mouse (Version 2.0) initialized
    XFree86-VidModeExtension Activated at 800x600
    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
    If this is intentional, add
    "+set r_allowSoftwareGL 1"
    to the command line when starting the game.
    ************************************************** *********
    ...WARNING: could not set the given mode (4)
    Initializing OpenGL display
    ...setting mode 3: 640 480
    Using XFree86-VidModeExtension Version 2.1
    XF86DGA Mouse (Version 2.0) initialized
    XFree86-VidModeExtension Activated at 800x600
    Received signal 11, exiting...

  • #2
    Fixed it.

    Remembering that the 2 RtCW test releases worked fine, I reinstalled wolftest2, and ran it. No problem. I then copied the config file it generated from ~/.wolf/demomain to ~/.wolf/main. I then fired up the released game and (ta-da!) it worked.

    Something in the graphics detection code of RtCW/Linux v1.0b2 is broken, but given a working config file the game is capable of running fine in my environment.

    Comment


    • #3
      Very smart!!!

      Comment

      Working...
      X