Just Cause 3 - i5 4690K & GTX 770 - FPS test and settings
Greetings, everyone.\r
\r
Today were going to do some testing of Just Cause 3, the much anticipated game from Avalanche Studios.\r
\r
This game makes use of the Avalanche engine, an in house solution that has worked pretty well on previous games and we can see how well it performed in Mad Max, the latest game using this engine before Just Cause 3.\r
\r
So, as usual, my current PC specs are the following:\r
\r
-CPU: i5 4690K@4.4 GHz (Turbo).\r
-Mobo: Asus Maximus VII Ranger.\r
-GPU: Asus GTX 770 DirectCU II OC 2 GB with no extra OC and latest Game Ready driver.\r
-RAM: 16 GB DDR3@1866, 9-10-9-28.\r
-Storage: Kingston SSDNow 300, 240 GB where both game and O.S. are installed.\r
-O.S: Windows 7 Ultimate SP1 64bit with latest updates.\r
\r
\r
Note that Im using the latest game ready driver released today (version 359.06) and if you didnt install that one yet, its probably a good idea.\r
\r
So, as we can see in the video, the game has a vast array of graphical options, as expected considering previous Avalanche games. Its quite nice to see several antialiasing methods, some of them with temporal component, something that its quite needed for this type of game where were playing on a huge island with vegetation, trees, and lots of objects and textures very subject to get visual artifs when moving the camera; But in this case, there seems to be some visual artifs in conjunction with motion blur and the antialiasing methods will give us some strange results at times.\r
\r
As for performance on my system, we can see how the game runs at ultra-maximum everything, and then also on the very lowest settings. Then I try every meaningful setting to try determining its imp on performance (and BTW, the “Edge” setting is just Vignette), and eventually decide which settings are more appropriate for my system.\r
\r
All things considered, and compared to Mad Max, which was a beautiful wasteland looking world, Just Cause 3s world is more full with stuff, a huge lot of explosions, details, vegetation, etc., things that were not present in Mad Max or to a lesser degree. So, its only natural that Just Cause 3 is a way more demanding game that Mad Max, and it clearly shows bath on CPU usage, GPU taxing settings and quite a bit of RAM consumed there, as well, at least on my system.\r
\r
In any case, this customized version of the Avalanche engine Just Cause 3 runs on feels quite different from its Mad Max iteration and on my system it doesnt run as smooth as the other title did, but the worlds are quite different and Just Cause 3 has a ton more of physics going on, which all of them work on the CPU, so keep that in mind.\r
\r
As usual, I hope this video can be useful to you guys, and Ill see you next time : )
\r
Today were going to do some testing of Just Cause 3, the much anticipated game from Avalanche Studios.\r
\r
This game makes use of the Avalanche engine, an in house solution that has worked pretty well on previous games and we can see how well it performed in Mad Max, the latest game using this engine before Just Cause 3.\r
\r
So, as usual, my current PC specs are the following:\r
\r
-CPU: i5 4690K@4.4 GHz (Turbo).\r
-Mobo: Asus Maximus VII Ranger.\r
-GPU: Asus GTX 770 DirectCU II OC 2 GB with no extra OC and latest Game Ready driver.\r
-RAM: 16 GB DDR3@1866, 9-10-9-28.\r
-Storage: Kingston SSDNow 300, 240 GB where both game and O.S. are installed.\r
-O.S: Windows 7 Ultimate SP1 64bit with latest updates.\r
\r
\r
Note that Im using the latest game ready driver released today (version 359.06) and if you didnt install that one yet, its probably a good idea.\r
\r
So, as we can see in the video, the game has a vast array of graphical options, as expected considering previous Avalanche games. Its quite nice to see several antialiasing methods, some of them with temporal component, something that its quite needed for this type of game where were playing on a huge island with vegetation, trees, and lots of objects and textures very subject to get visual artifs when moving the camera; But in this case, there seems to be some visual artifs in conjunction with motion blur and the antialiasing methods will give us some strange results at times.\r
\r
As for performance on my system, we can see how the game runs at ultra-maximum everything, and then also on the very lowest settings. Then I try every meaningful setting to try determining its imp on performance (and BTW, the “Edge” setting is just Vignette), and eventually decide which settings are more appropriate for my system.\r
\r
All things considered, and compared to Mad Max, which was a beautiful wasteland looking world, Just Cause 3s world is more full with stuff, a huge lot of explosions, details, vegetation, etc., things that were not present in Mad Max or to a lesser degree. So, its only natural that Just Cause 3 is a way more demanding game that Mad Max, and it clearly shows bath on CPU usage, GPU taxing settings and quite a bit of RAM consumed there, as well, at least on my system.\r
\r
In any case, this customized version of the Avalanche engine Just Cause 3 runs on feels quite different from its Mad Max iteration and on my system it doesnt run as smooth as the other title did, but the worlds are quite different and Just Cause 3 has a ton more of physics going on, which all of them work on the CPU, so keep that in mind.\r
\r
As usual, I hope this video can be useful to you guys, and Ill see you next time : )