Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.5.0f3
Issue ID
858080
Regression
Yes
When multiple .mb (Maya binary) files are imported, the imported files do not match up correctly with the original files
To reproduce:
1. Open attached project
2. Go to models folder
3. Notice that both models contains same submodels
4. Reimport one_meter_plain
5. Notice that now model contains correct submodels
Actual: Submodels are same on both models
Expected: Both models should have different submodels
Reproduced: 5.5.0p1, 5.6.0b1
Not reproducible: 5.3.7p1, 5.4.3p3
Maya 2016: 5.4 works, 5.5 works
Maya 2017: 5.4 works, 5.5 broken
More info: Affects anyone using native import of Maya/Max/C4D files on Mac and Windows (~10% of active projects).
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- VFX Graph particles are not culled when using URP and Frustum Culling is enabled on VFX Mesh Output
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
Add comment