OTOY Forums

Hi Oaktar

thanks for your answer!

Have been using the lastest Version for a couple of days now and its really very stable. Only 2 crashes where I´m not even sure its Octane related. So congrats again great release!

One little thing that might be related to the last Thing I have reported not updated position on instances:
When I kick "Clay Enable" mode everything works fine. Only Instances keep their material even when I reload the scene!
Just a minor thing and not really a big bug!

Finally one question:
Will the Node System be ready for the final release?

I don´t know if this is of interest to you but maybe you can team up with this guy. Seems like a pretty usable node solution!
http://www.cmstuff.com/

Cheers,
Raphael

oh I missed that!

perfect!

thanks
Mike

Hi Aoktar!

First thx for the motion blur! This render so fast and the results are great!
But i found 2 bugs.
First one is attached in the c4d. In mixtextures is a problem with the falloffmap. When i use the slider octane delete the falloffmap. Sometimes octane delete the Texture2 map.
For the second bug i will do a third test render this night and try to catch the log.
I have a big scene with a car on road. I have done serveral renderings in 720p and not one crash. But if i render the same scene in 1080p octane crashes a lot. But there is no rule for crashing...sometimes after 1hour.....or 6 hours. Maybe a memory leak?

Pixelkingdom wrote:Hi Aoktar!

First thx for the motion blur! This render so fast and the results are great!
But i found 2 bugs.
First one is attached in the c4d. In mixtextures is a problem with the falloffmap. When i use the slider octane delete the falloffmap. Sometimes octane delete the Texture2 map.
For the second bug i will do a third test render this night and try to catch the log.
I have a big scene with a car on road. I have done serveral renderings in 720p and not one crash. But if i render the same scene in 1080p octane crashes a lot. But there is no rule for crashing...sometimes after 1hour.....or 6 hours. Maybe a memory leak?

I don't think there is a big memory leak. If your scene need most of vram this can cause some problems with bigger buffers. Plugin has detection for render errors. can you check system memory and vram of gpu while rendering? Even texture usages and octane log window?

check scene but did'nt delete but will test again.

Silverwing wrote:Hi Oaktar

thanks for your answer!

Have been using the lastest Version for a couple of days now and its really very stable. Only 2 crashes where I´m not even sure its Octane related. So congrats again great release!

One little thing that might be related to the last Thing I have reported not updated position on instances:
When I kick "Clay Enable" mode everything works fine. Only Instances keep their material even when I reload the scene!
Just a minor thing and not really a big bug!

Finally one question:
Will the Node System be ready for the final release?

I don´t know if this is of interest to you but maybe you can team up with this guy. Seems like a pretty usable node solution!
http://www.cmstuff.com/

Cheers,
Raphael

For clay node: really need a fix for clay mode.
Not moving instance: i have some hardness on motion detection due of sdk. put under a null will be workaround for this. Next versions can have much better detection algoritms

need lot of work to make final version of node system. Anyway i don't want to remove this section for final release.
I know and checking cmnodes. But this not support octane materials and this is not provide good editing for octane nodes. Our editor will give much better editing when it's completed. This is my personal thought.

aoktar wrote:I know and checking cmnodes. But this not support octane materials and this is not provide good editing for octane nodes. Our editor will give much better editing when it's completed. This is my personal thought.

I tried cmNodes with Octane also these days. Worked well after copying the linked cmNodeShaders from a cinema standard material into an Octane mat, even when the cmNodes are linked to non-Octane shaders.
But since Octane has its own node based material system, this means to me only playing around with that.

Hi!
Masking objects with Cinema's object buffer not working when using PathTracing or PMC kernels (mask layer is black).
Mask layer work correct only using Directlighting.

update: now masking not work even with DL
Maybe this occur only with me?

@Rudi: it's not possible. This is Renderer limits. You can try more blurred images for better bumps.

How i make this?

Good job.
Hi. in beta 0.7.2B SDK 1.2 in cinema 14
you cannot use seamless texture in render
thanks

what does it mean (testing only) ?? is this why my account settings are't kept (need to activate after every restart) and the watermark is still there after activating?