Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2020.1.6f1
2020.2
Issue ID
1282357
Regression
No
Unity will pick the version of Maya which was installed last not the corresponding version when importing/opening .ma/.mb file
How to reproduce:
1. Firstly install Maya 2020
2. Secondly install Maya 2018
3. Make anything with Maya 2020, save as .mb or .ma
4. Create new Unity project
5. Import file from Maya 2020 to Unity
Expected results: Unity imports the file with Maya 2020
Actual results: Unity tries to import the file with Maya 2018
Reproducible with: 2018.4.28f1, 2019.4.13f1, 2020.1.10f1, 2020.2.0b8
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Resolution Note (2021.1.X):
Unity opens the Maya installation that is assigned to the file extension by the OS. Make sure that the wanted version opens when you start Maya from the file (.mb or .ma). Consequently, only one version at a time is possible.