Announcement

Collapse
No announcement yet.

D3D Problems in HalfLife

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

  • D3D Problems in HalfLife

    I have problems running HalfLife in Direct3D mode.. When I hit Join on a server and it brings up the console window and starts loading, 50% of the time the graphics gets completely messed up.. So I am forced to play in the slower OGL mode, which I also have a problem with.. Textures far away sometimes appear as solid pink or green or something.. But I would like a solution for the D3D problem.. My system is an AMD K6-2/3D 300MHz with ALi chipset motherboard and 128 Mb of PC100 and G400 MAX DH..

    - Avron -

  • #2
    You will find this thread in the Matrox Games Forum...
    Core2 Duo E7500 2.93, Asus P5Q Pro Turbo, 4gig 1066 DDR2, 1gig Asus ENGTS250, SB X-Fi Gamer ,WD Caviar Black 1tb, Plextor PX-880SA, Dual Samsung 2494s

    Comment


    • #3
      First off, what G400 drivers are you using? If not the latest (5.41), download those.

      Next, when properly configured OGL mode IS faster than D3D. HL is an OGL game. It's D3D support is just an OGL-D3D wrapper (not "real" D3D support).

      Add the lines
      gl_texsort "1"
      gl_polyoffset "2"
      To your autoexec.cfg (and the autoexec.cfg of all mods)

      Also, in your Powerdesk advanced options, turn on 32bit z-buffer

      With the latest drivers, and some tweaking, you should do fine in OGL mode.
      Core2 Duo E7500 2.93, Asus P5Q Pro Turbo, 4gig 1066 DDR2, 1gig Asus ENGTS250, SB X-Fi Gamer ,WD Caviar Black 1tb, Plextor PX-880SA, Dual Samsung 2494s

      Comment


      • #4
        Hmmm...tried your tips...no more white dots in corners and no more decals shining trough walls...i think the 16 bit z-buffer was my problem...but bullet-holes, blood and so on disapear from some angles...looks like half-life with very old TNT-Drivers on a TNT...any solution? Is there a place where someone collects stuff regarding half-life and matrox in general?
        thx
        Woeba

        Comment


        • #5
          gl_polyoffset is what controls the decals (blood, blast marks, bullet holes, etc). Play with that setting...move it up and down in incriments of .1.
          Eventually you'll find a setting that works best for you.
          You can even adjust this in the game, from the console, to make it easier. Once you find what looks best, put that number in the autoexec.
          You can also use negative numbers (in d3d mode on my g200, i used to have to run it at -0.1)
          Core2 Duo E7500 2.93, Asus P5Q Pro Turbo, 4gig 1066 DDR2, 1gig Asus ENGTS250, SB X-Fi Gamer ,WD Caviar Black 1tb, Plextor PX-880SA, Dual Samsung 2494s

          Comment


          • #6
            oh, and if you use the search function (upper right of this page), you can find lots of halflife threads with all sorts of info, including my full video configs in many places....(and many disussions about D3D vs. OGL in this game)
            Core2 Duo E7500 2.93, Asus P5Q Pro Turbo, 4gig 1066 DDR2, 1gig Asus ENGTS250, SB X-Fi Gamer ,WD Caviar Black 1tb, Plextor PX-880SA, Dual Samsung 2494s

            Comment


            • #7
              thx 4 the tipps!
              decals are ok now...how about the little probs when looking a a wall nearby a light source? Seems like the driver can display in this case only several stages of light-intensity...do you have the same prob?

              cu
              Woeba

              Comment

              Working...
              X