OTOY Forums

BK wrote:The implementation of Global type is to save translation time allowing nonanimated objects merging into only one translation node. [ https://docs.otoy.com/MayaH/MayaPluginM ... yTypes.htm]

calus wrote:

BK wrote:The implementation of Global type is to save translation time allowing nonanimated objects merging into only one translation node. [ https://docs.otoy.com/MayaH/MayaPluginM ... yTypes.htm]

Hey Bikram,
the online help about Global Geometry Type is not up to date, I think.

The Global type was useful in V2, it could make rendering really faster in some cases:
Indeed, merging objects into one is a common trick to speed-up ray-scene intersections for old raytracers.

But since V3, Octane seems to use a more efficient acceleration structure making this trick useless.
In my tests, rendering is even slower with Global Geometry Type now, because of the additional "mesh merging" time.

In my opinion the Global type should be removed because it doesn't speed-up rendering anymore and breaks a lot of Octane features.
Or did you find a use-case where the Global Geometry Type has any advantage in V3 ?

p3taoctane wrote:Geometry type

I have some mesh spheres that are animated on and off in visibility on the maya visibility node and the mesh is set to reshapable proxy as they are attached to a bend deformer.

Render window does not update this visibility feature.... is there any setting that I can key frame in Octane Render settings that will enable these to update in the render viewer for Octane render?

Thanks

Peter

calus wrote:

p3taoctane wrote:Geometry type

I have some mesh spheres that are animated on and off in visibility on the maya visibility node and the mesh is set to reshapable proxy as they are attached to a bend deformer.

Render window does not update this visibility feature.... is there any setting that I can key frame in Octane Render settings that will enable these to update in the render viewer for Octane render?

Thanks

Peter

Strange, this should work, if visibility is not updated in IPR for Reshapable Proxies, well this is a bug ...
I can't check now but I didn't notice this problem before,
trying to guess :

- Maybe you have the "animation mode" in render setting set to "Full" and should be set to "Movable proxies" for this to work ?
- Or maybe this is the visibility of the shape that you have animated and this only work if you animate visibility at the transform level ?

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

coilbook wrote:

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 were you able to fix this error? I am getting it a lot especially with VDBs Thank you

itsallgoode9 wrote:Considering, in the following "months" there will be no Maya 2018 support, no bug fixes and no feature additions, would you mind letting us know some some sort update on progress of the refactoring of the plugin? Now that it's been over a month since your last update, any update yet on what "months" means (will we get any update or support in 2017 etc)?