RhinoCycles does not render with CUDA - bug?

feklee · March 15, 2015, 2:06pm

When I render with CUDA enabled, then the render just stops, doing nothing:

Command: RhinoCycles_ListDevices
We have 2 devices
----------
	Device 0: CPU > Intel Core i3-2310M CPU @ 2.10GHz > 0 | False | True | False | CPU
	Device 1: CUDA_0 > NVS 4200M > 0 | False | True | False | CUDA
----------
Command: RhinoCycles_SetDebugOptions
Set Debug Options <100> ( use_cpu=CPU  use_bglight=NoBgLight  spotlight_factor=0.1  pointlight_factor=0.1  sunlight_factor=1  arealight_factor=1 ): use_cpu=CUDA
Command: Render
Processing light table
Processing geometry table
Using device CUDA_0 NVS 4200M
Rendering time: 0d 00h 00m 00s
Session 1
Session 1 start
Session 1 finished in 00:00:00.1880000
Slowest 0, fastest 0, average 0
Rendering stopped. The render window can be closed safely.

Version: Work In Progress (6.0.15062.11291, 3/3/2015) Beta

nathanletwory · March 15, 2015, 2:29pm

Could you paste the entire output from the command RhinoCycles_ShowDeviceCapabilities?

After you’ve run the command, press F2 and press the Copy All button, then paste the contents as reply here.

Thanks!

feklee · March 15, 2015, 2:52pm

