Re:Zelda: The Wind Waker – Tech and Texture Analysis
by Narishma on Sunday June 15, 2014 @11:38AM
(#7895451)
The lack of instancing is because there's no need for it. Consoles in general have low-level graphics APIs that let you make tons of drawcalls without the performance issues you get on PC.
[ Parent
| on HN ]
Re:Zelda: The Wind Waker – Tech and Texture Analysis
by glhaynes on Sunday June 15, 2014 @11:44AM
(#7895467)
Anybody got a quick explanation for why desktop APIs have such trouble with lots of drawcalls? What is it that Mantle, Metal, etc. do differently that saves so much time?
(And how much of that is a problem with just OpenGL vs. how much does it apply to DirectX as well?)
Re:Zelda: The Wind Waker – Tech and Texture Analysis
by corysama on Sunday June 15, 2014 @06:00PM
(#7896483)
MS's presentation on Direct12 does a good job of breaking down the problems with classic API models and how DX12 (very similar to Mantle) fixes them.
http://channel9.msdn.com/Events/Build/2014/3-564
youtube dupe: http://www.youtube.com/watch?v=m0QkjKGZQzI
Re:Zelda: The Wind Waker – Tech and Texture Analysis
by tpl on Sunday June 15, 2014 @02:15PM
(#7895856)
http://renderingpipeline.com/2014/06/whats-the-big-deal-with...
That blog post should help you clarify the difference. I think the primary problem it that OpenGL and DirectX handle changes in pipeline state very poorly.