Menu
Hercules Prophet 4500 in the test: The Kyro2 compared to the GeForce

Hercules Prophet 4500 in the test: The Kyro2 compared to the GeForce

Unreal Tournament

Overclocking Unreal Tournament 16Bit
  • 640x480:
    • Prophet @ 175MHz, 7.89
      27.89
    • Prophet @ 185MHz, 7.89
      27.85
  • 800x600:
    • Prophet @ 185MHz, 7.89
      27,80
    • Prophet @ 175MHz, 7.89
      27,60
  • 1024x768:
    • Prophet @ 185MHz, 7.89
      27.61
    • Prophet @ 175MHz , 7.89
      27.05
  • 1280x1024:
    • Prophet @ 175MHz, 7.89
      26.33
    • Prophet @ 185MHz, 7.89
      26.30
  • 1600x1200:
    • Prophet @ 175MHz,7.89
      25.03
    • Prophet @ 185MHz, 7.89
      24.98

Like You can see from the graphics that Unreal Tournament can take advantage of the slightly higher clock rate, but with an average of 0.5 frames per second more, the effort is in no relation to the benefit.

Overclocking Unreal Tournament 32Bit
  • 640x480:
    • Prophet @ 175MHz, 7.89
      28.65
    • Prophet @ 185MHz, 7.89
      28.58
  • 800x600:
    • Prophet @ 175MHz, 7.89
      28.20
    • Prophet @ 185MHz, 7.89
      28.16
  • 1024x768:
    • Prophet @ 175MHz, 7.89
      27.62
    • Prophet @ 185MHz, 7.89
      27.56
  • 1280x1024:
    • Prophet @ 175MHz, 7.89
      26.92
    • Prophet @ 185MHz, 7.89
      26.83
  • 1600x1200:
    • Prophet @ 175MHz, 7.89
      25.98
    • Prophet @ 185MHz, 7.89
      25.89

At a color depth of 32 bits, however, overclocking seems to backfire.

3DMark 2000

