Scene Tools 2.4.1 for Maya (maya script)

Modeless Maya File Browser and custom Open Scene Dialog with scene thumbnails and note display. Tools for dealing with playblasts, references and more...

Back to Bugs List Previous Next

Bugs

Can not open in maya2014

Status	closed
Priority	high
Date	10/16/2013
Submitted by	li jianjian
Modify this bug	edit

when i run craSceneTools in maya, maya give me a error message "// Error: "C:/Users/xxxx/Documents/maya/2014-x64/scripts/craSceneTools.mel" line 4329.59: Syntax error".
The scripts only suport english system ? if try to run the script in Other language system maya will have error?

Comments on this bug:

CharlieWales said about 13 years ago:

Hi, it seems that the error occurs because of this lines: line 4328. string $invalidCharacters[] = {"-", " ", "[", "]", "·", "$", "(", ")", "^", "'", "{", "}", "&", "%", "@", "#", "?", "¿", "!", "¡"}; line 4329. for($chr in $invalidCharacters) line 4329. $craSetSelectedProjectName = substituteAllString($craSetSelectedProjectName, $chr, "_"); and lines 4451, 4452 and 4453 (these are the same lines as above) I have run craSceneTools in Maya 2014 x64 Service Pack 2 with fresh Maya prefs/settings and it works correctly . Maybe you are right and has something to do with the Maya language. Which language are you using Maya with? Do you have this invalid characters in your keyboard layout / operating system? You can try to remove those lines and run it again to see if this way it works, though if it is the case and you need to remove those lines I cannot say if the tool will work correctly anymore if you have any project folder that contains any of those characters as Maya does not allow to use them inside the program for naming maya UI widgets. The tool needs to get rid of those characters in case they are present because of the way the tools works. Thanks for the feedback.

Report
CharlieWales said about 13 years ago:

Alright, well, try to delete those lines an let me know if that works for you. Due to the fact that the tool works as expected in english based systems I'm closing this bug report. Thanks for the feedback.

Report