OTOY Forums

Turned the arnold plugin off and now its working... but this is a new thing it seems.. worth a look at maybe

Thanks

p3taotoy
This is an Arnold bug, nothing to do with Octane.

You can try a quick fix yourself in your installation of Maya, by making a small change to one of Arnold scripts:
- Close Maya.
- Delete the C:\Program Files\Autodesk\Arnold\maya2020\scripts\mtoa\ui\globals\common.pyc (Python cache) file.
- Open the C:\Program Files\Autodesk\Arnold\maya2020\scripts\mtoa\ui\globals\common.py file in a text editor.
- Replace the line 2209 (the one containing cmds.scrollField(control, edit=True, text=value)) by two lines: Pay attention to proper code indentation of each line, in Python it is important (amount of forward spaces, explained e.g. HERE).

This is just a quick fix to eliminate this error Arnold script throws, but I don't guarantee that there are no other bugs in Arnold scripts producing conflicts and preventing a proper workflow when Arnold is not a current renderer. The proper thing to do for Arnold would be to have their irrelevant scriptJobs disabled when Arnold is not selected as a current renderer and there are no existing UI elements their scriptJobs were registered for (which would be more changes than just replacing these two lines).

i'm getting a WHOLE lot of "Translating Mesh Objects, Stage #1" messages, which constantly beach balling while Maya hangs. Nothing is animated or anything, so any clue what's up?

I'm not sure what exactly is triggering that. But in the scene i'm currently in, all I did was uncheck "maintain width/height ration" and the it started re-translating anything (all I did is uncheck the box, I hadn't changed any dimensions)

itsallgoode9
I can't answer this without the scene.

JimStar wrote:itsallgoode9
I can't answer this without the scene.

just messaged you the file.

itsallgoode9
Thank you for the scene.
Just checked it - nothing suspicious on my side, just the normal scene translation. It is a heavy scene with 253 meshes, almost 11 million polygons and heavy textures (eats almost 3GB of memory on my GTX980) - and it just spends about 4 seconds in the "Translating Mesh Objects" stage. Most of the time after that (already after the scene got translated by the plugin and already loaded into the rendering engine) - Maya hangs waiting for the Octane rendering engine finishes its job evaluating the translated/loaded scene and starts the rendering process.

Thanks Jimstar for the info will give it a try

Peter

I had 2 slave machines active with 2 GPU's in each, and noticed IPR/Render Frame would never finish rendering, it would get stuck on 115/150 samples (different minimum each time I would try), as soon as I quick Slave Daemons on slave machines, the render would finish.

g0ll4m
This looks like the rendering engine's issue, not the plugin's. Not sure if you can reproduce it in the same version of standalone, but the plugin just waits before the engine's API reports the max-samples reached (and this number is shown by the plugin in the render-statistics too). So if the engine SDK never reports the max-samples reached because of some daemon is stuck - there is nothing the plugin can do here...

Hi Jim,

Thanks for this release , there is a bug (or maybe feature missing) on those plugs is when we export orbx some constraints connections is not being baked basically each time need bake all those constraints manually , for example the Pascal script for the sun direction. and also when we plug float information drive by maya to drive float or octanes node please check here some screen shots and the maya scene.

Cheers
JO