[PcGameshardware] The Witcher 3 Benchmark

[Silverforce11]

You can repeat what ever you want but Luxmark is an OpenCL benchmark, when nVidia's focus was on Cuda, imho. I would like to see data on Direct Compute.

I'm surprised he didn't know Luxmark heavily favors AMD due to OpenCL.

Either way, the suggestion here is that Forward+ rendering via DX11 compute is killing Kepler performance (when Hairworks OFF).

But the Dirt series uses Forward+, and numbers in Dirt Rally is very impressive for Kepler.

You can see the 960 is down below where it belongs, away from being close to Titan. Note its Alpha and already very optimized.

AMD presented at GDC 2003 on Forward+ and like all of its GE features, open source, NO encryption or obfuscation of code. All developers can look at the raw code to optimize it further. Crytek took parts of it to use in their engines. NV can access it freely and have every opportunity to optimize for it. As such, Kepler can run very well with Forward+ rendering.

 

[Azix]

You can repeat what ever you want but Luxmark is an OpenCL benchmark, when nVidia's focus was on Cuda, imho. I would like to see data on Direct Compute. edit: Also the comparison with compute for the GTX 780 was using a different operating system -- osx -- and the 780 does much better with Windows.

Not running an open standard well is nvidia's problem really. it's open.

 

[Erenhardt]

Hairworks and non-hairworks.
R9 285 tessellation monster vs R9 280X.
R9 280X win with tessellated hairs but loses without it...

Strange...

Also, strange that their CPU results do not line up with gpu results at all...
GPU test is done with i5-4790 @4.5, but the numbers for OCed i5 in CPU test are way higher.

 

[tg2708]

That 770 number sounds right. Been playing it for the last 4 hours. Amazing game. Graphics are obviously downgraded, but been enjoying the story nevertheless.

Yea I checked the graphics settings when I first booted the game and just left the sliders where they were. Jumped in game and immediately noticed that messing with one or two could have caused performance issues but as it is it runs fairly well. Game is fun. I'm still in my infancy stage but its quite enjoyable.

 

[Freddy1765]

Been playing for about 5 hours, and just left the first area (White Orchard).
The gameplay is fun, for sure. Graphically, it's hardly mindblowing. Textures and character models are quite nice, but foliage in particular looks terrible. It's so 2-dimensional and bland to look at. Lighting effects also leave something to be desired; it appears quite static, if that's the right word. Sure, sunsets are pretty, but it's like there's no real interaction between the light and objects in the world.
I wonder if a PC-exclusive patch will improve any of those things in future.

 

[Enigmoid]

Game GPU

http://gamegpu.ru/rpg/rollevye/the-witcher-3-wild-hunt-test-gpu.html

Not demanding at all.

 

[Flapdrol1337]

Not demanding at all.

On the cpu that is, it's a real gpu killer.

 

[Subyman]

May wait for the enhanced edition or at least a nice community patch. I want to play it when it is as good as it gets.

 

[Head1985]

GTX670 vs 970 on same clock.1920x1080 All max with hairworks+HBAO+ and with shadows tweak for better shadows from
http://www.geforce.com/whats-new/gu...eaking-guide#the-witcher-3-wild-hunt-tweaking
GTX670 1280mhz

970 1280mhz

GTX970 1500/8000

 

[96Firebird]

Except that Hawaii is beating Maxwell in this benchmark. Maxwell doesn't seem to be suffering in TW3 though. Doesn't this kinda kill your theory?

But remember, this is a GW game. According to some, Nvidia has to kill Hawaii cards somehow...

DC is only part of the graphics rendering. There are many more variables, but if the bottleneck is in the compute, bye-bye Kepler.

But the Dirt series uses Forward+, and numbers in Dirt Rally is very impressive for Kepler.

AMD presented at GDC 2003 on Forward+ and like all of its GE features, open source, NO encryption or obfuscation of code. All developers can look at the raw code to optimize it further. Crytek took parts of it to use in their engines. NV can access it freely and have every opportunity to optimize for it. As such, Kepler can run very well with Forward+ rendering.

You're right, Kepler is doing well in Dirt Rally. I'm not an expert on this stuff, but can the amount of DC be changed on a game-to-game basis? Does Dirt Rally have as many jaggies that the Forward+ AA solution takes care of, compared to something like Ryse?

And like I already said, it doesn't matter if Forward+ is open. It runs on DirectCompute, and like Anandtech's benchmarks show, Kepler does not do well in DC. I don't think there is any way to optimize for that...

 

[Termie]

I ran some benchmarks on three of my cards, a GTX 980, GTX 780 Ti, and an R9 290, and came up with some pretty surprising findings. Here's my blogpost about it.

In short, it's not Gameworks that's causing the problem for Kepler. But Kepler is definitely under-performing in this game, so something in the game engine is hitting it really hard.

Thoughts?

 

[thilanliyan]

I ran some benchmarks on three of my cards, a GTX 980, GTX 780 Ti, and an R9 290, and came up with some pretty surprising findings. Here's my blogpost about it.

In short, it's not Gameworks that's causing the problem for Kepler. But Kepler is definitely under-performing in this game, so something in the game engine is hitting it really hard.

Thoughts?

Thanks for that. I also noticed that with my 290, Hairworks nearly halved my fps.

 

[gamervivek]

What's surprising about it when you've replicated the results from the first page?

 

[thilanliyan]

What's surprising about it when you've replicated the results from the first page?

I haven't looked at many benchmarks. I'm surprised that it is that much of a hit.

 

[escrow4]

I ran some benchmarks on three of my cards, a GTX 980, GTX 780 Ti, and an R9 290, and came up with some pretty surprising findings. Here's my blogpost about it.