Command: RhinoCycles_ShowDeviceCapabilities
The following capabilities have been found by Cycles:
----------
CPU device capabilities: SSE2 SSE3 SSE41 AVX
CUDA device capabilities:
	NVS 4200M
		CU_DEVICE_ATTRIBUTE_MAX_THREADS_PER_BLOCK			1024
		CU_DEVICE_ATTRIBUTE_MAX_BLOCK_DIM_X			1024
		CU_DEVICE_ATTRIBUTE_MAX_BLOCK_DIM_Y			1024
		CU_DEVICE_ATTRIBUTE_MAX_BLOCK_DIM_Z			64
		CU_DEVICE_ATTRIBUTE_MAX_GRID_DIM_X			65535
		CU_DEVICE_ATTRIBUTE_MAX_GRID_DIM_Y			65535
		CU_DEVICE_ATTRIBUTE_MAX_GRID_DIM_Z			65535
		CU_DEVICE_ATTRIBUTE_MAX_SHARED_MEMORY_PER_BLOCK			49152
		CU_DEVICE_ATTRIBUTE_SHARED_MEMORY_PER_BLOCK			49152
		CU_DEVICE_ATTRIBUTE_TOTAL_CONSTANT_MEMORY			65536
		CU_DEVICE_ATTRIBUTE_WARP_SIZE			32
		CU_DEVICE_ATTRIBUTE_MAX_PITCH			2147483647
		CU_DEVICE_ATTRIBUTE_MAX_REGISTERS_PER_BLOCK			32768
		CU_DEVICE_ATTRIBUTE_REGISTERS_PER_BLOCK			32768
		CU_DEVICE_ATTRIBUTE_CLOCK_RATE			1480000
		CU_DEVICE_ATTRIBUTE_TEXTURE_ALIGNMENT			512
		CU_DEVICE_ATTRIBUTE_GPU_OVERLAP			1
		CU_DEVICE_ATTRIBUTE_MULTIPROCESSOR_COUNT			1
		CU_DEVICE_ATTRIBUTE_KERNEL_EXEC_TIMEOUT			0
		CU_DEVICE_ATTRIBUTE_INTEGRATED			0
		CU_DEVICE_ATTRIBUTE_CAN_MAP_HOST_MEMORY			1
		CU_DEVICE_ATTRIBUTE_COMPUTE_MODE			0
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE1D_WIDTH			65536
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_WIDTH			65536
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_HEIGHT			65535
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE3D_WIDTH			2048
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE3D_HEIGHT			2048
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE3D_DEPTH			2048
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_LAYERED_WIDTH			16384
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_LAYERED_HEIGHT			16384
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_LAYERED_LAYERS			2048
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_ARRAY_WIDTH			16384
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_ARRAY_HEIGHT			16384
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_ARRAY_NUMSLICES			2048
		CU_DEVICE_ATTRIBUTE_SURFACE_ALIGNMENT			512
		CU_DEVICE_ATTRIBUTE_CONCURRENT_KERNELS			1
		CU_DEVICE_ATTRIBUTE_ECC_ENABLED			0
		CU_DEVICE_ATTRIBUTE_TCC_DRIVER			0
		CU_DEVICE_ATTRIBUTE_MEMORY_CLOCK_RATE			800000
		CU_DEVICE_ATTRIBUTE_GLOBAL_MEMORY_BUS_WIDTH			64
		CU_DEVICE_ATTRIBUTE_L2_CACHE_SIZE			65536
		CU_DEVICE_ATTRIBUTE_MAX_THREADS_PER_MULTIPROCESSOR			1536
		CU_DEVICE_ATTRIBUTE_ASYNC_ENGINE_COUNT			1
		CU_DEVICE_ATTRIBUTE_UNIFIED_ADDRESSING			1
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE1D_LAYERED_WIDTH			16384
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE1D_LAYERED_LAYERS			2048
		CU_DEVICE_ATTRIBUTE_CAN_TEX2D_GATHER			1
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_GATHER_WIDTH			16384
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_GATHER_HEIGHT			16384
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE3D_WIDTH_ALTERNATE			0
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE3D_HEIGHT_ALTERNATE			0
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE3D_DEPTH_ALTERNATE			0
		CU_DEVICE_ATTRIBUTE_TEXTURE_PITCH_ALIGNMENT			32
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURECUBEMAP_WIDTH			16384
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURECUBEMAP_LAYERED_WIDTH			16384
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURECUBEMAP_LAYERED_LAYERS			2046
		CU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE1D_WIDTH			65536
		CU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE2D_WIDTH			65536
		CU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE2D_HEIGHT			32768
		CU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE3D_WIDTH			65536
		CU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE3D_HEIGHT			32768
		CU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE3D_DEPTH			2048
		CU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE1D_LAYERED_WIDTH			65536
		CU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE1D_LAYERED_LAYERS			2048
		CU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE2D_LAYERED_WIDTH			65536
		CU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE2D_LAYERED_HEIGHT			32768
		CU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACE2D_LAYERED_LAYERS			2048
		CU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACECUBEMAP_WIDTH			32768
		CU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACECUBEMAP_LAYERED_WIDTH			32768
		CU_DEVICE_ATTRIBUTE_MAXIMUM_SURFACECUBEMAP_LAYERED_LAYERS			2046
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE1D_LINEAR_WIDTH			134217728
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_LINEAR_WIDTH			65000
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_LINEAR_HEIGHT			65000
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_LINEAR_PITCH			1048544
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_MIPMAPPED_WIDTH			16384
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE2D_MIPMAPPED_HEIGHT			16384
		CU_DEVICE_ATTRIBUTE_COMPUTE_CAPABILITY_MAJOR			2
		CU_DEVICE_ATTRIBUTE_COMPUTE_CAPABILITY_MINOR			1
		CU_DEVICE_ATTRIBUTE_MAXIMUM_TEXTURE1D_MIPMAPPED_WIDTH			16384
		CU_DEVICE_ATTRIBUTE_STREAM_PRIORITIES_SUPPORTED			0
		CU_DEVICE_ATTRIBUTE_GLOBAL_L1_CACHE_SUPPORTED			1
		CU_DEVICE_ATTRIBUTE_LOCAL_L1_CACHE_SUPPORTED			1
		CU_DEVICE_ATTRIBUTE_MAX_SHARED_MEMORY_PER_MULTIPROCESSOR			49152
		CU_DEVICE_ATTRIBUTE_MAX_REGISTERS_PER_MULTIPROCESSOR			32768
		CU_DEVICE_ATTRIBUTE_MANAGED_MEMORY			0
		CU_DEVICE_ATTRIBUTE_MULTI_GPU_BOARD			0
		CU_DEVICE_ATTRIBUTE_MULTI_GPU_BOARD_GROUP_ID			0
