WEBVTT

00:00:08.080 --> 00:00:14.960
you know what I say tigers are Chumps I just took one out with a bow and arrow

00:00:12.559 --> 00:00:18.800
with fire on it so there you go take that tiger but in all seriousness this

00:00:17.080 --> 00:00:23.800
video is about our Far Cry 3 benchmarking procedure so we want to

00:00:20.800 --> 00:00:25.840
show you guys exactly how we run it down

00:00:23.800 --> 00:00:29.119
to well okay the settings will vary depending on what class of graphics

00:00:27.439 --> 00:00:34.040
cards we're running but we want to show you how we achieve a reproducible real

00:00:32.200 --> 00:00:38.000
world benchmarking scenario so it's in this case slick found one of the trials

00:00:36.000 --> 00:00:41.879
that involves racing around a course and we want to show you guys how you can run

00:00:39.920 --> 00:00:45.600
exactly the same Benchmark as us using fraps and compare your system to

00:00:43.840 --> 00:00:49.039
whatever we're testing on our test bench this will give you a really good idea of

00:00:47.399 --> 00:00:53.559
how it Stacks up compared to newer Hardware that comes out as we test it so

00:00:51.440 --> 00:00:57.680
without further Ado here is Slick's benchmarking procedure for Far Cry

00:00:58.920 --> 00:01:01.920
3

00:01:28.840 --> 00:01:34.129
h

00:01:40.079 --> 00:01:44.520
[ __ ] [ __ ] this I got

00:01:58.840 --> 00:02:01.840
the

00:02:09.440 --> 00:02:11.879
[ __ ]

00:02:15.080 --> 00:02:18.280
this for

00:02:23.120 --> 00:02:26.120
the

00:02:28.760 --> 00:02:31.760
the

00:02:50.080 --> 00:02:58.120
that see [ __ ] [ __ ]

00:02:55.120 --> 00:02:58.120
[ __ ]

00:02:58.760 --> 00:03:01.760
you're

00:03:13.120 --> 00:03:16.120
[ __ ]

00:03:24.680 --> 00:03:28.280
drop [ __ ]

00:03:28.680 --> 00:03:33.480
Dam take

00:03:43.000 --> 00:03:48.599
theic so what you see me doing actually has nothing to do with the benchmarking

00:03:47.000 --> 00:03:54.200
procedure that you just saw quite clearly but oops shooting civilians will

00:03:52.079 --> 00:03:57.799
not be tolerated I just blew one up like 2 seconds ago and it didn't seem to care

00:03:56.200 --> 00:04:03.480
but I just want to show you guys what we run in fraps in order to Run The

00:04:00.040 --> 00:04:06.720
Benchmark so settings wise we are going

00:04:03.480 --> 00:04:09.480
to set a benchmarking hotkey and set it

00:04:06.720 --> 00:04:13.280
to stop bench marking after 120 seconds we always run a two-minute run now I

00:04:11.360 --> 00:04:16.880
would recommend for consistency's sake do some practice and see how close you

00:04:15.400 --> 00:04:20.759
can get it with the same hardware and the same settings before you rely on

00:04:18.880 --> 00:04:24.919
yourself to use this to actually measure performance so all you have to record is

00:04:22.960 --> 00:04:30.639
min max and average and it's going to spit out a CSV file that looks a little

00:04:27.600 --> 00:04:33.120
something like this c/ wraps benchmarks

00:04:30.639 --> 00:04:37.400
and here's all the benchmarks we've run on this drive since we started it up so

00:04:35.280 --> 00:04:41.840
here let's have a look at I don't know some Far Cry 3 Benchmark or something so

00:04:40.199 --> 00:04:46.160
this will tell you the minimum the Max and the average apparently this

00:04:44.199 --> 00:04:51.440
particular run slick was basically looking at a rock because that's very

00:04:48.560 --> 00:04:54.759
very consistent mid Max and average but that's pretty much it don't forget to

00:04:53.520 --> 00:05:00.039
subscribe to L this Tech tips for more unboxings reviews and other computer

00:04:57.039 --> 00:05:00.039
videos