- Oct 12, 2010
- 1,469
- 21
- 81
http://www.rebellion.co.uk/blog/2014/10/2/mantle-comes-to-sniper-elite-3
Some interesting stuff there.
Some interesting stuff there.
Surprising that they got decent gains in a very GPU limited game. The CPU isn't bottlenecked at all.
Interesting they noted a lot of the gains came from better memory access and control, as well as their engine's ability to hold more high-res textures in memory simultaneously, improving IQ.
Hopefully DX12 will enable these finer "to-the-metal" features.. but I suspect we may be seeing some GCN specific features in play here.
All right, I will take the bait. First, I would wait for independent tests. Secondly, the highest gains are at resolutions that I seriously doubt anyone will be using. Only around a 5 to 12 percent gain at settings that I would expect people to be playing when using the 3770k.
I do have an AMD card. This is not a game that I would be interested in buying, but it would be nice if they put out a demo that I could use to test out mantle with my older HD7770.
13% gain at 1920x1200 max settings while increasing IQ is bad? :|
What bait are you talking about?
PD: Would kill for the async compute. Would be really nice to put that APU iGP or Intel CPU iGP to do some useful work.
Can you pick some benches to us?? You have two 290s here, Mantle may make you FPS numbers explode!
This is not surprising. This is Asynchronous Compute, first time on PC, yay. They run the shadow mapping phase and the Obscurance Fields effect in parallel. So if the GPU has enough CUs (20+), than the entire Obscurance Fields effect will be free. Yes, you read that right, activating it won't affect the performance.Surprising that they got decent gains in a very GPU limited game. The CPU isn't bottlenecked at all.
This is not surprising. This is Asynchronous Compute, first time on PC, yay. They run the shadow mapping phase and the Obscurance Fields effect in parallel. So if the GPU has enough CUs (20+), than the entire Obscurance Fields effect will be free. Yes, you read that right, activating it won't affect the performance.
The direct memory management also useful in GPU-limited scenarios.
This is not surprising. This is Asynchronous Compute, first time on PC, yay. They run the shadow mapping phase and the Obscurance Fields effect in parallel. So if the GPU has enough CUs (20+), than the entire Obscurance Fields effect will be free. Yes, you read that right, activating it won't affect the performance.
The direct memory management also useful in GPU-limited scenarios, especially for an Asura-like texture streaming system.
There’s still a fair amount of scope for increasing performance with Mantle, particularly as we’re not yet taking advantage of the Asynchronous Compute queue. This would allow us to take some of our expensive compute shaders – like our Obscurance Fields technique – and schedule them to run in parallel with the rendering of shadow maps, which are particularly light on ALU work.
Our main goal for supporting Mantle was to take maximum advantage of the potential for multithreading the API calls, and refactor our existing engine rendering pipeline to better fit what we predict are the requirements of this new breed of lightweight APIs. In that respect we spent more time restructuring our engine's rendering architecture than we did writing Mantle-specific code!
Key quote in here is:
Mantle gives them the opportunity to rework their engine architecture today, so when DirectX 12 comes along they are ready. If DX12 supports the same low-level designs then porting should be easy.
I really think DX12 is going to be Mantle with access to other companies GPU's tacked on. Hopefully Msft won't weigh it down too much and have it well optimized for all.
Mantle and DX12 is 2 completely different things. And AMD is the one not being mentioned anywhere in the countless DX12 statements from MS.
http://blogs.msdn.com/b/directx/archive/2014/10/01/directx-12-and-windows-10.aspx
Mantle and DX12 is 2 completely different things. And AMD is the one not being mentioned anywhere in the countless DX12 statements from MS.
http://blogs.msdn.com/b/directx/archive/2014/10/01/directx-12-and-windows-10.aspx