-
Beta Was this translation helpful? Give feedback.
Replies: 0 comments 15 replies
-
Could you provide the logs? You should be getting 120fps easily. |
Beta Was this translation helpful? Give feedback.
-
Also check CPU usage. It should be low if GPU patch is successful. |
Beta Was this translation helpful? Give feedback.
-
"Screencasting with X11" this means that you are not using nvfbc, which is the purpose of patching the driver. If it is working correctly you would see "Screencasting with NvFBC". This could be that the driver patch wasn't successful. |
Beta Was this translation helpful? Give feedback.
-
Also check the CPU usage per core with htop or similar and not the overall percent. If one says 100% then you are CPU bound. The idea with nvfbc is to offload more to the GPU and avoid copying frames between GPU and RAM. |
Beta Was this translation helpful? Give feedback.
-
On the keylase front page, there is patch.sh and patch-fbc.sh. Have you applied both? The NVENC patch "removes restriction on maximum number of simultaneous NVENC video encoding sessions" - this won't help you. What you need is the NvFBC patch. |
Beta Was this translation helpful? Give feedback.
-
I've continued working on this issue and trying to troubleshoot things a bit. I've since updated my graphics driver and patched it again, and tested my NvFBC capabilities using https://developer.nvidia.com/capture-sdk which now appears to work when running NvFBCCUDAAsync. I also rebuilt sunshine after updating my graphics drivers and verifying NvFBC was working with the aforementioned SDK. |
Beta Was this translation helpful? Give feedback.
-
Issue has been solved! Turns out, my built copy was never detecting CUDA even though I had it installed, which was confusing me so I tried to use nvcc on a sample project and as it turns out, while the build instructions do specify to install g++-10, they don't call for g++ which was making nvcc fail and make everything compile without CUDA despite it being present. Installing g++ and rebuilding from source fixed it, as well as using 510.68.02 as 510.60.02 requires downgrading vulkan. |
Beta Was this translation helpful? Give feedback.
Issue has been solved! Turns out, my built copy was never detecting CUDA even though I had it installed, which was confusing me so I tried to use nvcc on a sample project and as it turns out, while the build instructions do specify to install g++-10, they don't call for g++ which was making nvcc fail and make everything compile without CUDA despite it being present. Installing g++ and rebuilding from source fixed it, as well as using 510.68.02 as 510.60.02 requires downgrading vulkan.