C4D animations on ORC
Moderators: ChrisHekman, aoktar
Quick question: Is it possible to render C4D animations on ORC without converting the scene to the Standalone version? Like simply clicking "render on ORC" in C4D instead of the picture viewer?
Workstation: Watercooled 4x GTX 780, 1500W Corsair AX1500i PSU, 4930K, 32 GB RAM, SSD and Cinema4D.
Render slave: 4X GTX 780 Asus Strix 6GB, 1200W Corsair AX1200i PSU
Render slave: 4X GTX 780 Asus Strix 6GB, 1200W Corsair AX1200i PSU
No! It's working like exporting fbx/abc files.schodt wrote:Quick question: Is it possible to render C4D animations on ORC without converting the scene to the Standalone version? Like simply clicking "render on ORC" in C4D instead of the picture viewer?
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
Too bad
Is this on the roadmap? Would be a welcome feature to have in the C4D plugin!

Workstation: Watercooled 4x GTX 780, 1500W Corsair AX1500i PSU, 4930K, 32 GB RAM, SSD and Cinema4D.
Render slave: 4X GTX 780 Asus Strix 6GB, 1200W Corsair AX1200i PSU
Render slave: 4X GTX 780 Asus Strix 6GB, 1200W Corsair AX1200i PSU
It's not practically possible to send every frames as different files over internet and get back. Files are very big and lost of time. This is not how it's designed. How do you imagine a feature like that?schodt wrote:Too badIs this on the roadmap? Would be a welcome feature to have in the C4D plugin!
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
I was thinking of functionality similar as to how Rebusfarm works. It basically makes a "Save project with Assets", and then renders out to a folder named "Render" inside the project. It's really smooth and easy to use. I'm sure if the C4D Octane plugin had this functionality, that the ORC would be used a lot more by C4D users, than now.
Workstation: Watercooled 4x GTX 780, 1500W Corsair AX1500i PSU, 4930K, 32 GB RAM, SSD and Cinema4D.
Render slave: 4X GTX 780 Asus Strix 6GB, 1200W Corsair AX1200i PSU
Render slave: 4X GTX 780 Asus Strix 6GB, 1200W Corsair AX1200i PSU
Part of how we will address this in 3.1 is by optimizing ORBX packages. We will start by having procedural textures no longer baked, since we have OSL. We have also added bones/skinning directly in Octane (ORBX will support glTF as interchange, which is much more compact than FBX, and way smaller than ABC). Beyond 3.1 ORBX improvements, we may also look into building C4D native support into ORC, but we would need to do this after 3.1 anyway.
+1 essential to be able to send my c4d project instead of exporting it to some other format (complex scenes with vdbs/tfd/particles/hair etc)
Other than size, is there anything that isn't working in the export process? One option we could help with is allowing you to run a remote PC on AWS install your own C4D+Octane (that is what the floating licence is for w./ ORC) and then export to ORC from there super fast - assuming that the connection is the bottleneck?thanulee wrote:+1 essential to be able to send my c4d project instead of exporting it to some other format (complex scenes with vdbs/tfd/particles/hair etc)
THAT is an intriguing idea...
CaseLabs Mercury S8 / ASUS Z10PE-D8 WS / Crucial 64GB 2133 DDR4 / 2 XEON E5-2687W v3 3.1 GHz / EVGA 1600 P2 / 2 EVGA RTX 2080Ti FTW3 Hybrid/ Cinema 4D
Is it fast? Oh, yeah!
Is it fast? Oh, yeah!