Announcement

Collapse
No announcement yet.

Why is Halflife sooooo much slower than Q2?

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

  • Why is Halflife sooooo much slower than Q2?

    Q2 runs pretty darn nice on my crummy system, even up to 1024x768x16, but HL/TFC is nearly useless in anything but software mode.

    Running HL in OpenGL or D3D makes the game slow to a crawl whenever there's any "monsters" or other players around.

    The Q3 demo runs ok, and FS2000 isn't bad at 1024x768x16. Everquest (ick, I don't play it, my brother does :-) also runs pretty good.


    Embarrasing system specs:
    Gigabyte GA-586SG bios 1.15
    (If it arrives, a Epox MVP3G5 tommorow :-)

    K6-II 450 @ 83 x 5.5

    64 megs SDRAM (66 MHz probably)
    64 megs EDO 60ns
    (128 megs 133 MHz SDRAM tommorow also)

    Millennium G200 AGP 8 meg SGRAM
    Soundblaster PCI64
    SMC EZ Card PCI 10

    Windoze 98 (not SE)

    IRQ's:

    0 System timer
    1 Standard 101/102-Key or Microsoft Natural Keyboard
    2 Programmable interrupt controller
    3 (free)
    4 Communications Port (COM1)
    5 SMC EZ Card PCI 10 Adapter
    5 IRQ Holder for PCI Steering
    6 Standard Floppy Disk Controller
    7 ECP Printer Port (LPT1)
    8 System CMOS/real time clock
    9 (free)
    10 Creative Labs Sound Blaster PCI64
    10 IRQ Holder for PCI Steering
    11 Matrox Millennium G200 AGP - English
    11 IRQ Holder for PCI Steering
    12 Microsoft PS/2 IntelliMouse with IntelliEye (IntelliPoint)
    13 Numeric data processor
    14 Primary IDE controller (dual fifo)
    14 SiS 5513 Dual PCI IDE Controller
    15 Secondary IDE controller (dual fifo)
    15 SiS 5513 Dual PCI IDE Controller

  • #2
    Duh, also forgot:

    DirectX 7.0a

    PDesk 4.51 with the 5.25 pd*.* stuff to fix the horrible PDesk CPU hog thing.

    Comment


    • #3
      Add this line to your autoexec.cfg or opengl.cfg file:
      gl_texsort "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


      • #4
        Tried it, didn't seem to make any difference. :-(

        And then I took the line back out of the autoexec.cfg, and it seems that it was automaticly set to "1" anyways.

        I guess I'll just wait and see what the new motherboard does for it tommorow.

        Comment


        • #5
          Half Life uses a heavily modified quake engine Valve licensed from Id. I seriously doubt Valve even paid a cent for any quake2 code to go into it. Half Life also uses skeletal models as opposed to quake2's age old .md2 format. The md2's are easier on framerate... trust me. But the skeletal models in half-life look damned realistic as hell... but you take a performance hit this way. Kruzin has a nice .cfg in this forum, use the search engine and try it... it will tweak you up a little.

          I think your pushing your luck at 1024x768 with your sytem specs as it is. Keep in mind that if your using the q2 engine optimized for 3dnow, it makes a world of difference over the normal one (this seems to be true for the AMD k6 series). Half Life has no such option... it won't use 3dnow specifically. It barely uses mmx as it is... not that mmx is worth a crap anyway.

          [This message has been edited by absalom (edited 09 February 2000).]

          Comment


          • #6
            Just some food for though:

            In half-life, 1024x768 at 16-bit (no triple buffering) depth will allocate 3.1 megs of video ram just for the frame buffer. What's left over is used for textures.

            Half Life's CVARs gl_picmip and gl_round_down can control how much texture storage you use. The higher the value, the less memory is used, as well as the blurrier things get. cl_himodels set to a value of 1 is also another performance hit. A standard half-life map *can* and usually does use more texture storage than a standard quake2 map.

            [This message has been edited by absalom (edited 09 February 2000).]

            Comment


            • #7
              Well, this is the full video config I am using. As pointed out gl_picmip and _playermip can be raised to 1,2 or 3 to help out speed. You could also change the texture mode, but I would leave that where it is.

              gl_ztrick "1"
              gl_dither "1"
              gl_polyoffset "2"
              gl_lightholes "1"
              gl_keeptjunctions "1"
              r_drawviewmodel "1"
              gl_keeptjunctions "1"
              r_shadows "0"
              cl_himodels "1"
              gl_texturemode "GL_LINEAR_MIPMAP_LINEAR"
              brightness "2.5"
              gamma "3.0"
              gl_playermip "0"
              gl_picmip "0"
              gl_round_down "0"
              gl_texsort "1"
              gl_overbright "1"
              scr_conspeed "8000.00"
              gl_palette_tex "1"
              r_decals "500"
              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


              • #8
                Hi !
                I would like to try that out.
                Which file do i put it in to please ?

                Comment


                • #9
                  It can go in either halfile\valve\autoexec.cfg or halflife\valve\hw\opengl.cfg...
                  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


                  • #10
                    Thanks

                    [This message has been edited by Gorf (edited 10 February 2000).]

                    Comment

                    Working...
                    X