OctaneRender® for Maya® 2.25 - 7.30 Win [STABLE V2]

[calus]

I am having a problem, because when you activate the movable proxy or resapeable proxy attribute for an object, the camera mapped texture does not work anymore, it only works when the object is in global

It was always like this,
camera mapped "feature" only works correctly with Global geometry type, making this functionality useless for advanced work.

When used with movable or reshapable proxy, it seems the camera mapped texture is projected in "local space" while it should use the "global space" coordinate...

Ironically the problem is reversed with projection nodes coordinate space,
textures are always projected in "global space" despite "local space" is selected.

For some reason Jimstar has never finished to implement this part, the same thing happened with 3DSmax plugin (exact same bugs).

[Refracty]

Calus, thanks for your hints and tips.
I have a problem with the Z-Depth. It is broken with newer scenes (value can not be changed).
I thought I could simply install the older plugin version 7.14 and render the Z-Depth there but the whole IPR turns black.
There must be some newer plug in information related to the ZDepth channel that the older version can not cope with.
Do you have any idea how I could render the Z-Depth in Octane4Maya?
Thank you

[calus]

Calus, thanks for your hints and tips.
I have a problem with the Z-Depth. It is broken with newer scenes (value can not be changed).
I thought I could simply install the older plugin version 7.14 and render the Z-Depth there but the whole IPR turns black.
There must be some newer plug in information related to the ZDepth channel that the older version can not cope with.
Do you have any idea how I could render the Z-Depth in Octane4Maya?
Thank you

Yes z-depth max of the z-depth pass is broken,
actually Jimstar introduced this bug in version 7.19.
I'm sure it's an easy fix but I don't know when/if V2 pluggin will be improved.

But you can still render Z-depth not using pass but with the Info channel Kernel,
z-depth max in this Kernel works

[abeoctane]

Thanks Calus, hope this is fixed soon because Its a very important feature for doing any compositing work with octane.

[calus]

Thanks Calus, hope this is fixed soon because Its a very important feature for doing any compositing work with octane.

But you can achieve the exact same result using an OctanePerspProjection node, with expressions or maya utility nodes.
Actually it's better than the "camera mapped" feature and works with all geometry type.

But it's a bit tricky.
I will post a script for that this week, in the Tutorial/help section, or a step by step description of how to do it.

[Refracty]

Hi Calus,
great hint that it will work via the info channels kernel !!!
Thank you

[christianP]

I've been trying to use this plugin. It crashes maya 2017 every time I fire it up. I'm running maya 2017 on window 8.1.
I have a titan X card.

[calus]

I've been trying to use this plugin. It crashes maya 2017 every time I fire it up. I'm running maya 2017 on window 8.1.
I have a titan X card.

What do you "fire up" ? are you talking about launching IPR or enabling Octane in plugin manager ?
do you use an old Titan X, or a brand new Pascal Titan X ?

[calus]

I am having a problem, because when you activate the movable proxy or resapeable proxy attribute for an object, the camera mapped texture does not work anymore, it only works when the object is in global, but I cant hide camera visibility or shadow visibílity in with a global attribute.

In the Help/tutorial section I posted a script to do the same thing as the "camera mapped" feature but with a perspProject node,
it works for all geometry type and with all image/procedural texture nodes:
viewtopic.php?f=126&t=56661

[abeoctane]

Hi calus, thank you very.