mtoa error when adding AOVs due to initialParticleSE shader

[felipe.ruizQ99GU]

We are getting this error. Seems like some of the default shaders in Maya like "initialParticleSE" shaders doesn't play well with mtoa. Not sure why adding aovs on some of our scenes are causing this problem. Fyi: initialParticleSE cannot be deleted or manipulated because it is Maya default node.

--Felipe

# Error: setAttr: The attribute 'initialParticleSE.aiCustomAOVs[0].aovName' is locked or connected and cannot be modified.
# Traceback (most recent call last):
#   File "/net/software/autodesk/modules/maya/2020/arnold/maya2020_linux_4.2.3/scripts/mtoa/ui/aoveditor.py", line 163, in addAOVs
#     aov = self.renderOptions.addAOV(aovName, aovShader=aovShaderName)
#   File "/net/software/autodesk/modules/maya/2020/arnold/maya2020_linux_4.2.3/scripts/mtoa/aovs.py", line 419, in addAOV
#     addAliases([aov])
#   File "/net/software/autodesk/modules/maya/2020/arnold/maya2020_linux_4.2.3/scripts/mtoa/aovs.py", line 173, in addAliases
#     cmds.setAttr(plug, aov.name, type="string")
# RuntimeError: setAttr: The attribute 'initialParticleSE.aiCustomAOVs[0].aovName' is locked or connected and cannot be modified. # 

[Stephen.Blair]

Got a repro scene you can share? Or are there some steps I have to do before adding an AOV?

[felipe.ruizQ99GU]

@Stephen Blair attached is a zip file with 2 empty maya files, open reproScene2.ma and make sure that the externalFile2.ma is properly referenced. Then attempt to add multiple aovs in the Render settings panel. You should get the error above. reproScenes.zip

[felipe.ruizQ99GU]

Thanks for looking into this. Please see Answer's section for attachment.

[Stephen.Blair]

@

Thanks. But I'm off today and tomorrow is a global corporate holiday...

[felipe.ruizQ99GU]

No worries, we got around it by editing aovs.py But it would be nice to not have to add this change set every time we upgrade versions.

[felipe.ruizQ99GU]

Hello, we are still running into this issues in Maya 2022.2. Any updates?

[Stephen.Blair]

Did you try unlocking it with MEL?

lockNode -lock off -lu off initialParticleSE

[Stephen.Blair]

I'm still able to add AOVs, and they render. But that is on Windows.

What happens on Linux? You can't add AOVs at all?

[felipe.ruizQ99GU]

Yeah! that works. Thanks!

[Karthik_Kumar1]

try this python script.

import maya.cmds as cmds

cmds.lockNode('initialShadingGroup', lock=False, lu=False)

cmds.lockNode('initialParticleSE', lock=False, lu=False)

[Karthik_Kumar1]

Try this python script

import maya.cmds as cmds

cmds.lockNode('initialShadingGroup', lock=False, lu=False)

cmds.lockNode('initialParticleSE', lock=False, lu=False)

[andrej.djukic]

This works, thank you very much

I did use the script a bit changed as the initial shading group was locked and could not apply a new shader at the object at all.

Mel script: lockNode -lock off -lu off initialParticleSE initialShadingGroup.nodeState

[subratakaal99]

# Error: RuntimeError: file C:\solidangle\mtoadeploy\2018\scripts\mtoa\aovs.py line 164: setAttr: The attribute 'initialParticleSE.aiCustomAOVs[0].aovName' is locked or connected and cannot be modified.

[lee_griggs]

@subratakaal99  Try updating your plugin here.