Page 13 of 19
Re: Version 3.04.3-R1 (11.11.2016) - Latest stable
Posted: Wed Nov 23, 2016 8:45 am
by KonstantinosD
Hello Ahmet,
I don't remember if that was always the case with previous versions but when i render a picture to the live viewer and send it to the picture viewer of C4D, it sends it as an 8bit picture. Is it possible to send the 32 bit tonemapped as we see it in the live viewer? It would be better for quick editing with curves etc.
Thanx,
Konstantinos
Re: Version 3.04.3-R1 (11.11.2016) - Latest stable
Posted: Wed Nov 23, 2016 6:06 pm
by aggiechase37
So question: If I need to make a large volume object, and the voxel sizes can only be so big, what options do I have? Can we not have a release that would use larger voxel sizes? Or is there another way?
Re: Version 3.04.3-R1 (11.11.2016) - Latest stable
Posted: Wed Nov 23, 2016 7:09 pm
by aoktar
aggiechase37 wrote: Can we not have a release that would use larger voxel sizes? Or is there another way?
No! Do more practice to detect limits.
Use less voxel counts.
Divide your volume to small parts
Use external VDB.
Re: Version 3.04.3-R1 (11.11.2016) - Latest stable
Posted: Fri Nov 25, 2016 1:50 am
by aggiechase37
So, I could throw volume object into a cloner and render instances? Or octane scatter?
Re: Version 3.04.3-R1 (11.11.2016) - Latest stable
Posted: Fri Nov 25, 2016 5:44 pm
by Ron
aoktar wrote:Ron wrote:Hi Ahmet,
since a couple of days I get crashes of c4d when rendering a particular scene in PV. First it starts normally but after a couple of moments it freezes C4D. In LV it's rendering fine.
I tried this scene without materials and it worked well. So I guess one of my mats is corrupted or in any case the reason for crashing Octane.
How can I find out this material? Hop the bug report helps. See attached.
I am using the latest version of SA and Plugin, latest C4D R18.
Cheers - Ron
_BugReport.zip
It seems as a crash on plugin side. You can see in picture. But not possible to know where it from comes. You can find reason. Delete some materials until crashes disappear. You may need to try several combinations until find. Make a version of your scene with crash of source. And send me if you can.
Hi Ahmet,
after lots of investigation I found the reason for the constant crashing of this particular scene. At the end it had nothing to do with materials but with C4D render settings: at some point of the creation process I must have accidentally changed "Field Rendering" in Output Tab to something else than "None". That caused a crash always at the very end of the rendering.
Shit happens sometimes.
Just wanted to let you know.
Cheers - Ron
Re: Version 3.04.5 (26.11.2016) - Latest stable
Posted: Fri Nov 25, 2016 10:40 pm
by aoktar
New build(3.04.5) is compiled with experimental vertex weights support. OSX version has been preparing...
Re: Version 3.04.5 (26.11.2016) - Latest stable
Posted: Sat Nov 26, 2016 2:28 am
by eyeonestudio
Finally..... Thanks...
Re: Version 3.04.5 (26.11.2016) - Latest stable
Posted: Sat Nov 26, 2016 6:34 pm
by Terryvfx
Wow I will try the vertex options right away! I bet the other plugins' users are jealous of this haha! Thanks you for implementing this
Re: Version 3.04.5 (26.11.2016) - Latest stable
Posted: Mon Nov 28, 2016 11:14 am
by moebius
You will now work further on the Node Editor?
Re: Version 3.04.5 (26.11.2016) - Latest stable
Posted: Mon Nov 28, 2016 4:37 pm
by alexchopjian
Regarding "Version 3.04.5 (26.11.2016) - Latest stable" for R18, I was initially having issues getting it to work. Looks like the R18.cdl64 doesn't work with R18. I deleted the R18.cdl64 out of the c4doctane folder and left the R17.cdl64 and it worked. Not sure if this is a bug or if I'll experience any issues down the road, but I thought I'd address this if any one else hasn't.