NvFBC API only requires a D3DDevice pointer to capture a screen buffer into another buffer on the GPU. If NvFBC is with the NVENC H.264 encoder or captured to system memory, then a D3D9 device is not required. But if you are using NvFBC to capture to a CUDA buffer, then a D3D9 device pointer is required. Refer to the NvFBCCudaSimple sample if you want to see how to use NvFBC with the D3D9 device.
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Capture SDK 5.0 - Now available under DesignWorks | 8 | 4731 | March 8, 2020 | |
NVENC: Realtime encoding using ID3D11Texture2D as input? | 12 | 7844 | April 13, 2018 | |
NVFBC_ERROR_UNSUPPORTED_PLATFORM in Capture SDK | 2 | 10090 | October 25, 2016 | |
Direct3D device for NvFBC | 0 | 913 | June 18, 2015 | |
Get GPU buffer after NVDEC | 1 | 614 | April 20, 2018 | |
Enabling NvFBC on GeForce | 1 | 6752 | June 28, 2014 | |
How to use NVENC and NVDEC for on device transcoding? (no cpu copies) | 0 | 623 | November 8, 2022 | |
NVFBC or equivalent api for jetson devices | 4 | 1958 | March 23, 2022 | |
NVFNC can only capture desktop from X server if that loads nvidia drivers | 0 | 436 | September 13, 2023 | |
NVIDIA GRID M60 vGPU support NVENC API? | 1 | 876 | November 1, 2018 |