Yes, python is supposed to be case-sensitive. The files should have been lowercased according to the changes in code. I didn't get the same problem on my system, because there are still lowercased .pyc files (compiled python), while the originals have been reverted to uppercase. Probably a problem of windows and git disagreeing on the case-ness of a file. I will remember to fix the naming of these files in the repository. Thx!
The problem of compiling in 4.14. Yes, deleting or commenting the line in question is ok. The correct solution takes a lot more time though, because I don't want to (again) adapt the changes of the asset import code, but instead only detect for .fbx import and then call upon the m2uFbxFactory, while delegating all other assets to the original code. But as far as I remember, that's not so simple. There has to be a reason for the current hacky solution.
Deprecation warnings can be ignored until the next minor version increase (4.15)
[MENTION=3956]James Barnette[/MENTION]: Do you have any suggestions on how to improve the maya instructions? The current readme https://github.com/m2u/m2u/blob/develop/README.md contains step-by-step instructions with links to official documentations where appropriate. Anything in particular that is unclear?
The problem of compiling in 4.14. Yes, deleting or commenting the line in question is ok. The correct solution takes a lot more time though, because I don't want to (again) adapt the changes of the asset import code, but instead only detect for .fbx import and then call upon the m2uFbxFactory, while delegating all other assets to the original code. But as far as I remember, that's not so simple. There has to be a reason for the current hacky solution.
Deprecation warnings can be ignored until the next minor version increase (4.15)
[MENTION=3956]James Barnette[/MENTION]: Do you have any suggestions on how to improve the maya instructions? The current readme https://github.com/m2u/m2u/blob/develop/README.md contains step-by-step instructions with links to official documentations where appropriate. Anything in particular that is unclear?
Comment