OTOY Forums

Plugin does not much things for network rendering. Only set that enabled/disabled. Be sure you are running same numbers of plugin and standalone on each daemons and master. Also i think standalone takes th control when you open it.

aoktar wrote:Be sure you are running same numbers of plugin and standalone on each daemons and master.

So each slave must use the same numbers as the master? Octane can only be active on one machine at a time. Each of my slaves are updated to the latest 2.02 both standalone and Plugin. I have noticed that cinema will sometimes disconnect a slave when you render to picture viewer. You then have to go back into the settings and enable the slave again for it to work.

This is how net rendering should work (This is an issue with standalone):

Once a slave of the same octane version is running the master should automatically see it and be available to render. (Exactly how Cinema's net render works, when a client is open its immediately displayed.) When a "daemon" or client is connected to a master it is then displayed as busy. When the render is finished the client should then be available to other masters.

that's it.

Client is online: Shows up in all octane standalone and plugin lists.
Client is busy: Still shows up in all octane standalone and plugin lists(but marked busy).

All of our standalones 2.02 see different clients at random. This is something I want to know why.

Another crash at the end of an animation render.

shawnfrueh wrote:Another crash at the end of an animation render.

FUSE_BugReport_001.zip

2.02?

yes 2.02

shawnfrueh wrote:yes 2.02

pls try with octane dialog and live viewer is closed and keep me informed, thanks

Hi Ahmet-

Here's another crash on save bug report for you. This is really cropping up a lot. Can you look into it? Version 2.02

Thanks


alec

ASyme1 wrote:Hi Ahmet-
Here's another crash on save bug report for you. This is really cropping up a lot. Can you look into it? Version 2.02
Thanks
alec

of course. But i need some more info about LV and octane dialog was open while getting this. Is it for Saving from Picture Viewer on last frame? All reports points the same place but i can't produce here. How is your scenes? Complex with many octane materials?

shawnfrueh wrote:

aoktar wrote:Be sure you are running same numbers of plugin and standalone on each daemons and master.

So each slave must use the same numbers as the master? Octane can only be active on one machine at a time. Each of my slaves are updated to the latest 2.02 both standalone and Plugin. I have noticed that cinema will sometimes disconnect a slave when you render to picture viewer. You then have to go back into the settings and enable the slave again for it to work.

What Ahmet was saying was that the Octane version of master (the C4D plugin) and slave have to match.

A slave computer can also be used as master. The only thing to remember is that there can be only 1 master on one computer at any time, because it will occupy the master socket port and a second master can't use that one anymore. So if you run Standalone with net rendering, the plugin can't do net rendering on the same computer and vice versa.

This is how net rendering should work (This is an issue with standalone):

Once a slave of the same octane version is running the master should automatically see it and be available to render. (Exactly how Cinema's net render works, when a client is open its immediately displayed.) When a "daemon" or client is connected to a master it is then displayed as busy. When the render is finished the client should then be available to other masters.

that's it.

Client is online: Shows up in all octane standalone and plugin lists.
Client is busy: Still shows up in all octane standalone and plugin lists(but marked busy).

All of our standalones 2.02 see different clients at random. This is something I want to know why.

I don't really get what you want, but the way how it's done right now is: You can have one master per computer, multiple masters in a network and each slave can be used only by one master at a time. That should work, if not, then there is a bug and needs to be fixed, in which case we would need a detailed explanation of the problem and how to reproduce it.

Hiya,

Version 2.01 and v 2.02
I don't know if it was already discussed but We're having problems with MatID and ObjectID channel.
We have a scene with a package and some cloners flying around. Mat ID changes once the cloners appear in the render (I believe they should stay the same).
Object ID keeps the same color for all cloners (each cloner has ~ 5 different objects)
I'd be nice to have a color option to set as MatID in the material and a color option to set as ObjectID in the Octane Object TAG.

Version 2.02
Randomly objects in cloners do not update while rendering sequence.
Also, MB (Motion Blur) Behaves strangely in LV, meaning it has rotation keys and deformation keys but it translates in Y.

Artur