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

Suggestion: point out a Maya hiccup in export workflow in the plugin readme file #6613

Closed
michaelybecker opened this issue May 27, 2015 · 6 comments

Comments

@michaelybecker
Copy link
Contributor

Hi! As a newcomer to this lovely library, it took me a long, long time to realize that my objects weren't exporting well from maya, and showing up as not well formed, simply because I didn't delete object history before exporting (I believe that's the case for .obj export/import from maya although I haven't tested it thoroughly). Once I made sure I deleted object history everything worked out.

I think a clarification in the readme about the need to do so would prove extremely helpful for others in my situation. Thanks!

@mrdoob
Copy link
Owner

mrdoob commented May 29, 2015

@Lu-Do
Copy link

Lu-Do commented Jun 23, 2015

ehm, deleting history means that the mesh cannot be a skinned one... or am i wrong?

@michaelybecker
Copy link
Contributor Author

I could be wrong, but it's my understanding that the JSON exporter is
intended exclusively for static models anyway, so skinning isn't an issue.
Any model that includes rigging/animation/skinning etc. is best exported
using Collada DAE files (for example, see
http://stackoverflow.com/questions/14736090/maya-to-three-js-with-animation
).

Re. file update - haven't had a chance to properly test the workflow (and
I'd need to in order to justify a doc change;), but I hope to get to it
soon!

On Tue, Jun 23, 2015 at 6:27 AM, Lu-Do notifications@github.com wrote:

ehm, deleting history means that the mesh cannot be a skinned one... or am
i wrong?


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

@michaelybecker
Copy link
Contributor Author

I could be wrong, but it's my understanding that the JSON exporter is intended exclusively for static models anyway, so skinning isn't an issue.
Any model that includes rigging/animation/skinning etc. is best exported using Collada DAE files (for example, see http://stackoverflow.com/questions/14736090/maya-to-three-js-with-animation).

Re. file update - haven't had a chance to properly test the workflow (and I'd need to in order to justify a doc change;), but I hope to get to it soon!

@Lu-Do
Copy link

Lu-Do commented Jun 23, 2015

thnks for the reply Michael! well, the exporter's dialog actually lets you choose to include skinning info and animation... i'm just a 3d artist, but i've send a bunch of animated .js to a programmer to put the stuff in his code. it seems to work, although not every time! not sure about what's happening at the moment (the "not well formed" problem), but the problem could be exactly the same you pointed out. before binding the skin in maya all object should have no history and freezed transformation... not sure anyway, i need the programmer feedback on this. i will anyway try to work with .dae too.
cheers!

@michaelybecker
Copy link
Contributor Author

Interesting, didn't know those translated well to JSON! Very impressive.
I'll dig into it further and update if I learn anything new in the matter. Thanks for the tip!

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

No branches or pull requests

4 participants