@Corris Thanks for the insight. I was gonna hint at some form of compiler bug..

When it comes to switching fullscreen/windowd, changing buffercount/ backbuffer format and changing dimensions, you can get away with a swapchain→ResizeBuffers call.

cozzie said:

Out of curiosity; is there a specific reason/ target audience why you're upgrading to dx9 instead of say dx11?

You could have asked that 2 months ago when he first asked his question.

SyncViews said:

Also to avoid precision loss, you want more than 8 bits for any linear colour value (consider if you mapped 8bit 0-255 to 0-255 some inputs give duplicate outputs and some outputs are impossible), since shaders often use floats this isn't an issue, unless you had some intermediate 8b…

who_say_pawno said:
I have anti-aliasing enabled.

ah ok, understood, in this case, GetFrontBufferData( ) is the only way you can capture your screenshot with AA. I would then suggest running your app in full screen mode and capturing that way. There is no other way that I know of that can avoid the d…

well done and thank you for sharing your solution ?

I don’t know which version of D3DVideoSink you were using, but my understanding is that at it’s core it is using this dynamic texture method.  I.e. create texture at initialisation and then after each arrival of a decoded video frame, map (lock), copy video frame, unmap (unlock) and render

As D…

The better questions is: Why do you care?

Is it worth the work to just “turn off” Afterburner to find a way to prevent it from attaching it's overlay to your Editor instead of investing time in the Editor/ Engine itself?

If it just effects your visual view, turn it off

Real fullscreen means setting the .Windowed parameter to FALSE and setting any available resolution, which works perfectly. Fullscreen window means setting the .Windowed parameter to TRUE, making the window cover the entire screen at the current desktop resolution and creating a backbuffer matching…