1
00:00:00,440 --> 00:00:09,759
just for entertainment Factor more than anything else I wanted to try running

2
00:00:04,680 --> 00:00:13,719
Hawks 2 on the AMD Fusion

3
00:00:09,759 --> 00:00:16,000
E350 Apu so this is a mini ITX board

4
00:00:13,719 --> 00:00:21,160
from Gigabyte featuring The E350 which is both a CPU and a GPU it is both in

5
00:00:18,760 --> 00:00:26,039
one so I just want to tell you guys right off the bat okay so we're only

6
00:00:22,680 --> 00:00:28,439
getting about 20 to 30 FPS here and this

7
00:00:26,039 --> 00:00:33,120
is running at very low detail so you can see the aliasing is fairly ID we're only

8
00:00:30,960 --> 00:00:38,040
running at shoot I forget what it is like 1024x 600 res or something like

9
00:00:35,840 --> 00:00:43,879
that and all the details are turned down but the game does

10
00:00:40,200 --> 00:00:45,520
run and uh for single player as long as

11
00:00:43,879 --> 00:00:50,280
you don't get you know too deep into these too as long as you get don't get

12
00:00:47,640 --> 00:00:53,559
too close to the landscape uh it may actually be functional hard to say

13
00:00:52,160 --> 00:00:56,920
depends some people have much lower thresholds than others I personally

14
00:00:55,160 --> 00:01:00,519
wouldn't be able to play it at this kind of a frame rate but uh it looked a

15
00:00:59,160 --> 00:01:05,040
little bit better before near the beginning I guess now uh we're probably

16
00:01:02,559 --> 00:01:09,400
running into a more CPU bottleneck kind of scenario than GPU based on all of the

17
00:01:07,640 --> 00:01:14,240
planes falling apart all the effects that are going on so um yeah what I'm

18
00:01:12,520 --> 00:01:18,759
going to do is I'm going to run it at full details and just to see what kind

19
00:01:16,560 --> 00:01:22,360
of a performance difference we actually see but first I'll get you guys the

20
00:01:20,240 --> 00:01:27,079
overall Benchmark score here so here's the overall Benchmark score running

21
00:01:24,640 --> 00:01:30,479
everything on low at the lowest possible res supported by the game and wide

22
00:01:28,880 --> 00:01:36,600
screen and all that good stuff Stu so I'll be back in a moment with my full

23
00:01:32,960 --> 00:01:39,680
quality directx11 results so just for

24
00:01:36,600 --> 00:01:41,960
fun I decided to see you know for

25
00:01:39,680 --> 00:01:49,040
forgetting about playable settings on the E350 AMD's Fusion Apu I decided for

26
00:01:46,759 --> 00:01:55,159
Giggles I was going to turn the details up run this baby at 1080p with

27
00:01:52,439 --> 00:02:00,240
tessellation on no anti-aliasing but everything else set to high to see what

28
00:01:57,960 --> 00:02:05,360
kind of results we can get in a legitimate direct X11 game at HD

29
00:02:02,719 --> 00:02:10,840
resolution supporting the latest dx11 features like say for example heavy

30
00:02:08,239 --> 00:02:15,200
tessellation that uh we have going on in this game so we were able to achieve 8

31
00:02:12,840 --> 00:02:21,280
FPS average which unfortunately isn't really playable but you wouldn't be

32
00:02:17,280 --> 00:02:23,400
expecting to run an E350 Fusion Apu at

33
00:02:21,280 --> 00:02:27,440
1080p with the highest details in the latest games anyway so I thought this

34
00:02:25,560 --> 00:02:35,879
was an interesting experiment and thank you for checking out my video on Hawks 2

35
00:02:30,560 --> 00:02:35,879
Gaming on the E350 APU