OTOY Forums

BK wrote:

itsallgoode9 wrote:Will there be any bug fixes to the current version during the next couple months that the refactoring is taking place? or are we stuck with any existing bugs of the current version for a few months, until the refactored version gets released?

There are no bug fixes for the current version but they are all logged on our tracking system. We planned to focus 100% on refactoring which will help us to finish it ASAP, unless there is any major bug report.

Cool, that's understandable. I was just curious so we would know what to expect in the coming months.

itsallgoode9 wrote:

BK wrote:

itsallgoode9 wrote:Will there be any bug fixes to the current version during the next couple months that the refactoring is taking place? or are we stuck with any existing bugs of the current version for a few months, until the refactored version gets released?

There are no bug fixes for the current version but they are all logged on our tracking system. We planned to focus 100% on refactoring which will help us to finish it ASAP, unless there is any major bug report.

Cool, that's understandable. I was just curious so we would know what to expect in the coming months.

Hi Itsallgoode9,

Thank you so much. We will let you know with further updates.

I know you're working on the refactored plugin but can you please issue a new release with the render region fixed? That is something that was not broken, which you guys broke and now it's becoming a huge pain in the ass. This is something we should not be forced to endure for the next MONTHS, considering it was a dev introduced bug.

itsallgoode9 wrote:I know you're working on the refactored plugin but can you please issue a new release with the render region fixed? That is something that was not broken, which you guys broke and now it's becoming a huge pain in the ass. This is something we should not be forced to endure for the next MONTHS, considering it was a dev introduced bug.

hey Itsallgoode9,

While we are taking a look it.. please leave the "Use Pick Focus region" unchecked on all the camera when working with render region. The IPR window must be closed or re render the IPR if you decide to change the render camera.

Hi Guys,

Please we need a quick fix on the plug, basically sometimes we want just hide the mesh and not being loading on the GPU this plug if we set global and visibility off doesn't work anymore, I understand when we have movable or reshapable for some animation is good to load so Octane load on frame one all scene when we hide and show.

Our problem is some scenes we want Octane to not export the only solution is delete the mesh on the scene and this is terrible, Could we have fix like when the mesh are set Global and they are set invisible Octane doesn't take to gpu?

Please this would be really great for us.

Cheers,
JO

Jolbertoquini wrote:Hi Guys,

Please we need a quick fix on the plug, basically sometimes we want just hide the mesh and not being loading on the GPU this plug if we set global and visibility off doesn't work anymore, I understand when we have movable or reshapable for some animation is good to load so Octane load on frame one all scene when we hide and show.

Our problem is some scenes we want Octane to not export the only solution is delete the mesh on the scene and this is terrible, Could we have fix like when the mesh are set Global and they are set invisible Octane doesn't take to gpu?

Please this would be really great for us.

Cheers,
JO

Hi Jo,

Setting as "Scatter type" would help to hide the geometry in the scene.

Would you please use "Export selection" option for time being, may be put all the unnecessary geometry inside a layer?

BK wrote:

Jolbertoquini wrote:Hi Guys,

Please we need a quick fix on the plug, basically sometimes we want just hide the mesh and not being loading on the GPU this plug if we set global and visibility off doesn't work anymore, I understand when we have movable or reshapable for some animation is good to load so Octane load on frame one all scene when we hide and show.

Our problem is some scenes we want Octane to not export the only solution is delete the mesh on the scene and this is terrible, Could we have fix like when the mesh are set Global and they are set invisible Octane doesn't take to gpu?

Please this would be really great for us.

Cheers,
JO

Hi Jo,

Setting as "Scatter type" would help to hide the geometry in the scene.

Would you please use "Export selection" option for time being, may be put all the unnecessary geometry inside a layer?

Hi Bikram,

We don't want export the scene and scatter mode also download the mesh on the Octane buffer and Layer doesn't work did you actually tried?
I'm curious to now if a issue here.

What we need is have a control to chose what we don't want to be load on the buffer at Render stage hide the mesh for the render engine without export.

Right now, On Global mode visibility doesn't work and the mesh are loaded at the buffer, Is fine for the others like scatter,movable or reshapable they should be loaded and the visibility is working, only Global is broken, normally on Global mode if we set visibility off should be ignore by Octane.

Could we have a fix for that please???

Cheers,
Jo

Hi, with this version of the plugin, the render hags randomly with the next error:

Octane engine log:
CUDA error 719 on device 3: unspecified launch failure
CUDA error 719 on device 2: unspecified launch failure
CUDA error 719 on device 0: unspecified launch failure
CUDA error 719 on device 1: unspecified launch failure
-> kernel execution failed(report)
-> kernel execution failed(report)
-> failed to launch kernel(ptBrdf2)
-> failed to launch kernel(init4)
device 0: path tracing kernel failed
CUDA error 719 on device 2: unspecified launch failure
CUDA error 719 on device 3: unspecified launch failure
-> failed to copy memory from device.
-> failed to launch kernel(ptBrdf2)
device 1: path tracing kernel failed
device 3: path tracing kernel failed
device 2: path tracing kernel failed

My gpus are 3x780ti and 1x1080

I have noticed that the problem is more frequent when I have other programs opened like firefox or photoshop, when I have only maya opened the problem is less frequent.

abeoctane wrote:Hi, with this version of the plugin, the render hags randomly with the next error:

Octane engine log:
CUDA error 719 on device 3: unspecified launch failure
CUDA error 719 on device 2: unspecified launch failure
CUDA error 719 on device 0: unspecified launch failure
CUDA error 719 on device 1: unspecified launch failure
-> kernel execution failed(report)
-> kernel execution failed(report)
-> failed to launch kernel(ptBrdf2)
-> failed to launch kernel(init4)
device 0: path tracing kernel failed
CUDA error 719 on device 2: unspecified launch failure
CUDA error 719 on device 3: unspecified launch failure
-> failed to copy memory from device.
-> failed to launch kernel(ptBrdf2)
device 1: path tracing kernel failed
device 3: path tracing kernel failed
device 2: path tracing kernel failed

My gpus are 3x780ti and 1x1080

Hi abeoctane,

I think this most be some issues with yours drivers for the nvidia cards. and also is not related to the plug as error I think, Is Standalone or drivers issues we had that on our farm but after updates they all working fine now.

Cheers.
JO