Hi people,
we get bug reports sometimes about CUDA rendering not working on some systems. (Rendering fails to start, error message comes up).
During the development process it’s possible that something breaks (Fault on our side), but in a lot of cases it’s a issue of the GPU / GPU driver / Operating system combination.
So I’d like to gather some feedback about working configurations to get some idea where the issues might be. Thank you.
I would also ask if the user is rendering on GPU having one of the sub windows in Rendered Mode, because then F12 GPU rendering is not working. Is this a bug?
blender-2.66-testbuild1-linux-glibc211-x86_64:
works
however
blender-2.66-testbuild1-linux-glibc211-i686: (yes, on a 64-bit system)
yields empty image and
CUDA error: Launch failed in cuCtxSynchronize()
CUDA error: Launch failed in cuMemcpyDtoH((uchar*)mem.data_pointer + offset, (CUdeviceptr)((uchar*)mem.device_pointer + offset), size)
CUDA error: Launch failed in cuMemFree(cuda_device_ptr(mem.device_pointer))
CUDA error: Launch failed in cuMemFree(cuda_device_ptr(mem.device_pointer))
CUDA error: Launch failed in cuMemAlloc(&device_pointer, size)
<lots of these lines>
CUDA error: Launch failed in cuMemAlloc(&device_pointer, size)
CUDA error: Launch failed in cuMemFree(cuda_device_ptr(mem.device_pointer))
<lots of these lines>
CUDA error: Launch failed in cuMemFree(cuda_device_ptr(mem.device_pointer))
Blender 2.66 Testbuild1
GPU: Geforce GTX 660 Ti
Driver: 310.90
OS: Windows 7 x64
Status: works
Though what’s with the funny flashes of orange while the rendering is in progress? I’m guessing that’s a new way of highlighting the “currently being rendered” tile? Neato!
GPU ; 580GTX
Driver : 306.97 (Had to revert from 310.xx)
OS : Win 7, x64
Status : This time, it works.
Had many of cuCtxSynchronize error messages before
I really think the download files must be named “linux_32bit” “linux_64bit” instead what they are named just now, that glib and that i686 or x86 thing… The same in the buildbot and release files.