Announcement

Collapse
No announcement yet.

Speeding up 5.21

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

  • #31
    I can see that VSync is disabled, because of the typical tearing. But my scores are still the same. And things like this should simply be incorporated in the drivers.

    Comment


    • #32
      I uninstalled my 5.15 drivers with the uninstaller Ant posted. Then I installed 5.21 after going back to standard VGA drivers. After installing 5.21 AND running the reg hacks (Disable VSync and Force AGP 2x) I went to go play Revolt (a new Acclaim Radio Control car racing game) at 1024x768x32 with 24Bit textures and full detail. Usually I would get no lower than 32FPS playing with the 5.15 drivers. Now with the 5.21 it barely ever gets over 20FPS, usually 12-14FPS. I checked my registry and only 0000 is listed. I went to play Tribes at 1024x768 software mode with full detail and it felt slower. I didn't use Q3Test. I uninstalled 5.21 and put back 5.15 with the reghacks and all is back to normal. Not sure what is wrong. I know I didn't use the regular games to test the speed of the drivers but I still felt a hit.

      My system specs are:
      Abit BX6-2 with KH BIOS and 128 AGP Aperature
      128MB CAS2 RAM
      Celeron 300A @ 450
      Diamond MX300 with newest Aureal Ref Drivers
      Asus 40X CD ROM
      IBM 14GXP 10GB HD
      G400 32MB SH OEM not OCed yet
      Sony 420GS 19" Monitor

      -The-Rev-

      Comment


      • #33
        Ok, here's why I'm confused...

        Ant, Kruzin, Rags - any input appreciated.

        Step 1: Install Win98
        Step 2: Install 5.21
        Step 3: Apply Registry Hack (this meant adding the DirectX key under 0000/settings)
        Step 4: Reboot
        Step 5: Run OpenGL
        Step 6: Shit for performance

        Is there some special reason why the VSYNC disable hack isn't working for me?

        And... even with VSYNC _on_, 13fps is pretty unacceptable on a P3-550/256/25GB/G400DH

        - Gurm

        ------------------
        G. U. R. M. It's not hard to spell, is it? Then don't screw it up!
        The word "Gurm" is in no way Copyright 1999 Jorden van der Elst.
        The Internet - where men are men, women are men, and teenage girls are FBI agents!

        I'm the least you could do
        If only life were as easy as you
        I'm the least you could do, oh yeah
        If only life were as easy as you
        I would still get screwed

        Comment


        • #34
          V-sync is disabled and I can´t see a difference from the older drivers. Oh, wait a minute, now Q3 at 1024x768x32 all on now lays at 10 fps.

          SO where is the crusher/massive improvements that were promised? SO where is the Half-Life Opengl fix?

          Comment


          • #35
            first ant and kruzin thanks for the good work and effort put into finding the v-sync problem for people not already using the g400tweak and fresh installs.it managed to get a lot of people back to the starting point on the 5.13.but were are the dramatic inprovements(5 fps) no-one seems to be getting a improventment and those few that do may have had their card setup wrong and with all the info now are getting what they should have been getting all along.really someone post some good results.and thanks from the less appreciative on finding the v-sync problem

            Comment


            • #36
              Kruzin, yes, there are no other 000x there, only 0000. In fact before I applied that fix there was no DirectX subree in the 0000 subtree at all!

              As you can see many of us are disabling the VSync yet aren't getting the same results as we used to with previously working drivers... so what now, we all start switching drivers depending on what game we want to run? Heh heh...


              Anyway, I also played with refresh rates... didn't change the situation either... 85Hz or 120Hz - the results was more or lesss the same (that's at VSync on). At 120Hz it was a bit slower (10.5 fps vs 12.6fps for 85Hz). With VSync off it's 13.8. Yes I can see that VSync is disabled because of tearing... I never used to see tearing before - I guess at 25fps you don't generally see it. But at 13 you ALWAYS do.

              Haig, just one thing, can you make sure developers look into:

              timedemo 1
              demo q3demo1.dm3

              on their machines? The open scene with alot of jumping is rediculously slow (something like 2-5fps) and when averaged with the rest which moved o.k. you get that 12-13fps...

              Also make them check System Shock 2. Doors are all screwed up in the Basic/Advanced Training lobby. That's not a performance issue, just them breaking a previously working OGL code. They should be able to figure by looking at what it uses and what they changed.

              Michael

              P.S. btw, I tried both 64MB and 128MB aperture AGP setting in the BIOS. I have it at AGPx2 (tried both default and forced)

              ------------------
              P2c-300a/450, 192MB PC125 SDRAM, Quantum Fireball Plus KA 18.2GB 7200rpm, Panasonic 7502B x4/x8 Ultra SCSI CD-R, Tekram DC-390U2W Ultra2Wide SCSI controller, Diamond MX300 (Vortex2), Creative Labs AWE64 Gold Sound Blaster, A-Trend Voodoo II 12MB, Matrox Millennium G400Max, 19" Hitachi SuperScan 752 and some other fancy stuff
              P2c-300a/450, 256MB PC125 SDRAM, Quantum Fireball Plus KA 18.2GB 7200rpm, Panasonic 7502B x4/x8 Ultra SCSI CD-R, Tekram DC-390U2W Ultra2Wide SCSI controller, Diamond MX300 (Vortex2), Matrox Millennium G400Max, 19" Hitachi SuperScan 752, Logitech Cordless MouseMan Wheel and some other fancy stuff

              Comment


              • #37
                I haven't even benchmarked it anymore... I disabled VSync in all posible ways (reg hack, quake 2x) and I still get shit performance in Q2. So, I'm pretty confident it's NOT a VSync problem. (btw: I want VSync to be ON, it always has been and I hate tearing)

                Comment


                • #38
                  I have Vsync disabled in the registry under the right key (0000), sync every frame to no in the q2 menu, and gl_swapinterval set to 0 but still no improvement in OpenGl q2. Same performance as 5.13, so what is going on? Q3test 1.06 same situation, except that demo1 peformance has gone down while demo2 performance has increased slightly with r_swapinterval at 0 and vsync disabled in the menu. So where is the promised perfomance increase? I guess it would sting less if these drivers hadn't been hyped for over two months now, but this is really disappointing. I can put up with quarterly driver releases if something significant changes with each release. Two months for a small increase in D3D performance and no change in OpenGl, along with some bug fixes (which I haven't seen) just doesn't cut it.

                  Comment


                  • #39
                    Oh and system specs:

                    Dell PII - 400, 128mb RAM, OEM G400 32m SH, 5.21 drivers, Win 98.

                    Comment


                    • #40
                      Hehe - I don't smoke crack Kruzin - I just made the ever fateful mistake of believing what ROM said... I should know by now..

                      Anyway - there IS a possibility that the ICD was not the intended one - hence the VSYNC cockup that we are all left with. Andrea posted me a Matrox utility that disables Vsync for OpenGL - I don't know if it fixes this and it may be what some of you (Ant, Kruzin) have been eluding to. I'll try it and see what it does in the registry/

                      I've pulled my post - it was posted in the midst of a barrage of complaints and with Rom bleeting that he'd told everybody that it was the wrong ICD but nobody listened..

                      As they say...

                      4714389 times bitten.. still too stupid to be shy!





                      ------------------
                      Phil
                      Phil

                      Comment


                      • #41
                        Oh Mr. Administrator, Ant,

                        Tried your suggestion and life is better, got 8 FPS back of the 10 I lost. Thanks very much.

                        Probably would have got more, but I only got a little junior card, 16MB, unlike most everyone else with 32MB and MAX's and such.

                        Another interesting issue I had, OGL crashes with ECC memory enabled in BIOS, was solved with the latest driver release. Imagine that...
                        ---------------------------------------------
                        P III 500, ASUS P2B-LS w/256MB ECC RAM, ECC enabled, 16MB G400 w/5.21 drivers, Win98 SE, hard drives, cables, CD ROM drives, burners, DVD and fans all in a new hi rise, befitting soon to be outdated cutting edge technology, connected to dear wifes Micron XKE w/that way cool docking station with SCSI and LAN built in.

                        MSI K7D Master L, Water Cooled, All SCSI
                        Modded XP2000's @ 1800 (12.5 x 144 FSB)
                        512MB regular Crucial PC2100
                        Matrox P
                        X15 36-LP Cheetahs In RAID 0
                        LianLiPC70

                        Comment


                        • #42
                          Himself,

                          If memory serves me correctly,

                          "Warp Clock"

                          is distortion in brainwaves and mental bias, usually in a parallel dimension, experienced by a person with a fragmented thought process forced to speak in an absolute for the first time in their life.

                          MSI K7D Master L, Water Cooled, All SCSI
                          Modded XP2000's @ 1800 (12.5 x 144 FSB)
                          512MB regular Crucial PC2100
                          Matrox P
                          X15 36-LP Cheetahs In RAID 0
                          LianLiPC70

                          Comment


                          • #43
                            Or maybe it's the egg timer for when the startrek crew cook up their dinner while having a day out sitting on the warp engines.

                            That really didn't work, did it? I don't care. I'm bored. I wanna go ome.

                            ------------------
                            Cheers,
                            Steve

                            Comment


                            • #44
                              Ok... I'm using the 3.21 drivers and I don't know what I'm doing right. But I'm getting 43fps in Demo1 on Q3test at:

                              1024x768
                              32bit color
                              16bit textures
                              all other settings turned all the way up

                              I get 32fps at 1280x1024 with the same settings.

                              True, this isn't as fast as some benchmarks I've seen with TNT2s and V3s. But it's still plenty fast enough for me.

                              This is on a C366 OCed to 567MHz on a G400MAX (225/169). I did install the control panel tweaking app and disabled vsynch.

                              I'm at work right now but I'll investigate further when I get home tonight.

                              Thorn

                              Comment


                              • #45
                                Well, since there seems to be a lack of Q3 numbers so far, guess I'll toss mine in as well.

                                Not sure if these are good or bad exactly but... PII 450, 128 ram, G400 MAX at the default clock speed...

                                Q3 is set to 1024x768, 32bpp, 32bit textures, everything on and I'm getting 29/30 fps consistently in both demo1 and demo2. Vsync appears to be disabled(love that tearing in the slower parts ) although these are the exact same numbers I was getting running the 5.13 drivers.

                                Not sure if this will help any, but figured it couldn't hurt to try add some extra information.
                                You mean, think of something witty to say? I don't think I have the energy for that.

                                Comment

                                Working...
                                X