-o or --out for output file?
Also, does anyone know what message is displayed or what happens if a private key is found?
It's activated with either -o or --out.
When it finds a private key it prints "Found key for address XYZ. Written to OUTPUTFILE", then in the output file it writes the address, private key in hex and compressed public key separated by space, all in one line. It looks like if you don't pass one of them, you will not get private keys printed at all.
Ive tried modifying the .props to change
<CUDA_INCLUDE>C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\include</CUDA_INCLUDE>
<CUDA_LIB>C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\lib\x64</CUDA_LIB>
<OPENCL_INCLUDE>C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\include</OPENCL_INCLUDE>
<OPENCL_LIB>C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.1\lib\x64</OPENCL_LIB>
[/color]
to
<CUDA_INCLUDE>C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.2\include</CUDA_INCLUDE>
<CUDA_LIB>C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.2\lib\x64</CUDA_LIB>
<OPENCL_INCLUDE>C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.2\include</OPENCL_INCLUDE>
<OPENCL_LIB>C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.2\lib\x64</OPENCL_LIB>
[/color]
Then building the CudaKeyFinder and KeyFinder in VS2019 (Release x64) but it will not work for me, I am most likely doing something wrong.
P.S. When running on linux the most up to date cuda drivers had no problems running on my 2080, 2080ti, and 3070. there is most likely just a problem with the last release and the compute capability with cuBitCrack from brichard19.
VS doesn't read the Makefiles when it complies the Windows version so the things in the Props file and each .vcxproj are the only things it reads.
Did you check to see if the path to CUDA 11.2 is called C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.2? Also paste the errors from the VS build window here, it'll be helpful to know what's going on.