IDirect3DDevice9::UpdateSurface vs LockRect/UnlockRect

IDirect3DDevice9::UpdateSurface vs LockRect/UnlockRect

I am experimenting with encoding from system memory, and I had the following thought.

Just wondering if anybody at Intel thinks there would be speed benefits to using UpdateSurface() to load D3D surfaces from system memory during encoding rather than use LockRect()/UnlockRect() as per the examples.



2 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Hi Cameron,

As far as I know this is not something we have explored. But that approach seems to be somewhat constrained, since you would somehow have to store your system memory surfaces in a D3D surface container. Anyways, I've personally not explored this.

If you find a suitable way of doing this which brings good performance, feel free to share your findings on this forum.

BTW. if you are using system memory surfaces as input to the do not have to lock surface ahead of copying data into it.


Leave a Comment

Please sign in to add a comment. Not a member? Join today