• Competitor rules

    Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.

CRYSIS BENCHMARKTOOL HARBOR SCORES

Soldato
Joined
6 Oct 2007
Posts
23,159
Location
North West
I see many people say that crysis is playable in DX10 very high, the test that is used in many benchmarks on here IMO is not a very good indication of in game performance and it suprises me why we don't use the harbor test in crysis benchmarktool that is tested as you would play in game. Feel free to post up your scores, though going by my 4870 result, crysis is noway playable in DX10 very high on any machine, SLI or XFIRE included, prove me wrong.;)

TEST SETTINGS: 1680X1050, DX10 VERYHIGH SPEC, TIME OF DAY 5, 2 LOOPS OF TEST.

capture555wx4.jpg
 
Reason harbor wasn't used is it allowed people with the demo to compare benchmarks with those with the game.
 
That benchmarks pretty odd, in the first runthrough where he grabs a missle launcher there was a korean just in front of the rocket launcher with his back to the player, then the second runthrough the korean was gone.

Also seems almost slow motion in places, where he uses the first grenade looked slower than normal. :confused:
 
Ok ran through it again, this benchmark is pointless. This time in the first loop koreans at the rocket launcher pickup site actually started attacking the player, then the second time around in the same area a gunboat in the harbor started attacking the player.

Obviously comparisons are pointless as the events aren't consistant between runthroughs.

crysis-dx10.jpg
 
Last edited:
I see many people say that crysis is playable in DX10 very high, the test that is used in many benchmarks on here IMO is not a very good indication of in game performance and it suprises me why we don't use the harbor test in crysis benchmarktool that is tested as you would play in game. Feel free to post up your scores, though going by my 4870 result, crysis is noway playable in DX10 very high on any machine, SLI or XFIRE included, prove me wrong.;)

You are wrong, I get nearly 40fps at 1920x1200.

If I turn on the SLI indicator its almost completely full all the time and that is really rare in other games.
 
Last edited:
Do the bench then, there are far more taxing levels in the game than the harbor test, all of which will be nasty to play even on your 280 SLI setup.
 
I must admit I did a little worse than expected. On the regularly used "beach" benchmark I get 37fps at these settings. It is at 1900x1200 though. Average 30.7

TEST SETTINGS: 1900X1200, DX10 VERYHIGH SPEC, TIME OF DAY 5, 2 LOOPS OF TEST.

benchcry.jpg
 
Last edited:
the reason the ai is in differnt places is the game was made that way so you never see the same thing,when playing the level again...i.e die in game and reload a checkpoint.

i could be wrong but im pretty sure thats why the demo shows odd behaviour.:)
 
Don't use Harbor because quite a lot of physics is involved. So not strictly a gpu test.

One could otherwise argue that the cpu test is actually better for testing the graphics card.
 
Ouch, 22.8 fps

I also ran perfmon to see how CPU limited I am in this test, the one core is pretty much limited, the second one only used about a third.

perfmonvx6.jpg
 
Last edited:
I must admit I did a little worse than expected. On the regularly used "beach" benchmark I get 37fps at these settings. It is at 1900x1200 though. Average 30.7

TEST SETTINGS: 1900X1200, DX10 VERYHIGH SPEC, TIME OF DAY 5, 2 LOOPS OF TEST.

http://i4.photobucket.com/albums/y110/Darkwind212/benchcry.jpg[/IM][/QUOTE]

Suprisingly im roughly only about 2fps slower than that at 1920x12000, getting around 28.56fps or thereabouts. Cpu's clocked higher though. Suprising how little cpu makes a difference to this game though, clocked my cpu up 200mhz more and there was barely any change, not even a single fps, went up to about 28.66 fps.
 
Last edited:
Back
Top Bottom