ID3D11DeviceContext::CSSetUnorderedAccessViews

Started by
1 comment, last by DieterVW 14 years, 10 months ago
I ran across this method for the first time today, and was wondering about the usage of the last parameter. The documentation and header seem to imply that it's an array of lengths, but if so what exactly are these lengths? Looking at the samples seems to tell a completely different story; I see these two usages:

pd3dImmediateContext->CSSetUnorderedAccessViews( 0, 1, &pUnorderedAccessView, (UINT*)&pUnorderedAccessView );

ID3D11UnorderedAccessView* ppUAViewNULL[1] = { NULL };
pd3dImmediateContext->CSSetUnorderedAccessViews( 0, 1, ppUAViewNULL, (UINT*)(&ppUAViewNULL) );

These seem quite confusing to me. What exactly is getting passed, and why?
Mike Popoloski | Journal | SlimDX
Advertisement
Well, I'm at a loss. It's not even a type that can safely take a pointer.
SlimDX | Ventspace Blog | Twitter | Diverse teams make better games. I am currently hiring capable C++ engine developers in Baltimore, MD.
The docs should be fixed for the next SDK release.

The 3rd parameter is an initial count offset that will be given to the corrisponding UAV with the COUNTER or APPEND flag set during creation. Other UAV's ignore this value. -1 can be used to keep the current count value associated with the UAV.

This topic is closed to new replies.

Advertisement