This forum is for swapping tips or ideas with fellow users, suggesting new features, or showing of what you have created with the system etc, there is no guarantee of an answer to questions posted in the forum. All support questions must be submitted via the Support ticket system
So I've been working with an artist to try and get morph data from 3DS Max into a Unity project using MegaFiers' morph feature. But, I continually get errors upon importing the .mor file.
For reference, this is the tutorial video we've been following:
When I first add the Modify Object component, this error appears in the console:
I then add the Morph modifier and choose to import the .mor file. Immediately, I get this error message:
On hitting okay, this message shows in the console:
We've consulted this page regarding reasons mapping might fail:
Our artist has attempted to avoid any of the listed issues. He also wasn't sure if the bones should be selected when exporting the .mor file and so we tried with and without. Any version of the .mor file seems to give the same errors.
I've also seen that you have the option (?) of importing morph targets by .OBJ files. Is that necessary if you've exported a .mor file?
Is there something I'm missing or something different we should be doing from the tutorial video above?
Is it possible the errors I'm seeing on adding the Modify Object component are related?
The OBJ file import of morph targets is there for people who use a 3d package that does not have an exporter currently available for it, but if you have an exporter and an mor file then use that.
I get a lot of emails about mapping failures and files sent to me saying they have tried everything and in every single case it has been moved pivots that have caused the issue. You you would like me to check the files then you can submit a support ticket at http://www.west-racing.com/mf/?page_id=385 I am trying to keep all support requests in the ticket system now as it is getting very hard to keep track of all the various forums questions are asked on and from numerous emails, the ticket system keeps it all in one place and I can easily keep track of what I need to do 🙂
Chris
Okay, after banging our heads over this for a while, I realised that the mistake is 100% my own bone-headedness. I simply attached the components to the wrong object in the model's hierarchy, so they obviously weren't able to read the mesh data (hence the null reference exception above). Oi...
Author
Morphs — Errors in Mapping
