Announcement

Collapse
No announcement yet.

Benchmark f00ked?

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

    Benchmark f00ked?

    Ok I just got the latest ATI Catalyst drivers so I could check if they make a difference.

    So I ran the benchmark and for some reason I have control. I.e. I can move around freely. When it comes to the botmatch, its like playing a botmatch. Both last around the correct times before switching to the next demo.

    Now something has obviously gone wrong and its affecting the results.
    While I'm sure the new Catalyst drivers are good I'm definitely sure that they didn't boost my flyby FPS from 172 to 258 @ 1280 x 960
    Thats because I was flying around and shooting the bots. Oh and I got stuck in a dark area.
    Any solutions?
    :bulb:

    #2
    Well if you run a broken benchmark, no wonder it gives you complete strange and unpredictable results.

    Try to run it again w/o errors maybe?

    Comment


      #3
      Originally posted by Gaal Dornik
      Well if you run a broken benchmark, no wonder it gives you complete strange and unpredictable results.

      Try to run it again w/o errors maybe?
      ROFL! Erm... I'll try again.

      Ok basically my benchmark is messed up. I don't know whats wrong with it. But from what I can see, I am in control. I.e. I can move around the map at a very high framerate. I also know that this is why I'm getting unpredictable results.
      My question is:

      How do I return them to the flybys that Epic set? Since thats the most fair benchmark.

      Comment


        #4
        the benchmark in 2004 has never worked for me

        Comment


          #5
          Just tried another benchmark which was botmatch-rankin.bat in the Benchmark folder. Same thing happened again.

          I'm starting to see the solution I don't like. :sour:

          Comment


            #6
            Originally posted by CH405
            Just tried another benchmark which was botmatch-rankin.bat in the Benchmark folder. Same thing happened again.

            I'm starting to see the solution I don't like. :sour:
            Format all hard disks!!!!!!

            Comment


              #7
              More RAM may help =)

              Comment


                #8
                Originally posted by Gaal Dornik
                More RAM may help =)
                I'm gonna slap you in a minute.

                Comment


                  #9
                  I get exactly the same thing.
                  Can't jump in the botmatches either...

                  Comment


                    #10
                    I get the same thing with the 2004 benchmark.

                    I assumed it was like this for everyone.

                    Comment


                      #11
                      Have you tried UMark?

                      Comment

                      Working...
                      X