Page 5 of 10

Re: Version 2.23.1 - RC2 (Updated on 01.05.15)

Posted: Sat May 02, 2015 5:58 pm
by Ron
Using the node editor causes a weird behavior from time to time. See attached screenshot: sometimes one node like eg. FloatTex or ImageTexture is displayed infinite times.
It produces the same node whenever you drag it away.
Node Editor Bug.jpg

Re: Version 2.23.1 - RC2 (Updated on 01.05.15)

Posted: Sat May 02, 2015 6:06 pm
by aoktar
Ron wrote:Using the node editor causes a weird behavior from time to time. See attached screenshot: sometimes one node like eg. FloatTex or ImageTexture is displayed infinite times.
It produces the same node whenever you drag it away.
Node Editor Bug.jpg
they should come from old scenes. There was a problem on embedded floattexture creations. Ex. floattexture in emissions. You can delete this leaked nodes. Any unconnected node is leaked.

Re: Version 2.23.1 - RC2 (Updated on 01.05.15)

Posted: Sat May 02, 2015 6:40 pm
by Ron
aoktar wrote:
they should come from old scenes. There was a problem on embedded floattexture creations. Ex. floattexture in emissions. You can delete this leaked nodes. Any unconnected node is leaked.
OK - but deleting leaked nodes crashes C4D immediately.

:-(

EDIT: deleting any node crashes C4D in all materials :-((

Re: Version 2.23.1 - RC2 (Updated on 01.05.15)

Posted: Sat May 02, 2015 7:07 pm
by sadece
Ron wrote:
aoktar wrote: but deleting leaked nodes crashes C4D immediately.
i agree with that. same here.

Re: Version 2.23.1 - RC2 (Updated on 01.05.15)

Posted: Sat May 02, 2015 7:37 pm
by aoktar
Ron wrote:
aoktar wrote:
they should come from old scenes. There was a problem on embedded floattexture creations. Ex. floattexture in emissions. You can delete this leaked nodes. Any unconnected node is leaked.
OK - but deleting leaked nodes crashes C4D immediately.

:-(

EDIT: deleting any node crashes C4D in all materials :-((
EDIT: Ok! I have found the problem. That's again a mistake on my side. I'll publish RC3, i hope that can be last fix.

EDIT EDIT: Could it be possible to test this immediate version for nodegraph. It's looking good here
http://render.otoy.com/customerdownload ... C3-win.zip

Re: Version 2.23.1 - RC2 (Updated on 01.05.15)

Posted: Sun May 03, 2015 1:54 pm
by cfrank78
I will try it!

Edit: Tryed 30 min. Here it is working now as it should!

Re: Version 2.23.1 - RC3 (Updated on 03.05.15)

Posted: Sun May 03, 2015 6:28 pm
by Ron
Tested RC3 and its looking good.
Thanks for your fixing this so quick!

Ron

Re: Version 2.23.1 - RC2 (Updated on 01.05.15)

Posted: Sun May 03, 2015 7:01 pm
by aoktar
cfrank78 wrote:I will try it!

Edit: Tryed 30 min. Here it is working now as it should!
thanks.
Ron wrote:Tested RC3 and its looking good.
Thanks for your fixing this so quick!

Ron
Enjoy it.

Bugreport: Relative Server Paths in IES lights

Posted: Mon May 04, 2015 10:15 am
by fuelnewmedia
Hi aoktar,

When we tried to render with Octane on our small render farm using CGRU, the following minor bug appeared:

Setup:
Rendering with several clients from one ressource folder on a server

Bug Desciption:
IES files with relative file paths not found

Solution:
IES lights must have absolute file paths

Best regards & thx for your great work!
Paul

Re: Version 2.23.1 - RC2 (Updated on 01.05.15)

Posted: Mon May 04, 2015 7:50 pm
by Weirdpictures
aoktar wrote:
Weirdpictures wrote:Hey Ahmet,

thanks for quick reply. We did not know that send all scene data erases all objects. Sometimes we are using send all scene data in order to get a still shot without any motion to render multiple frames with different grain, otherwise Octane renders one frame in a non changing animation and then just copies the file after 2 frames. Is there any other way to force octane to render every frame in a still animation, so that we can use it with moving grain?

Thanks
Pfff.. You missed the all worklow logic of plugin. We have a bunch of new tutorials about secrets and usages of plugin. It's far better than lot of explanations. Please see them on first page...

Hey Ahmet,

thanks for the tip :-) We actually did know about all the tricks in the videos (and we watched them all through and they are a great resource.) We did render images now with the update only resend objects and yes, now the object tags and render layers work, but when rendering with the render layer masks enabled we encountered some weird effect. If we turn on the object layer masks, the first image rendered into PV shows up with the correct gamma, but every following frame drops gamma and renders darker. We tested rendering the same scene without the render layer make output and it renders all frames in correct gamma.
Is that again something we are missing and need to change in our settings or a bug?

Thanks