Overclocking 3DMark 2000 16Bit
Unit: points
  • 640x480:
    • Prophet @ 185MHz, 7.89
      3.175
    • Prophet @175, 7.103
      3.174
    • Prophet @ 175MHz, 7.89
      3.174
  • 800x600:
    • Prophet @ 175, 7.103
      3.172
    • Prophet @ 185MHz, 7.89
      3.172
    • Prophet @ 175MHz, 7.89
      3.126
  • 1024x768:
    • Prophet @ 175, 7.103
      3.171
    • Prophet @ 185MHz, 7.89
      3.166
    • Prophet @ 175MHz, 7.89
      3.121
  • 1280x1024:
    • Prophet @ 175MHz, 7.89
      3.084
    • Prophet @ 175, 7.103
      3.079
    • Prophet @ 185MHz, 7.89
      3,078
  • 1600x1200:
    • Prophet @ 185MHz, 7.89
      2.753
    • Prophet @ 175MHz, 7.89
      2.735
    • Prophet @ 175, 7.103
      2.731
  • Even Madonion's 3DMark 2000 can only draw very little advantages from the higher clock rate. Since the new Hercules drivers of version 7.103 were already available at the time of the test, they were also used in this comparison. As you can clearly see, sometimes the use of the newer driver brings more than overclocking the cards. At this point you can clearly see that optimizing the drivers can achieve a few percent more performance, perhaps the eighth generation drivers will bring a little morePerformance leap with itself. The 32-bit comparison values ​​are available here. In order not to prolong the matter unnecessarily, here are the comparison values ​​for 3DMark 2001 and Aquanox. For both, everything that has already been mentioned applies:

    Overclocking 3DMark 2000 32Bit
    Unit: points
    • 640x480:
      • Prophet @ 175MHz, 7.89
        3.201
      • Prophet @ 175, 7.103
        3.197
      • Prophet @ 185MHz, 7.89
        3.105
    • 800x600:
      • Prophet @ 175, 7.103
        3.163
      • Prophet @ 185MHz, 7.89
        3.156
      • Prophet @ 175MHz, 7.89
        3.149
    • 1024x768:
      • Prophet @ 175, 7.103
        3.169
      • Prophet @ 185MHz, 7.89
        3.148
      • Prophet @ 175MHz, 7.89
        3.135
    • 1280x1024:
      • Prophet @ 175MHz, 7.89
        3.001
      • Prophet @ 175, 7.103
        2.999
      • Prophet @ 185MHz, 7.89
        2.965
    • 1600x1200:
      • Prophet @ 175, 7.103
        2.511
      • Prophet @ 185MHz, 7.89
        2.511
      • Prophet @ 175MHz, 7.89
        2.501
    Overclocking 3DMark 2001 16Bit
    Unit: points
    • 640x480:
      • Prophet @ 185MHz, 7.89
        1.063
      • Prophet @ 175 , 7.103
        1.057
      • Prophet @ 175MHz, 7.89
        1.045
    • 800x600:
      • Prophet @ 185MHz, 7.89
        1.061
      • Prophet @ 175, 7.103
        1.047
      • Prophet @ 175MHz, 7.89
        1.043
    • 1024x768:
      • Prophet @ 185MHz, 7.89
        1.054
      • Prophet @ 175, 7.103
        1,050
      • Prophet @ 175MHz, 7.89
        1,042
    • 1280x1024:
      • Prophet @ 175MHz, 7.89
        1.012
      • Prophet @ 185MHz, 7.89
        1.002
      • Prophet @ 175, 7.103
        1.001
    • 1600x1200:
      • Prophet @ 185MHz, 7.89
        935
      • Prophet @ 175MHz, 7.89
        933
      • Prophet @ 175, 7.103
        928
    Overclocking 3DMark 2001 32Bit
    Unit: Points
    • 640x480:
      • Prophet @ 185MHz, 7.89
        1.051
      • Prophet @ 175, 7.103
        1.044
      • Prophet @ 175MHz, 7.89
        1.035
    • 800x600:
      • Prophet @ 175, 7.103
        1.038
      • Prophet @ 185MHz, 7.89
        1.037
      • Prophet @ 175MHz , 7.89
        1.024
    • 1024x768:
      • Prophet @ 185MHz, 7.89
        988
      • Prophet @ 175, 7.103
        979
      • Prophet @ 175MHz, 7.89
        974
    • 1280x1024:
      • Prophet @ 175, 7.103
        938
      • Prophet @ 175MHz, 7.89
        936
      • Prophet @ 185MHz, 7.89
        935
    • 1600x1200:
      • Prophet @ 185MHz, 7.89
        825
      • Prophet @ 175, 7.103
        824
      • Prophet @ 175MHz, 7.89
        812
    Overclocking Aquamark 16Bit
    • 640x480:
      • Prophet @ 185MHz, 7.89
        8.6
      • Prophet @ 175MHz, 7.89
        8.3
    • 800x600:
      • Prophet @ 185MHz, 7.89
        8.3
      • Prophet @ 175MHz, 7.89
        8.2
    • 1024x768:
      • Prophet @ 175MHz, 7.89
        8.0
      • Prophet @ 185MHz, 7.89
        7.9
    • 1280x1024:
      • Prophet @ 185MHz, 7.89
        7,1
      • Prophet @ 175MHz,7.89
        7.1
    • 1600x1200:
      • Prophet @ 175MHz, 7.89
        5.5
      • Prophet @ 185MHz, 7.89
        5.4
    Overclocking Aquamark 32Bit
    • 640x480:
      • Prophet @ 185MHz, 7.89
        8.3
      • Prophet @ 175MHz, 7.89
        8.3
    • 800x600:
      • Prophet @ 185MHz, 7.89
        8.2
      • Prophet @ 175MHz, 7.89
        8.2
    • 1024x768:
      • Prophet @ 185MHz, 7.89
        7.9
      • Prophet @ 175MHz, 7.89
        7,9
    • 1280x1024:
      • Prophet @ 185MHz, 7.89
        7.0
      • Prophet @ 175MHz, 7.89
        7.0
    • 1600x1200:
      • Prophet @ 185MHz, 7.89
        5,3
      • Prophet @ 175MHz, 7.89
        5,3

    Problems

    During our test of the Hercules Prophet 4500, we actually encountered very few problems, but they caused them to Driver updates can be removed, or have already been. For example, in Unreal Tournament in 16-bit color mode, there were small texture errors in individual places, where instead of a very dark floor, there was simply a black floor that could not be brightened by ambient lights or rockets. This bug isbut only present in the driver supplied with the card; the last driver update, however, eliminated this error. Furthermore, the 16-bit mode with the Hercules 3D Prophet 4500 should be taboo, since the card's performance in 16-bit or 32-bit makes no difference. Another problem is that of forced texture compression. If you activate this in OpenGL mode and then start Quake3, gross and noticeable texture errors occur in the game. However, as soon as you activate texture compression in the game itself, these graphics errors have disappeared. Another problem with the drivers is the activation of full-screen antialiasing (FSAA). It was possible to force this setting in the drivers, so there were no further problems, only when the drivers were supposed to activate the anti-aliasing method themselves did problems arise. Aquanox didn't even recognize that there was support for FSAA, which may well be due to the development status of the benchmark. It was possible to activate this function in 3DMark 2001, but the tests still ran without anti-aliasing and accordingly without any noticeable quality improvement. However, I am sure that such problems can be eliminated with future drivers.

    On the next page: Conclusion

    Comments