Page 14 of 14

Re: Beta 0.68 (SDK 1.18 ) Updated on 21 June

Posted: Tue Jun 25, 2013 1:56 pm
by cfrank78
I have max and plugin, i have checked same scene which is similar results with your video. There is some reasons. Your version has not yet speed optimised due stability problems. It's not a quick process for me. Second can be each program has different scene graphs. Max is simplier than C4D. I don't think there is voxelling speed differents. Seems like fetching data lags. First way is to go with stability. But it needs deep diving to codes, so need to wait apporipate free time to do. If i have some process can ask you to help.
Thanks
Of course you can. Karba also sent me beta of beta of beta to test :lol: . Just PM me. We can also connect via Teamviewer,Skype or what you want!

Chris!

Re: Beta 0.68 (SDK 1.18 ) Updated on 21 June

Posted: Tue Jun 25, 2013 6:28 pm
by ribrahomedesign
Hi there.
I have purchased the plugin a view week ago and have tested it with big scenes and small ones
i am not sure what i have to think about it , i know its still in beta ,but its absolute not
usable the way it is at the moment ,materials are not updating properly ,renderings randomly slow down drastically,have to switch to clay render and back again to get up to speed again,my GPUs
are going absolutely mad now and then ,they sound like they are taking off any moment.and
then all those crashes all the time .I am absolutely sure aoktar is working very hard on it.
but this plugin needs some much more stability.it does not seem to me,that the last view updates have made any major improvements.
i can remember when the max plugin came out ,they where running and making images and animations in no time,what is still not possible with the c4d plugin.
i am sorry if i offend anybody
cheers
Rico

Re: Beta 0.68 (SDK 1.18 ) Updated on 21 June

Posted: Tue Jun 25, 2013 6:56 pm
by aoktar
ribrahomedesign wrote:Hi there.
I have purchased the plugin a view week ago and have tested it with big scenes and small ones
i am not sure what i have to think about it , i know its still in beta ,but its absolute not
usable the way it is at the moment ,materials are not updating properly ,renderings randomly slow down drastically,have to switch to clay render and back again to get up to speed again,my GPUs
are going absolutely mad now and then ,they sound like they are taking off any moment.and
then all those crashes all the time .I am absolutely sure aoktar is working very hard on it.
but this plugin needs some much more stability.it does not seem to me,that the last view updates have made any major improvements.
i can remember when the max plugin came out ,they where running and making images and animations in no time,what is still not possible with the c4d plugin.
i am sorry if i offend anybody
cheers
Rico
Are you using which version?

Re: Beta 0.68 (SDK 1.18 ) Updated on 21 June

Posted: Tue Jun 25, 2013 8:21 pm
by ribrahomedesign
i just uptated to the latest version because the problem with the slow rendering at some times
did drive me mad ,but with the latest version i have the same problem ,i really appreciate the
work you doing ,i am sometime a bit inpatient,
the problem with the material update ,is it normal that i have manually save all material
i use in the render ,in to the tex folder of my project folder?

Rico

Re: Beta 0.68 (SDK 1.18 ) Updated on 21 June

Posted: Tue Jun 25, 2013 9:05 pm
by aoktar
ribrahomedesign wrote:i just uptated to the latest version because the problem with the slow rendering at some times
did drive me mad ,but with the latest version i have the same problem ,i really appreciate the
work you doing ,i am sometime a bit inpatient,
the problem with the material update ,is it normal that i have manually save all material
i use in the render ,in to the tex folder of my project folder?

Rico
I did some revisions since sdk 1.17 because of new functionality problems. I advice to download always last one. I'm upload new release.
You may don't have to collect textures to project folder. You can use absolute paths or Octane texture paths parameters in setting window..
http://render.otoy.com/manuals/Cinema4D/?page_id=380

Also for your problems, sound come to me like some limitations of renderer. If you fill all gpu memory with triangles or textures then you can see slowdowns. Also if you use pathtracing or pmc will cause slowdown. I advice you do some small tests to known limits. If you have still problems give more info about workflow.

Importan note: Try with one gpu which is connected to monitor, let it free

Re: Beta 0.68 (SDK 1.18 ) Updated on 21 June

Posted: Tue Jun 25, 2013 9:33 pm
by NVN
my liveDB wont works?
normal?

i have the new version 0.68

Re: Beta 0.68 (SDK 1.18 ) Updated on 21 June

Posted: Tue Jun 25, 2013 9:34 pm
by NVN
sorry....now it works!
shame on me....

Re: Beta 0.68 (SDK 1.18 ) Updated on 21 June

Posted: Wed Jun 26, 2013 12:14 am
by ChrisVis
Hi aoktar,

did some more animation renderings with 0.6.8a and the picture manager renderer and still get random crashes after 50-100 frames with some projects. I disconnected one of my GTX590 and don`t got any bluescreens since that, need to do more testing to find out where the exact hardware problem is, hopefully its not the VRAM.

But for random crashes see this debug error crash message during animation rendering... don`t know what kind of failure this is, nor if it is caused by octane, maybe you have a clue?
DebugAssertionFailed.jpg
I also tried to rebuild the AreaLightTag problem by cutting down a complex scene I am working on (and where it occured) to make it a simple test scene, but after that the problem wasn`t there any more.
Or did you change something according to the OctaneLights since 0.6.7c and found a problem?
If not, maybe it just was some wired late night tired problem. :?

Thanx for your work,
ChrisVis

Re: Beta 0.68 (SDK 1.18 ) Updated on 21 June

Posted: Wed Jun 26, 2013 12:22 am
by aoktar
Hi Chrisvis and all,
i made important fix to get away this frustating error on renderings.
Please update from:


http://render.otoy.com/forum/viewtopic.php?f=30&t=33493


i have checked arelight problem but cannot found any problem.