A.I. Install Guide for Darknet
Follow this guide on your 2nd PC to correctly install OpenCV with CUDA support . Note that this is only needed for older versions of Moonlight which are not recommended.
Last updated
Follow this guide on your 2nd PC to correctly install OpenCV with CUDA support . Note that this is only needed for older versions of Moonlight which are not recommended.
Last updated
Download the OpenCV build from the provided Google Drive link.
Extract the ZIP file to C:\
, ensuring it is not nested inside another folder.
The final directory should be:
C:\opencv-build
If you see C:\opencv-build\opencv-build
, move the contents to just C:\opencv-build
.
Open File Explorer and navigate to C:\opencv-build
.
Locate and run installer(GPU).bat
.
right-click and select 'Run as administrator'.
The installer can take up to 40 minutes to download the dependencies needed to build opencv with cuda support.
When prompted, choose the GPU architecture that matches your graphics card.
For NVIDIA 40-series GPUs, select the 30-series option instead.
The build phase can take up to 40 minutes depending on GPU.
Wait for the installation to finish.
Take a screenshot of the final output and share it as requested. This step is important because it allows us to check if there are any errors in the install.
Issue: CUDA or cuDNN Failed to Install
If the build phase completes early and the output indicates that CUDA or cuDNN has failed (or shows "NO" next to it), follow these steps:
Open Visual Studio Installer.
Click Resume if it needs to finish installing.
Download CUDA 11.1 from the official NVIDIA site.
After Visual Studio has finished being installed, install CUDA 11.1 following the on-screen instructions.
After installation is complete, go back to C:\opencv-build
.
Run build.bat
.
Select your GPU architecture when prompted.
The installation should now proceed successfully.
Other Troubleshooting Tips:
If you encounter errors, verify that you extracted the folder correctly to C:\opencv-build
.
If the batch script fails, make sure you were running Command Prompt as Administrator.