In short, it's not Gameworks that's causing the problem for Kepler. But Kepler is definitely under-performing in this game, so something in the game engine is hitting it really hard.

Thoughts?

Define hitting hard. I can hit 55-60FPS on the high preset with Ultra textures, SSAO and Hairworks disabled. More or less locked to 60FPS with the in game limiter. A 980 could up 4 or 5 settings another notch up and can just about hit 60 FPS. Fine. I'd be moaning if the game ran like a dog on Medium, but this isn't too bad. Under-performing, sure.

Like so:

 

[tential]

Define hitting hard. I can hit 55-60FPS on the high preset with Ultra textures, SSAO and Hairworks disabled. More or less locked to 60FPS with the in game limiter. A 980 could up 4 or 5 settings another notch up and can just about hit 60 FPS. Fine. I'd be moaning if the game ran like a dog on Medium, but this isn't too bad. Under-performing, sure.

Like so:

I'm still surprised you use the 780 ti rather than pick up a new card. I'd have thought your performance tolerance wouldn't be met by the 780 ti at this point haha. Waiting for the 980ti?

 

[DiogoDX]

I'm surprised he didn't know Luxmark heavily favors AMD due to OpenCL.

Either way, the suggestion here is that Forward+ rendering via DX11 compute is killing Kepler performance (when Hairworks OFF).

But the Dirt series uses Forward+, and numbers in Dirt Rally is very impressive for Kepler.

You can see the 960 is down below where it belongs, away from being close to Titan. Note its Alpha and already very optimized.

http://gamegpu.ru/images/remote/http--www.gamegpu.ru-images-stories-Test_GPU-Simulator-DiRT_Rally-test-drt_1920.jpg[/img

[img]http://gamegpu.ru/images/remote/http--www.gamegpu.ru-images-stories-Test_GPU-Simulator-DiRT_Rally-test-drt_2560.jpg[/img

AMD presented at GDC 2003 on Forward+ and like all of its GE features, open source, NO encryption or obfuscation of code. All developers can look at the raw code to optimize it further. Crytek took parts of it to use in their engines. NV can access it freely and have every opportunity to optimize for it. As such, Kepler can run very well with Forward+ rendering.[/QUOTE]
Withcer 3 is using Forward+?

One of the best benefits is the ability to do the traditional cheap hardware MSAA but they have to create their own post AA for the game and there is no option for MSAA in the game menu.

 

[5150Joker]

Game GPU

http://gamegpu.ru/rpg/rollevye/the-witcher-3-wild-hunt-test-gpu.html

Not demanding at all.

So now where are all the guys talking about the sky falling and NVIDIA abandoning Kepler? Seems to be doing fine to me.

 

[DooKey]

Free copy of Witcher 3 for Titan X owners. Go to this thread: http://forums.anandtech.com/showthread.php?p=37413716#post37413716

 

[casiofx]

So now where are all the guys talking about the sky falling and NVIDIA abandoning Kepler? Seems to be doing fine to me.

Invalid comparison, that chart you quoted have Hairworks turned on. Everyone knows Hairworks run like turtle on Radeons.

But remember, this is a GW game. According to some, Nvidia has to kill Hawaii cards somehow...

That somehow is Hairworks, it gave Nvidia a big marketing advantage for their geforce cards

 

[nsavop]

Invalid comparison, that chart you quoted have Hairworks turned on. Everyone knows Hairworks run like turtle on Radeons.

I think he talking about Kepler performing "normal" on the gamegpu chart despite earlier reports showing it much worse.

 

[casiofx]

I think he talking about Kepler performing "normal" on the gamegpu chart despite earlier reports showing it much worse.

OK thanks.

By the way, anyone tried overriding the Tessellation options in Catalyst Control Centre? I set override to 8x and turning on Hairworks to all dropped my fps from 70+ to around 55 in a small recovered town in White Orchard, not bad. I'm running on 1150MHz on the R9 290. The hair looked a bit worse than the default stock options for Tessellation though.

 

[DiogoDX]

OK thanks.

By the way, anyone tried overriding the Tessellation options in Catalyst Control Centre? I set override to 8x and turning on Hairworks to all dropped my fps from 70+ to around 55 in a small recovered town in White Orchard, not bad. I'm running on 1150MHz on the R9 290. The hair looked a bit worse than the default stock options for Tessellation though.

https://www.reddit.com/r/witcher/comments/36jpe9/how_to_run_hairworks_on_amd_cards_without/


Other tweak:

Tip for FPS gain while using HairWorks.
HairWorks automatically sets the Anti Aliasing for the HairWorks to 8x MSAA and does not let you change this in game. This is why HairWorks is such an FPS killer.

To give you better performance while using HairWorks, go into The Witcher 3 folder, then go into "bin", then "config", then "base", then click on the "rendering.ini". Now look for "HairWorksAALevel=8", change the number at the end to 4, 2 or even zero. Easy as, easy FPS gain.


Lowering the Anti Aliasing value will not give you a lesser version of HairWorks, it works the same as any other Anti Aliasing, it just depends how jaggy you want your hair, or how important that is to you compared to performance.

http://steamcommunity.com/app/292030/discussions/0/617335934150506844/#p3

 

[Azix]

That hairworks is strange. It seems its not really the calculations that make it taxing, but the fancy graphics they have to put on it to give it volume. Seems imaginable they could have found a better way.

 

[5150Joker]

Invalid comparison, that chart you quoted have Hairworks turned on. Everyone knows Hairworks run like turtle on Radeons.

Yeah ok whatever you say.