Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

maya 2015 export plugin errorrs #6053

Closed
makc opened this issue Feb 11, 2015 · 8 comments
Closed

maya 2015 export plugin errorrs #6053

makc opened this issue Feb 11, 2015 · 8 comments

Comments

@makc
Copy link
Contributor

makc commented Feb 11, 2015

So, 1st of all it requires pymel, which latest version from 2012 does not even install, unless you patch it like this.

2nd, after you go all the way and try to enable it in Maya, you get this:

// Error: line 1: ImportError: file /Volumes/HDD/Applications/Autodesk/maya2015/Maya.app/Contents/Frameworks/Python.framework/Versions/Current/lib/python2.7/site-packages/pymel-1.0.0-py2.7.egg/pymel/internal/parsers.py line 11: No module named BeautifulSoup // 
// Warning: line 1: Failed to run file: /Users/makc/Library/Preferences/Autodesk/maya/2015-x64/plug-ins/threeJsFileTranslator.py // 
// Error: line 1:  (threeJsFileTranslator) // 
// Error: file: /Volumes/HDD/Applications/Autodesk/maya2015/Maya.app/Contents/scripts/others/registerVectorRenderer.mel line 71: The renderer mayaVector is already registered.  To edit it, use the "-edit" flag. // 
@makc
Copy link
Contributor Author

makc commented Feb 11, 2015

So I manually downloaded BeautifulSoup.py from 3.2.1 and placed it under /Volumes/HDD/Applications/Autodesk/maya2015/Maya.app/Contents/Frameworks/Python.framework/Versions/Current/lib/python2.7/site-packages/ - now the error says:

// Error: line 1: IOError: file /Volumes/HDD/Applications/Autodesk/maya2015/Maya.app/Contents/Frameworks/Python.framework/Versions/Current/lib/python2.7/site-packages/pymel-1.0.0-py2.7.egg/pymel/internal/parsers.py line 368: Cannot find maya documentation. Expected to find it at /Volumes/HDD/Applications/Autodesk/maya2015/docs/Maya2015/en_US // 

My /Volumes/HDD/Applications/Autodesk/maya2015/docs/ is empty 🍶 Trying to get this thing, will report how did it go )

@makc
Copy link
Contributor Author

makc commented Feb 11, 2015

Useless 1G download. Pymel expects API subfolder with files like API/class_m3d_view.html which is not there.

@makc
Copy link
Contributor Author

makc commented Feb 11, 2015

💩 💩 💩
looks like pymel moved to github and I was wrong to assume google code has the latest version. any way, this does not seem to be directly relevant to the exporter, so closing.

@makc makc closed this as completed Feb 11, 2015
@michaelybecker
Copy link
Contributor

Did installing the most recent version of pymel solve the error? So far I've inadvertently followed in your footsteps (got pymel from google code) and received the abominable "line 71: The renderer mayaVector is already registered. To edit it, use the "-edit" flag.". How did you get rid of it? Thanks!

@makc
Copy link
Contributor Author

makc commented May 17, 2015

I don't remember ( Most probably I've found some way not involving using the exporter.

@mprice1
Copy link

mprice1 commented May 30, 2015

Just ran into this today...
MichaelHazani: Did you make any headway here?

I notice that for me, an older version of the three.js maya exporter works as expected (while still depending on PyMel). But it does not support bones/animation, which I need...
I get the same errors as above.

@Dynasty9
Copy link

We have an exporter that handles this functionality at
https://github.com/BlackTowerEntertainment/animation-tools
On May 30, 2015 1:37 PM, "mprice1" notifications@github.com wrote:

Just ran into this today...
MichaelHazani: Did you make any headway here?

I notice that for me, an older version of the three.js maya exporter works
as expected (while still depending on PyMel). But it does not support
bones/animation, which I need...
I get the same errors as above.


Reply to this email directly or view it on GitHub
#6053 (comment).

@michaelybecker
Copy link
Contributor

@mprice1 : fixed in Maya 2016. No idea what was wrong but upgrading Maya and reinstalling pymel and the plugins solved it. Haven't experimented with rigging yet - I'll look into @Dynasty9 's recommendation if it breaks again (but since my plugin issues started at runtime, I doubt I'll get the problem again.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants