super annoying bug that requires force quit

[nick.holliday]

Everytime i hover over the menu to assign  new materials i get this error ehich im unable to escape for and so need to force quit.!  I cant be the only one (i know im not).  Surely this could/should be fixed asap?

[Christoph_Schaedl]

Which Maya and Arnold version are you using?

[nick.holliday]

Hi

im using 2024.1  and arnold 5.3.1.1

[brentmc]

Which platform are you running Maya on and do you have any other plugin shaders loaded?

Also, could we get a bit more detail on how to reproduce the issue. Like a screenshot showing which menu are you are hovering over when the error occurs. 

Thanks.

[nick.holliday]

sorry, it was a bit of a rage post. Ill get a video  (im on windows 11)

[nick.holliday]

Her'es a vid. It doesnt happen with every mesh.  Just certain ones.

[brentmc]

Hi Nick,

Thanks for this. Any chance of getting one of the scene files that triggers this error?

You can send it to brent.mcpherson@autodesk.com and it will only be used for investigating this issue.

Thanks.

[brentmc · Accepted solution]

Hi Nick,

A quick update on our investigation.

The security issue is coming from the uiConfigurationScriptNode in the file and deleting these two lines from the file fixes the issue.

-docTag \"isolOutln_fromSeln\"
-docTag \"RADRENDER\"

There are also settings in Preferences > UI Elements that prevent Maya from generation and/or using the uiConfiguration node and disabling these also avoids the issue in my tests.



Thanks.

[nick.holliday]

oh!  thanks for the update - ill give it  try.  Was there something i did that might have caused that to happen?

[brentmc]

No, it isn't anything you have done.

It only seems to happen in the context menu, not in the main Lighting/Shading menu in the main menubar!?

Another workaround is to uncheck the Python compile command in the Python Security preferences:

[nick.holliday]

thanks again. It seems unchecking those initial prefs seems to have done the trick!