OTOY Forums

I'm having a problem with the remote slave not connecting when I try to render using the commandline version of C4D R18 or R19. This worked flawlessly in 3.06.2, but has been broken since these new 3.07 versions came out.

The remote slave station (2-gpus) works fine within C4D and remains active during the session. If I export to an animated .orbx file, I can use both systems to render and all gpus remain active and bound.

But if I try to use the "path to C4d commandline.exe" -render "path to c4d project" to render, the slave system simply won't come online to render. The daemon just sits there, and there is no activity on the gpus.

So I have a workaround using the standlone Octane for now, but I have used the commandline version of C4D for almost a year now with Octane and both systems have rendered fine. This is my preferred way to work and why I am bringing it up. Thanks.

alchu wrote:Hey Aoktar!

Is it possible the Node Editor: Solo mode for textures- feature update has a bug that does not let me un-solo a texture? And does the texture need to be connected to a port on the shader in order to be able to solo it?

Thank you very much in advanced, and thanks for everything you've done so far!

Attached a video to show how it should be. Where's bug?

BCres wrote:I'm having a problem with the remote slave not connecting when I try to render using the commandline version of C4D R18 or R19. This worked flawlessly in 3.06.2, but has been broken since these new 3.07 versions came out.

The remote slave station (2-gpus) works fine within C4D and remains active during the session. If I export to an animated .orbx file, I can use both systems to render and all gpus remain active and bound.

But if I try to use the "path to C4d commandline.exe" -render "path to c4d project" to render, the slave system simply won't come online to render. The daemon just sits there, and there is no activity on the gpus.

So I have a workaround using the standlone Octane for now, but I have used the commandline version of C4D for almost a year now with Octane and both systems have rendered fine. This is my preferred way to work and why I am bringing it up. Thanks.

That's true as i can see. I think there's a change in sdk to hold the saved slaves. I'll add some extra parameters to bind_all or select deamons from render settings interface.

Thanks, aoktar. The standalone is working fine in the meantime—still rendering an animation I started last night with no problems.

Thanks for all the hard work thus far, aoktar. I'm having trouble getting octane working. I installed this version (3.07 - Test6a) with the respective standalone version and I keep getting the error - "There is no CUDA device which is supported by Octane Render..." My specs are below:

Cinema 4D r16 (newest version)
iMac (Late 2013)
macOS High Sierra
NVIDIA GeForce GTX 775M 2 GB
CUDA Driver Version: 9.0.197
OctaneRender 3.06.4 Standalone

Can you help me with this?

Hello everybody,

I can't find LiveDB anymore. What happened to it?
Win on R18.

Thanks

albatetra wrote:Hello everybody,

I can't find LiveDB anymore. What happened to it?
Win on R18.

Thanks

Where to do you look and could you be more clear? What do you mean with "can't find it"?

Ahmet, thank you for this last update, the new instance id is so powerful, works perfect with X-Particles! Do you have plans to do the same with RealFlow for C4D particles?

Domenico

Domenicozzo wrote:Ahmet, thank you for this last update, the new instance id is so powerful, works perfect with X-Particles! Do you have plans to do the same with RealFlow for C4D particles?

Domenico

It's not possible without having a proper api for RF. I'll do it when they offer that.

Got it. Keep up the great work!

Domenico