OTOY Forums

Hi all,
I'm working on some bugs and optimisation for motion blur. Especially for render instances. Also added a new parameter to render settings. Time sampling per frames. This is for exporting sub calculations between two frames. To overcome some weird effects on big rotations. Default is 1.

A test version for R15 windows is here. Could someone test it please?
http://render.otoy.com/customerdownload ... 23-R15.zip
Please check the results. This show how effect the new parameter [/b]




Also some explanation for LV+mblur. It cannot be very accurate on some situations. Please read the manual for details. It's not production tool, only a previewer. And to get motion data is impossible for some situations. Motion blur calculation requires some frames which are depending to shutter settings. If plugin has missing motion keys, we can't see correct motion blur effect.
I wrote that in manual. Doing some timeline scrubbing step-by-step, it allows to filling caches. But jumping from frame 10 to 100 will broke the motion caching. So you will need to go frames 98,99,etc..

I see the 2.0 Cinema 4d Win version is released

When can we expect the release of the Mac OSX version?

Cheers

davidtorpey wrote:I see the 2.0 Cinema 4d Win version is released

When can we expect the release of the Mac OSX version?

Cheers

You can grab it from page one of this thread. That said, it has some issue for Mac. Clones don't all render and motion blur is pretty much broken.

SVITAdmin wrote:

davidtorpey wrote:I see the 2.0 Cinema 4d Win version is released

When can we expect the release of the Mac OSX version?

Cheers

You can grab it from page one of this thread. That said, it has some issue for Mac. Clones don't all render and motion blur is pretty much broken.

Yes, correct. Sdk has some problem, will look the solution.

Seems to fix the issue with 8 'sampleing per frames' on my system.

aoktar wrote:Hi all,
I'm working on some bugs and optimisation for motion blur. Especially for render instances. Also added a new parameter to render settings. Time sampling per frames. This is for exporting sub calculations between two frames. To overcome some weird effects on big rotations. Default is 1.

A test version for R15 windows is here. Could someone test it please?
http://render.otoy.com/customerdownload ... 23-R15.zip

fast_rotation_mblur.zip

Please check the results. This show how effect the new parameter

2014-06-20_142838.jpg

2014-06-20_141910.jpg

[/b]




Also some explanation for LV+mblur. It cannot be very accurate on some situations. Please read the manual for details. It's not production tool, only a previewer. And to get motion data is impossible for some situations. Motion blur calculation requires some frames which are depending to shutter settings. If plugin has missing motion keys, we can't see correct motion blur effect.
I wrote that in manual. Doing some timeline scrubbing step-by-step, it allows to filling caches. But jumping from frame 10 to 100 will broke the motion caching. So you will need to go frames 98,99,etc..

Render splines via hair +1

Hey Tkkim and bepeg4d,

Thanks for the specs.... Aside from the cards, I have the same specs except for C4d r14 (instead of 15) I wonder if I upgrade to 15 if that will help...
Basically it just crashes when I launch C4D r14 with just the 2.0 Octane plugin.... Aoktar is working on it (aside from other things) but we'll see.

Octane StandAlone 2.0 works fine and also C4D plugin 1.0. It's only 2.0 C4D plugin that fails for me. I want to slave my pc to the mac!!!

MacPro - 10.9.3
GTX 680 - Cuda Driver 6.0.46
Cinema r14.042 (build RC76788)
------------------------
PC - Win 7
4x GTX 780ti
Cinema r14.042 (build RC76788)

Hi Mingatu,

I did get "Error: Tried to start a dll more than once" on Opening C4D, then when I launch Octane, it crashes. What fixed it for me is deleting "c4dOctane-R13.dylib" and "c4dOctane-R14.dylib" from the plugins/Octaneblabla folder, so that Cinema cannot select a wrong version of Octane on startup. Everything fixed now, works like a charm, aside from the known Problems.

Im on a Mac Pro 5,1 OSX9,3 with GTX680 mac Edition. Cuda Driver is latest (released 20/5/2014)

...and C4D R15 obviously

Hey Johnteddy.

Thanks for the info. I did remove the r13 and r15.dylibs .... there may be something with the r14. I will try and upgrade to r15 and see if the problem still persists.


Thanks!

MINGATU wrote:Hey Johnteddy.

Thanks for the info. I did remove the r13 and r15.dylibs .... there may be something with the r14. I will try and upgrade to r15 and see if the problem still persists.


Thanks!

Hi,
i checked files. It works. But please wait until next release. I found a problem, Otoy guys will check it.