I’m currently experiencing 2 errors when using the ART Maya plugin (I don’t believe they are related to one another).
After specifying the MayaTools directory (first time ART setup), I’ve experienced the following error message every time I start Maya:
# Error: file: C:/Program Files/Autodesk/Maya2014/scripts/others/performGpuCacheExport.mel line 561: IOError: file C:\Program Files\Unreal Engine\4.0\Engine\Extras\Maya_AnimationRiggingTools/MayaTools/General/Scripts\customMayaMenu.py line 249: 2 #
I was able to get this error to stop by adding a check:
if os.path.isfile(mayaToolsDir + "/General/Scripts/projectSettings.txt")
since the issue seemed to be that there wasn’t a “projectSettings.txt” file at the specified directory. Not sure if this will work as a permanent fix…
When I get to the point in the ART process where I click the “Build Control Rig” button, I fill out the information and hit the build button, but an error pops up, saying:
Could not save file: C:/Program Files/Unreal Engine/4.0/Engine/Extras/Maya_AnimationRiggingTools/MayaTools/General/ART/Projects/Sample/ExportFiles/a_Export.mb not a valid file.
File may exist already and be marked as read only. Aborting operation.
I have no idea why this one is happening, as Maya didn’t have any problems writing the Physique, JointMover, and Skeleton templates.
Please let me know if there is something I can do on my end to resolve these issues or if more information is needed. Thanks!
OK, I think the first issue is probably due to the projectSettings.txt file being read only. I’ll add a check to the code to make sure this doesn’t error, but I have a feeling that is the issue there.
As for the second issue, try pasting this file in your MayaTools/General/Scripts folder:
The file that is currently there is a compiled version, which might be causing issues. Let me know if that resolves the problem!
I’ve also updated the error message to be hopefully more descriptive as to what the issue is, instead of the generic “File may exist or be marked as read only”.
You can find that updated file here:
Hopefully that will also help narrow down the issue if the ART_Settings file wasn’t it.
Ok, that Helped. However, It looks to me like this variable somewhere within the collection of scripts isnt being set/overridden properly : mayaToolsDir
it seems that it still points to a d:/UE4/Build directory or something similar when I try pull in the mannequin template… Im assuming it should point to my maya scripts dir. I could set it at the top of the script, but id rather keep the files exactly as you guys packaged them for future update etc. Also, I dont know how many times that variable has been added throughout.
Are you referring to loading in the mannequin and the reference being set to the d:/ path? Unfortunately, Maya hard codes the reference paths which is a pain, so you may need to reset it to wherever the files lives locally on your machine.
yes, pulling in the mannequin comes up with a reference not found issue.
Im not sure what you mean by reset it however? Im hoping that missing reference doesnt come up everytime one our artists tries to pull in the mannequin.
You should be able to browse to the new location when that message comes up. There is a checkbox as well that says something along the lines of “remember path changes”. Checking that will fix up the reference paths to be correct on your machine.
Everything in the toolkit uses relative directory paths based on your install location. However, Maya’s referencing uses absolute paths I haven’t looked too deeply into whether or not I can catch that and change it automatically for the user. I’ll be adding that to my list for investigation.
ahh i see, well yes, i guess that depends how its being called. Im not sure what approach requires it to be hardcoded in, I typically just make a new file reference, or in the past if ive had to literally edit references in place ( pretty rare ) ive literally just called in the ascii and saved over the top replacing the references… referenceEdits/referenceQueries don’t give you that control to my knowledge so they are the only options im aware of.
The addcharacter_ui method is calling on a file “mayaTools.txt”, which looks as though its supposed to be in my scripts dir (based on the cmds.internalVar(usd = True)) but isnt.
from art_addcharacter_ui
Im definitely still getting this error also:
Error: 2
Traceback (most recent call last):
File “C:/Users/ac/Documents/maya/scripts/MayaTools/General/Scripts\customMayaMenu.py”, line 249, in p4ProjectMenu
f = open(mayaToolsDir + “/General/Scripts/projectSettings.txt”, ‘r’)
IOError: [Errno 2] No such file or directory: ‘C:/Users/ac/Documents/maya/scripts/MayaTools/General/Scripts/projectSettings.txt’
on starting up maya
Since ive replaced the skeletonbuilder ui with the version mentioned above Im now also getting
Error: invalid syntax
Traceback (most recent call last):
File “C:/Users/ac/Documents/maya/scripts/MayaTools/General/Scripts\customMayaMenu.py”, line 635, in launchSkeletonBuilder
import ART_skeletonBuilder_UI
File “C:/Users/ac/Documents/maya/scripts/MayaTools/General/Scripts\ART_skeletonBuilder_UI.py”, line 1
@spooty89, what version of Maya are you using? Are you by chance using a student license?
Anyone else that is having the " File may exist already and be marked as read only. Aborting operation." error, what version/license of maya are you all running? We’ve been trying to reproduce this error and so far, the only thing we’ve been able to possibly find is that users running into this have been on a student license.
line 14647: cmds.file(save = True, type = “mayaBinary”, force = True, prompt = True)
you must to set prompt=true, because of the warning message that saving process in maya occurs with student edition !
don’t forget to fix the problem for AnimRig folder =)
there is 4 place to edit :
14647, 14829, 14955 and 14987
I haven’t looked too deeply into whether or not I can catch that and change it automatically for the user. I’ll be adding that to my list for investigation.