Sign in to follow this  
yckx

D3D11 Device and DeviceContext

Recommended Posts

I'm working with D3D11 and it's fun and all, but I don't really understand Microsoft's decision to split the D3DDevice into device and device context. I just don't see the benefit. This is (at least) partly because I've never really grokked what a context is supposed to represent. The pattern appears to be that that the device is used to create other D3D objects, and then the device context is used to manipulate them. How is that better than keeping it all together?

Share this post


Link to post
Share on other sites
Hodgeman basically hit the nail on the head - the design change was done more or less to support multithreading. In the end, by separating the resource management from the operations, it makes it quite easy to implement multithreaded rendering paradigms without imposing the solution on the user. Overall, I am quite impressed with the solution...

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this