----------

nathanletwory · March 15, 2015, 3:19pm

Thanks. According your log the driver for your device should support CUDA 2.1. Some other error must be happening resulting in an early abort of the render.

Could you please run the tester program I posted in this thread, and attach the resulting log.txt here?

Thanks in advance.

feklee · March 15, 2015, 3:52pm

That cube gets rendered:

log.txt (37.2 KB)

nathanletwory · March 15, 2015, 4:34pm

Does a simple box with a basic material set to some color like red or green render in RhinoCycles?

feklee · March 15, 2015, 4:47pm

No, it (box.3dm) doesn’t:

With Rhino Render it renders fine:

nathanletwory · March 15, 2015, 6:20pm

Ok, well, there have been many changes, improvements and fixes since March 3rd. I hope upcoming Tuesday we see a new update to Rhino WIP released.

Until that you should be able to select the CPU as your rendering device with RhinoCycles using the RhinoCycles_SetDebugOptions command (toggle the use_cpu to CPU instead of CUDA).

norbert_geelen · March 20, 2015, 4:16pm

Hi Jester.

Do You still need more log files/pictures that your testprogram creates?
My computer does render a black window when using the gpu (nvidia geforce gtx 560ti) but does render correctly with cycles using the cpu.

Cheers, Norbert

feklee · March 20, 2015, 5:32pm

Just tried with 6.0.15076.10541, 3/17/2015, and CUDA powered rendering fails, just as before.

nathanletwory · March 22, 2015, 1:56pm

Not at the moment. I have my thinking hat on to come up with more ways to figure out why some cards fail. According specs I find on the internet your and feklees card should work. Perhaps more information about hardware setup might give some clues, but right now hard to say.

Information like operating system version, video card driver version, number of displays attached (and how, like VGA, DVI, etc), any special themes is use, etc.

Right now I’m busy with ironing out the last wrinkles of the changequeue integration (interactive rendering in separate window), but once that is in WIP trunk I can concentrate better on diagnosing this kind of errors.

I’ll ask in a new thread for more user help when I get to it!

FYI, I am daily testing and developing RhinoCycles on my NVidia GeForce GT 420, on of the lowest-end cards supported by Cycles (and thus RhinoCycles). This card has been working nicely (albeit a bit slow compared to the CPU in the same computer).

Ah bummer. Well, see above I will ask for user help soon

feklee · March 23, 2015, 9:45am

Let us know what you need! By the way, as I am on an Optimus system, I just checked what happens when I turn off integrated graphics in the BIOS: Same thing, no render. So that’s not it.

nathanletwory · March 23, 2015, 11:37am

[quote=“feklee, post:12, topic:17817”]By the way, as I am on an Optimus system, I just checked what happens when I turn off integrated graphics in the BIOS: Same thing, no render. So that’s not it.
[/quote]

One possible reason down, X to go

[quote=“feklee, post:12, topic:17817”]
Let us know what you need![/quote]

→

feklee · March 23, 2015, 12:56pm

Device: ThinkPad T420si 4174-E37
OS: Windows 7 Pro X64, clean install, i.e. not the Lenovo installation
Video card and driver:
Number of displays attached: only built-in monitor

Topic		Replies	Views
RhinoCycles: collecting available devices and render results Rendering WIP	32	2060	February 24, 2015
RhinoCycles CPU @ 100%, even when GPU is selected Rendering WIP	5	1339	October 22, 2015
RhinoCycles Serengeti (Rhino WIP)	10	413	January 29, 2015
Unable to set plug-in RhinoCycles as current render plug-in Serengeti (Rhino WIP)	6	878	July 1, 2016
Rhino 6 WIP > RhinoCycles Rendering WIP	17	2483	February 28, 2015

RhinoCycles does not render with CUDA - bug?

Related topics