OTOY Forums

-Materials don't update once applied; work around, change sub div level to 1 and then back to 0. **Sometimes this works, but not always.

-Sunlight environment: when i click to change sun position (very slowly i'm not clicking like in a first person shooter) often there's an immediate crash.

-Think you've got the clay made not working in batch render logged.

-When clicking 'renderer - octane' to preview and then back to 'viewport 2.0... I can generally do this ~5 times throughout a session if I'm lucky but eventually the render stops responding. 'Render current frame' stops working as well.
I've tried adjusting 'frames to precache' with no luck.
Generally the only fix I've found is to restart maya.

-Exporting ORBX scenes to standalone: Export 'orbx scene' , 'animated orbx scene' , 'octane-alembic' and then 'Cache - export all to alembic' seems excessive to begin with but moving past that. They never seem to work consistently. Sometimes animations export, sometimes they don't. Sometimes meshes are missing. And it's often not a consistent one way or the other.



Thanks

baxley wrote:-Materials don't update once applied; work around, change sub div level to 1 and then back to 0. **Sometimes this works, but not always.

-Sunlight environment: when i click to change sun position (very slowly i'm not clicking like in a first person shooter) often there's an immediate crash.

-Think you've got the clay made not working in batch render logged.

-When clicking 'renderer - octane' to preview and then back to 'viewport 2.0... I can generally do this ~5 times throughout a session if I'm lucky but eventually the render stops responding. 'Render current frame' stops working as well.
I've tried adjusting 'frames to precache' with no luck.
Generally the only fix I've found is to restart maya.

-Exporting ORBX scenes to standalone: Export 'orbx scene' , 'animated orbx scene' , 'octane-alembic' and then 'Cache - export all to alembic' seems excessive to begin with but moving past that. They never seem to work consistently. Sometimes animations export, sometimes they don't. Sometimes meshes are missing. And it's often not a consistent one way or the other.

Thanks

Hi Baxley,

Thank you for reporting this.
Would you please try disabling the Texture quality(SPP) and Swatch quality(SPP) from the Octane tab>Maya viewport defaults rollout?

or Maybe if you could share an Archived scene to investigate or let us know the steps to replicate!!

The Clay render bug will be fixed in the next release.

cheers

Haven't had a chance to do a non NDA project to share these errors yet.

Currently I'm seeing this in the script editor:

CUDA error 719 on device 1: unspecified launch failure
-> kernel synchronization failed
CUDA error 719 on device 0: unspecified launch failure
-> kernel synchronization failed
select -cl -sym ;
CUDA error 719 on device 1: unspecified launch failure
-> kernel synchronization failed
CUDA error 719 on device 0: unspecified launch failure
-> kernel synchronization failed

baxley wrote:Haven't had a chance to do a non NDA project to share these errors yet.

Currently I'm seeing this in the script editor:

CUDA error 719 on device 1: unspecified launch failure
-> kernel synchronization failed
CUDA error 719 on device 0: unspecified launch failure
-> kernel synchronization failed
select -cl -sym ;
CUDA error 719 on device 1: unspecified launch failure
-> kernel synchronization failed
CUDA error 719 on device 0: unspecified launch failure
-> kernel synchronization failed

hi Baxley,

Sorry for the late reply.
It could be the Nvidia driver issue.
Would you please try installing Nvidia Studio driver v460.89 [https://www.nvidia.com/download/driverResults.aspx/167759/en-us]

Also, please install either the GPUZ or Afterburner to monitor the GPU temperature as overheating could cause CUDA errors.

GPUZ[https://www.techpowerup.com/gpuz/]
MSI Afterburner[https://www.msi.com/Landing/afterburner]

cheers

hello.
I am working with mash and orbx instances.
When the scene gets more complicated I get this error.

Octane: scene translated in 46:624 sec. //
Unhandled exception in render data compilation (bad allocation). Application must restart.

Help please!!

My workstation
amd threadripper
2x2080Ti
windows 10

already had up to date nvidia drivers but tried this and still crashing all the time.
Seems to happen a lot when i do even super light displacement maps.
Still get crashes when moving sun position.
Any idea when next update is coming and if it will address these issues. Been having them for over a year now...

Upgraded from 2x 2080's to 1 2080 for display and 1x 3090 for engine... sunlight position seems to crash slightly less but 1/2 when i open 'edit orbx' material while i have octane render window enabled it's an immediate crash.

Over a year later and I still get countless crashes while opening orbx material editor while ipr rendering. Drivers are up to date. 3090 and 2080.
Please advise/FIX/make stable.

maya 2022.3

baxley wrote:Over a year later and I still get countless crashes while opening orbx material editor while ipr rendering. Drivers are up to date. 3090 and 2080.
Please advise/FIX/make stable.

maya 2022.3

Hi Baxley,

Thank you so much for posting this.
We are unable to replicate on our side.

Would you please share a video or the steps?

cheers

Was this resolved?

Was it a PSU issue?