Page 3 of 6
Re: integrated Octane for Cinema Beta
Posted: Sun Mar 24, 2013 4:37 pm
by Jaybee
aoktar wrote:
hmm, this is important feature which is missing. Thanks you for pointing this.
previews is limited with lonely ball rightnow. we want to be improved this. But need time, but you can think so. this is realtime renderer you don't need to look to preview balls while doing adjusment
Haha

I just like to see a picture in my library of materials. Sometimes it's easier to browse through previews than having to read about a material called "pine_wooden_planks_with_bump_and_dirt"
The basic ball would be fine. Just a picture so I know what I'm looking at in the Content Browser as I'm starting to try and build my library of Octane C4D materials with my favourite textures and remake stuff I had on the standalone version.
Re: integrated Octane for Cinema Beta
Posted: Sun Mar 24, 2013 6:12 pm
by nehale
is the voxelation process faster in the integrated plugin or its the same speed as the exporter?
Re: integrated Octane for Cinema Beta
Posted: Sun Mar 24, 2013 6:14 pm
by aoktar
nehale wrote:is the voxelation process faster in the integrated plugin or its the same speed as the exporter?
voxelizing is done by Octane Render part. Plugin use sdk 1.11b. So that's very similar.
Why?
Re: integrated Octane for Cinema Beta
Posted: Sun Mar 24, 2013 6:35 pm
by nehale
aoktar wrote:nehale wrote:is the voxelation process faster in the integrated plugin or its the same speed as the exporter?
voxelizing is done by Octane Render part. Plugin use sdk 1.11b. So that's very similar.
Why?
I'm rendering an animation now with c4d and the exporter, the scene take up 900mb of vram, rendertime is 10-17sec but translation/voxelising takes almost 30-40secs per frame just to transfer the files and textures to the graphics cards, I wanted to know if this translating of materials and geometry is faster in the integrated version or just the same speed?
Thanks
Re: integrated Octane for Cinema Beta
Posted: Sun Mar 24, 2013 6:52 pm
by aoktar
Only voxel time is similar, except this integrated much faster in total process (run standalone/export/voxel/import...)
Also you can run multiply instances of C4D for animation rendering. I'm using this method sometimes. And you can split to 2 or more part your sequence on different Cinema 4d instances. So pratically you can lower the export process time to ZERO.
Also plugin has preview maker which can do only camera flytroughs. Also Instancing can give much more lower export times.
Re: integrated Octane for Cinema Beta
Posted: Sun Mar 24, 2013 7:07 pm
by nehale
aoktar wrote:Only voxel time is similar, except this integrated much faster in total process (run standalone/export/voxel/import...)
Also you can run multiply instances of C4D for animation rendering. I'm using this method sometimes. And you can split to 2 or more part your sequence on different Cinema 4d instances. So pratically you can lower the export process time to ZERO.
Also plugin has preview maker which can do only camera flytroughs. Also Instancing can give much more lower export times.
Does this mean that i can run multiple c4d's with one licence or will i need to buy C4D licences for each instance, also can i use them with only one Stand Alone licence or will need another for each pc?
Re: integrated Octane for Cinema Beta
Posted: Sun Mar 24, 2013 7:20 pm
by aoktar
nehale wrote:aoktar wrote:Only voxel time is similar, except this integrated much faster in total process (run standalone/export/voxel/import...)
Also you can run multiply instances of C4D for animation rendering. I'm using this method sometimes. And you can split to 2 or more part your sequence on different Cinema 4d instances. So pratically you can lower the export process time to ZERO.
Also plugin has preview maker which can do only camera flytroughs. Also Instancing can give much more lower export times.
Does this mean that i can run multiple c4d's with one licence or will i need to buy C4D licences for each instance, also can i use them with only one Stand Alone licence or will need another for each pc?
You can't run same time on different machines. Only i say that:
You can open multiply Cinema4d and you can do multiply renderings on same machine. This provides you one instance export, other render. So you can use %100 gpu power.
Note: You must check memory usage of gpu's so how much simultaneous rendering fit your gpu's
Re: integrated Octane for Cinema Beta
Posted: Sun Mar 24, 2013 7:30 pm
by nehale
aoktar wrote:nehale wrote:aoktar wrote:Only voxel time is similar, except this integrated much faster in total process (run standalone/export/voxel/import...)
Also you can run multiply instances of C4D for animation rendering. I'm using this method sometimes. And you can split to 2 or more part your sequence on different Cinema 4d instances. So pratically you can lower the export process time to ZERO.
Also plugin has preview maker which can do only camera flytroughs. Also Instancing can give much more lower export times.
Does this mean that i can run multiple c4d's with one licence or will i need to buy C4D licences for each instance, also can i use them with only one Stand Alone licence or will need another for each pc?
You can't run same time on different machines. Only i say that:
You can open multiply Cinema4d and you can do multiply renderings on same machine. This provides you one instance export, other render. So you can use %100 gpu power.
Note: You must check memory usage of gpu's so how much simultaneous rendering fit your gpu's
That's sounds awesome!, can you do a tutorial showing just that?
Re: integrated Octane for Cinema Beta
Posted: Sun Mar 24, 2013 7:39 pm
by aoktar
nehale wrote:
That's sounds awesome!, can you do a tutorial showing just that?
if you have integrated plugin it's easy.
you must open multiple Cinema4d.exe with -parallel parameters.
In render setting set output frames to different ranges. Of course you must select Octanerender for render engine.
An start render on each copy of c4d.
Re: integrated Octane for Cinema Beta
Posted: Sun Mar 24, 2013 7:58 pm
by mauricesteenbergen
aoktar wrote:
if you have integrated plugin it's easy.
you must open multiple Cinema4d.exe with -parallel parameters.
In render setting set output frames to different ranges. Of course you must select Octanerender for render engine.
An start render on each copy of c4d.
Great tip Aoktar, have been searching on how to open multiple C4D instances on one machine.
I found another bug: if you work with the preview window for a while, and you decide to render a full frame with the renderer (shift+r), the preview size has changed after that.
I would like to thank you for your hard work on the plugin, I just bought it and I already love it. I got used to the standalone, but it's so much easier this way. I'm sure you'll get rid of the bugs soon, It's been running pretty good here up until now.