OTOY Forums

aqcoelho wrote:Yes now is working fine, with the updated C4D.. Thanks!

i did not expected that. strange!

IOn OSX - the Color Shader issue is coming up here too. This is with R16 and the latest update to 16.050.
Putting a color shader into the texture slot of the emission and starting the render causes an immediate crash.

joeycamacho wrote:IOn OSX - the Color Shader issue is coming up here too. This is with R16 and the latest update to 16.050.
Putting a color shader into the texture slot of the emission and starting the render causes an immediate crash.

Ok thx. Where is bugreport.zip?

Any words about latest feature(automatic mode) from guys?

aoktar wrote: Any words about latest feature(automatic mode) from guys?

what can i say ?!
It's just brilliant ! Tested on light and heavy scenes .

If only the voxelization process was so lightning fast like your plugin

uncia wrote:

aoktar wrote: Any words about latest feature(automatic mode) from guys?

what can i say ?!
It's just brilliant ! Tested on light and heavy scenes .

If only the voxelization process was so lightning fast like your plugin

Great to hear, thanks uncia. I'll try to make it better on next version. I wish to provide a full render session without closing/pausing/resending while working on big scenes. Regarding to voxelling or compilation of geos, that's our big headache. I hope a faster process one day.

I know that you have a long list to do but just wanted to remind
Could you please fix function in live viewer "Show in Picture viewer" ?
Really handy feature but now it's broken.

Have massive problems with freezing of the whole computer (about 10 times in 3h), using C4D 16.05 and RC4, RC1 was also. When not freezing, Cinema shuts down. Seems to depend on huge amount of clones and also cloner. No bugreports, because of the feeze and/or shutdown no log files. Last sentence to read is always "scene was sent in .. seconds", Octane Live Viewer mostly starts to render some seconds and then *bam*
Deactivating the draw pipeline wich switches all generators off won't show any clones in Live Viewer, renders faster but also seems to have an issue because of camera movements/rotations will lack first and probably shutdown Cinema also later on.

Someone else? Didn't read the whole thread.

Edit: and I get a pin error like below, but can't find the lonely RGB node in the material. Before that, there where two similary pin errors. One with also an RGB node but all nodes "unknown" and one with an Absorption Medium (connected to an absorption pin, yes) wich is fed by an RGB Specctrum node. It worked and colored the absorption but lead to nearly the same error.

dinf wrote:...

Just post that *bam* scene on forum

dinf wrote:Have massive problems with freezing of the whole computer (about 10 times in 3h), using C4D 16.05 and RC4, RC1 was also. When not freezing, Cinema shuts down. Seems to depend on huge amount of clones and also cloner. No bugreports, because of the feeze and/or shutdown no log files. Last sentence to read is always "scene was sent in .. seconds", Octane Live Viewer mostly starts to render some seconds and then *bam*
Deactivating the draw pipeline wich switches all generators off won't show any clones in Live Viewer, renders faster but also seems to have an issue because of camera movements/rotations will lack first and probably shutdown Cinema also later on.

Someone else? Didn't read the whole thread.

Edit: and I get a pin error like below, but can't find the lonely RGB node in the material. Before that, there where two similary pin errors. One with also an RGB node but all nodes "unknown" and one with an Absorption Medium (connected to an absorption pin, yes) wich is fed by an RGB Specctrum node. It worked and colored the absorption but lead to nearly the same error.

Code: Select all

Tried to access null node pin
Can't connect node 'RGB color' ...

I can't see any problem on scene. It pretty small scene to cause crashes, etc.. You may think to check your drivers,hw,etc...

Thanks alot for your fast response. Seemed to be the driver, hopefully.

These pin errors, do they have any effect? Where do they come from?
It sounds to me like there is a node somewhere I can't find and remove or reconnect.