Live viewer stops working

Tue Apr 21, 2015 3:30 pm

Having quite a few issues with Octane stopping working in Cinema 4D after a while. Usually after performing a main render to picture viewer. After that finishes the Live viewer refuses to update (clicked all the buttons, no dice). Have to restart Cinema.

Also getting lots of beach-balling when changing render settings in Cinema's Render options.

Its starting too feel more like a beta.

Tue Apr 21, 2015 3:41 pm

version number? Are you working via interface of Octane dialog or directly in Live Viewer?

Tue Apr 21, 2015 3:49 pm

aoktar wrote:version number? Are you working via interface of Octane dialog or directly in Live Viewer?

2.22.2 test3

Not sure what you mean regarding interface question?

Having another issue now, maybe related, where is fails to render to the PV. I have an out of memory error in the logs. Deactivating the GTX 980 solved that problem, so not sure what is going on. I checked in standalone and that can render on the 980 with no problems.

--------------------------- EXPORT LOG ---------------------------
Export materials time= 6072.602 ms
Collect objects time= 0.161 ms
Meshes creation time = 4.745 ms
Octane voxelization time = 0 ms
Sending to Octane engine time = 0 ms
CUDA error 2 on device 1: The API was unable to allocate enough memory to perform the requested operation.
-> failed to allocated device memory
Failed to allocate buffer for render passes
CUDA device 1: Failed to update info buffers
<<< Render Failure >>>
Total export Time = 6348.256 ms

Tue Apr 21, 2015 3:57 pm

I will not reply about "Beta". Are you using Octane Dialog to control the Live Viewer window?
You should check triangle counts and free VRAM amounts to avoid this CUDA errors.

Tue Apr 21, 2015 4:17 pm

aoktar wrote:I will not reply about "Beta". Are you using Octane Dialog to control the Live Viewer window?
You should check triangle counts and free VRAM amounts to avoid this CUDA errors.

I'm giving you my honest opinion as a customer Ahmet. There seem to be more bugs and glitches that I would like and they are starting to make me doubt it as a reliable proposition for my business. I'm using it on a very small job right now and its become a headache. There are always teething problems when learning new sw, and hardware in this case, so I'm willing to give it good go since when it does work it's incredible.

Anyway, nothing has changed in the scene apart from textures. The geometry is a single Bezier patch - there's virtually no geom in the scene. 3 textures that are big, one is 16bit at about 8k. 3 lights, and HDRI. That's it. Its reporting 763MB used.

The Octane Dialog... its a little confusing. Why is it duplicated in the LV and in a separate panel? I have it docked to the interface along with Settings and the Live Viewer. I usually use the buttons in the LV.

Tue Apr 21, 2015 4:38 pm

OK so I think the problems are all related, and caused by the plugin not wanting to use the 2nd cards. At least I can work around that for the time being by turning off the 980. But I have 2 cards so I can use two cards...

will try trashing the plugin and reinstalling

Tue Apr 21, 2015 5:04 pm

sdanaher wrote:OK so I think the problems are all related, and caused by the plugin not wanting to use the 2nd cards. At least I can work around that for the time being by turning off the 980. But I have 2 cards so I can use two cards...

will try trashing the plugin and reinstalling

i think you are missing why Cuda errors appear. This is not related with plugin or Octane, it's a issue about of triangle limits or insufficient vram.

Tue Apr 21, 2015 5:23 pm

aoktar wrote:
sdanaher wrote:OK so I think the problems are all related, and caused by the plugin not wanting to use the 2nd cards. At least I can work around that for the time being by turning off the 980. But I have 2 cards so I can use two cards...

will try trashing the plugin and reinstalling
i think you are missing why Cuda errors appear. This is not related with plugin or Octane, it's a issue about of triangle limits or insufficient vram.

Yes it's something to do with vram. I've junked the plugin and re-booted the machine. It now renders the same scene just fine. I think it's more likely the reboot that helped because Octane was reporting only 2.5GB of free vram on the 890 (it's not in use for anything else and no monitors are plugged in). After reboot its reported as having 3.7GB free vram. Something was steeling the vram.

But this doesn't explain why Standalone was able to render with the 980 while Cinema wasn't...

We'll have to see if the beachballing reappears as that doesn't seem related to rendering, its Cinema that is stalled.

Tue Apr 21, 2015 7:59 pm

Double check amount of free vram for big scenes. C4D uses some extra vram for opengl, standalone not.

Wed Apr 22, 2015 7:47 am

aoktar wrote:Double check amount of free vram for big scenes. C4D uses some extra vram for opengl, standalone not.

It wasn't a big scene, it was tiny geometry-wise. Does it have to load all textures in vram too?

It would be useful to be able to render the scene in Standalone and quite Cinema for cases where time and vram are in short supply. I haven't test if this is reliable yet.