Sign in to follow this  
tcige

how direct3d waits when not using D3DPRESENT_INTERVAL_IMMEDIATE

Recommended Posts

if using D3DPRESENT_INTERVAL_IMMEDIATE, the core usage is high

 

but if not using D3DPRESENT_INTERVAL_IMMEDIATE, the core usage is almost 0

 

so how direct3d waits internally, ZwWaitForSingleObject or ZwDelayExecution or some way?

 

and for D3DPRESENT_INTERVAL_IMMEDIATE, why the core usage is not 100%?

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