well done
If this supports Maya 2014 you should update the 'Maya® Version Requirements' on top
OctaneRender® for Maya® v1.18 beta [OBSOLETE]
Moderator: JimStar
No they don't. I have now had time to check and the problem began on Maya plugin v1.11brenmaxhb wrote:TBFX,
All versions have the bug you found.
v1.11a worked fine so something changed between those.
JimStar,
Just to reiterate - IPR works fine but render or batch render gives the mesh export error.
The cut down scene I uploaded is from Maya 2014 so you can't test it with older versions of the plugin. Let me know if you need it and I'll create a new cutdown in 2013.
T.
Win10 x64|i7-9750H 2.6 GHz|32 GB RAM | RTX2080 max Q 8GB
Hi JimStar!
I've got a little trouble with texture animation.
In v1.16c was claimed
Do I need to create movable proxies in this type of scene or what should I do?
I've got a little trouble with texture animation.
In v1.16c was claimed
In IPR texture animations work fine, even in "Camera only" mode, but the Batch render gives me an error.Now materials are animated in "Movable proxy" animation mode too.
I have no movable proxies in my scene, I just want to animate a texture.mayaRenderLog.txt:
Error: Octane: Error refreshing movable proxies. Octane render stopped. You can enable verbose mode in Octane settings to see scene compilation details...
Do I need to create movable proxies in this type of scene or what should I do?
SketchUp Pro 8/ Maya 2012 / W7 64bit / Intel i7 870 / 8GB / 2*GeForce gtx 680 4GB
Thank you for report!TBFX wrote:Hi JimStar,
I have found a bug in this version. I have a scene (a cut down version is attached) that will render fine in IPR mode but as soon as you try to render in standard render mode or batch render it errors out when it tries to compile the instanced geometry. The geo is manually instanced and not particle instanced.
The error in verbose mode is as follows:
Octane: Object "grillSection_1|grillSectionVerticals_2|pCylinder182_3|pCylinder_Shape102" is instanced //
// //
// 0:01 Setting Mesh data of mesh: pCylinder_Shape102 //
// ****************************** MESH DATA ****************************** //
// Number of vertices: 14 //
// Number of normals: 14 //
// Number of UVs: 28 //
// Number of polygons: 18 //
// Number of vertex indices: 60 //
// Number of normal indices: 60 //
// Number of UV indices: 60 //
// Number of material indices: 18 //
// 0:01 ...done setting Mesh data in 0:00 //
// 0:01 Voxelizing... //
// 0:01 ...voxelized in 0:00 //
// Error: Octane: error compiling mesh "pCylinder_Shape102" (instance 1) //
// Error: Octane: Error mesh export. Octane render stopped. //
This bug may have crept in to a version before this one as I haven't rendered this scene in a while but it is definitely present in v1.18 and the scene did render fine in v1.0
T.
I have found the problem, will be fixed soon in new upcoming release. It was the consequence of fighting with non-unique object names..
