Community Forums for OTOY Customers
https://render.otoy.com/forum/
Can you pls send me a Rhino scene which demonstrates the problem, and I will take a closer look.unfortunately it isn't making any difference in my end.
i will look through my setting and workflow once again to make sure i'm not making any mistake, but it'll be great if you can keep looking into other possible cause for this.
The current TEST release can be considered as STABLE.I need to update to 3.03 at a client's place. Is there a "stable" release (of the Rhino plugin) comming shortly or can I consider the current one as quite stable.
I thought this had been fixed in a recent release. Which version of the plugin are you running pls?I was working on a large scene, rendering a hires panoramic image. Suddenly the scene stopped rendering, the attached dialogue windows appeared after the voxelization phase, I think the last thing i did was changing the resolution while rendering. I deleted all geometry and loaded the octane default settings -> still crashing... attached please find the screenshot of the error message and the stripped down scene.
Is it possible the unused material belongs to a layer?P.S. another thing I observed several times before in other scenes: If you look at the second screenshot, you can see that despite purging several times, there is still a unused material in this scene - do you know why ?
P.S.S. another thing : this scene is huge ! although it only contains one polysurface box, it is 30 MB... something is definitely wrong
Also worth noting on that scene is that if you click the Perspective View, you can see the Rhino Camera coords are corrupt (the Octane Camera is translating them to an Up Vector with "Not a Number". I've seen this before, and found the solution was to create a new Perspective viewport - which will not have a corrupted Rhino camera.I was working on a large scene, rendering a hires panoramic image. Suddenly the scene stopped rendering, the attached dialogue windows appeared after the voxelization phase, I think the last thing i did was changing the resolution while rendering. I deleted all geometry and loaded the octane default settings -> still crashing... attached please find the screenshot of the error message and the stripped down scene.
Hi Paul,face_off wrote:I have updated this links at the top of this thread with:
3.3.4.71
- Compiled with Octane 3.03.4
- Fixed issue where exporting a Bongo animation to ORBX/OCS was not correctly setting the FPS when that scene was opened in Octane Standalone
- Added command OctaneConvertAllMaterialsToOctaneMaterials which does the same function as the Setup tree menu command "Convert all Materials to Octane Materials"
- Added command OctaneExportSceneToORBX
I have also merged the TEST and STABLE threads into this thread.
Paul
Hi Alxen - yes, those controls are in the 3.3.4.71 release.Did you added new "visible..." attributes for visible environment mode or visible background. I need this.