I have some errors/warnings in the script editor on fresh boot of Maya how to fix?

I have some errors/warnings in the script editor on fresh boot of Maya how to fix?

malcolm_341
Collaborator Collaborator
1,984 Views
11 Replies
Message 1 of 12

I have some errors/warnings in the script editor on fresh boot of Maya how to fix?

malcolm_341
Collaborator
Collaborator

Hi there, Maya is starting a bit slower than I remember so I'd like to clear out these warnings/errors from the script editor as Maya starts up. Does anyone know how to fix these?

 

textureWindowSetCheckerMapApplyOptionsUpdateTexEditor 1;
// Error: line 1: Cannot find procedure "textureWindowSetCheckerMapApplyOptionsUpdateTexEditor". //

 

evalDeferred "shaderBallRendererMenuUpdate";
// Warning: file: C:\Users\malco\Documents\maya\2022\prefs\filePathEditorRegistryPrefs.mel line 4: filePathEditor: Attribute 'aiImage.filename' is invalid or is not designated 'usedAsFilename'. //
// Warning: file: C:\Users\malco\Documents\maya\2022\prefs\filePathEditorRegistryPrefs.mel line 5: filePathEditor: Attribute 'aiPhotometricLight.aiFilename' is invalid or is not designated 'usedAsFilename'. //
// Warning: file: C:\Users\malco\Documents\maya\2022\prefs\filePathEditorRegistryPrefs.mel line 7: filePathEditor: Attribute 'aiVolume.filename' is invalid or is not designated 'usedAsFilename'. //
// Warning: line 1: filePathEditor: Attribute 'aiVolume.filename' and label 'VDB' have been saved already. //
// Warning: line 1: filePathEditor: Attribute 'aiImage.filename' and label 'Image' have been saved already. //
// Warning: line 1: filePathEditor: Attribute 'aiPhotometricLight.aiFilename' and label 'IES' have been saved already. // Attribute 'aiVolume.filename' is invalid or is not designated 'usedAsFilename'. //
// Warning: line 1: filePathEditor: Attribute 'aiVolume.filename' and label 'VDB' have been saved already. //
// Warning: line 1: filePathEditor: Attribute 'aiImage.filename' and label 'Image' have been saved already. //
// Warning: line 1: filePathEditor: Attribute 'aiPhotometricLight.aiFilename' and label 'IES' have been saved already. //

0 Likes
Accepted solutions (1)
1,985 Views
11 Replies
Replies (11)
Message 2 of 12

malcolm_341
Collaborator
Collaborator
Accepted solution

Closing Maya and deleting this file cleared up most of my errors after the file regenerates on startup filePathEditorRegistryPrefs.mel

0 Likes
Message 3 of 12

MrEddie
Enthusiast
Enthusiast

Any progress on the below error ? I can't seem to find what is causing it.

textureWindowSetCheckerMapApplyOptionsUpdateTexEditor 1;
// Error: line 1: Cannot find procedure "textureWindowSetCheckerMapApplyOptionsUpdateTexEditor". //

0 Likes
Message 4 of 12

malcolm_341
Collaborator
Collaborator

@MrEddieNope, I'm still getting all those errors and warnings in Maya 2024.

0 Likes
Message 5 of 12

MrEddie
Enthusiast
Enthusiast
In userprefs.mel... stack trace can be turned off. (One solution). I am trying to track it down, it is something in userprefs.mel.

// Script Editor
optionVar -cat "Script Editor"
-iv "echoAllLines" 1
-iv "stackTraceIsOn" 1
;
0 Likes
Message 6 of 12

MrEddie
Enthusiast
Enthusiast

I think I found it, switch this to 0 and that error does not show up in the stack trace on start-up.

MrEddie_0-1692691765635.png

 

Something to do with 3d cut and sew tool, - and it's integration with the Cut tool in UV editor, it switches back and forth if UV editor is active or viewport. Some weirdness in how they are sharing and saving settings for checkermap and UV shell colouring, there must be some conflict. 

 

 

Message 7 of 12

malcolm_341
Collaborator
Collaborator

@MrEddiewhich mel file did you edit to find that option?

0 Likes
Message 8 of 12

MrEddie
Enthusiast
Enthusiast
userprefs.mel, I noticed that some funky relationship between the checker settings in the UV editor are linked to the Tool Settings for the 3d Cut and Sew tool, so even if you disable the checker option in the tool, it can be re-enabled in the background- again changing that value to 1 from 0. For now I'll add an adjustment mel script to override it, so I don't get that annoying popup!
Message 9 of 12

brentmc
Autodesk
Autodesk

Hi,

I can confirm it is a bug related to the polyCutUV tool. 

It is trying to call procedures in texturePanel.mel when restoring preferences that have not been loaded yet.

I'll pass this on to the modeling team.

Thanks.

Brent McPherson
Principle Engineer
Message 10 of 12

malcolm_341
Collaborator
Collaborator

@brentmcThanks, much appreciated.

Message 11 of 12

laomusic_arts
Advocate
Advocate

Hi!

Turning off the warnings in not a fix for this issue.
I´ll try some stuff and post later. Thank you all for the tips!

 

LAO

0 Likes
Message 12 of 12

marcosvicenteAVPHC
Explorer
Explorer

Hi! I had the same issue, fixed it by reseting 3D Cut and Sew tool settings. Seems like the Display->Show checker map option causes this stack trace message.

0 Likes