Page 26 of 31
Re: Beta 0.72 / 0.79 (SDK 1.20)
Posted: Sun Sep 01, 2013 10:31 pm
by aoktar
krzychuc4d wrote:Hi Aoktar,
This update works fine for me,
mesh update is very quick and responsive. Thanks!
So far I found only one small bug .
When I started octane viewer and did some rendering
I've changed cinema 4d scheme from light to dark
after that Cinema has crashed.
Another small thing.
Why Object tag needs to be set to 1 ?
In my opinion by default it should work even with 0
one more question
how can I set Subsampling 2x2 or 4x4 in Live Viewer ?
You can expect some improvements on updating algoritms.
Number 0 means static geometry. So removing a objecttag or changing the mesh number to 0 has same result.
i'll test for crash. subsampling has not yet any effect on sdk.
Re: Beta 0.72 / 0.79 (SDK 1.20)
Posted: Mon Sep 02, 2013 7:58 am
by Andygp
I have a Problem with Navie“(dpit effex2) The Gas renderer is crashing with Octane Plugin at the Plugin Folder, without it goes.
Re: Beta 0.72 / 0.79 (SDK 1.20)
Posted: Mon Sep 02, 2013 8:47 am
by indexofrefraction
just had a strange bug with 0.72 mac :
i build half a house (medium complex hierarchy) with some materials
then mirrored the whole group with a symmetry object
boom -> all materials are white now
if i turn off the symmetry object, all is ok again.
i circumvented this by making an instance of the whole group
then entering -1 in the z scale of the instance
but this shouldnt be i guess
Re: Beta 0.72 / 0.79 (SDK 1.20)
Posted: Mon Sep 02, 2013 10:23 am
by Subroutine49690
Andygp wrote:I have a Problem with Navie“(dpit effex2) The Gas renderer is crashing with Octane Plugin at the Plugin Folder, without it goes.
Hi Andygp,
I also use Depit-Effex. The Gas-Shader is only compartible to C4D-Advanced-Renderer...nothing else.
Even Vray can't read it...therfor exists a workaround using vray-volumetric-fog.
And since octane tries to bake the C4D-shaders before rendering, I understand it when a crash happens here.
Hope this was helpful.
Re: Beta 0.72 / 0.79 (SDK 1.20)
Posted: Mon Sep 02, 2013 10:34 am
by Andygp
i dont have the Plugin active, nothing to render
Re: Beta 0.72 / 0.79 (SDK 1.20)
Posted: Mon Sep 02, 2013 10:45 am
by areafilm
Hi! the node editor dont't work fine for me.. If I add an Image no there is not in the render..
Re: Beta 0.72 / 0.79 (SDK 1.20)
Posted: Mon Sep 02, 2013 1:33 pm
by indexofrefraction
ahmm... how the heck can you open the node editor ?
cant find how to access this in the mac version of 0.79
Re: Beta 0.72 / 0.79 (SDK 1.20)
Posted: Mon Sep 02, 2013 3:06 pm
by aoktar
Hi all,
i want to say about your reports, please try to be more specific on messages.
Octane node editor is disabled, because it was for viewing for devs. New Node editor is highly wip. Please score as is that.
I'm not aware about mirror problem but if it's render instance can be a problem with (-) negative scaling. Not sure octane is supporting this.
Re: Beta 0.72 / 0.79 (SDK 1.20)
Posted: Tue Sep 03, 2013 12:22 pm
by atome451
Hi all,
First, thanks a lot to aoktar for this new release with so much improvements!
Here some little bugs i've found:
TurbulenceTexture: Transform node doesn't work fine, rotation is very limited, scale only works in expansion on X & Z, but not contraction, and not at all on Y. Basic scale parameters doesn't work at all, Y is locked on minimal setting (texture is stretched on Y).
Checks: give curious results with default paramaters on a simple cube, not in black and white but with concentric lines in diagonal. Doesn't give the same result with a cube in Octane Render standalone.
Kernels: in pathtracing, the alphachannel is checked (or return to checked after changing the kernel) even if alphachannel isn't activated.
Help > Show gpu info: the relationship between values and GPUs aren't correct (EDIT:
the value on the HUD of octane view aren't correct too). By sample, I have 2 GPU 670 and 1 GPU 285 for the screen, the HUD gives 99% for one 670 and the 285, and 0% for the second 670. The devices are correctly configured in settings of course and performance is clearly in line with the parameters set.
Environment tag: If you activate the object "OctaneSky" and click on the tab "Environment Tag", it's impossible to add an ImageTexture. If you activate directly the tag itself, it works.
MixTexture: the "amount" float parameter is unstable, often the first time you click on it, it disappears.
I hope this little list will be usefull
EDIT: changes in
Help > Show gpu info
Re: Beta 0.72 / 0.79 (SDK 1.20)
Posted: Tue Sep 03, 2013 3:17 pm
by mate
Nice update. Node editor is very unstable, keeps crashing every other minute even with very simple setups.