Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.2.0a1
2018.2.0f2
Issue ID
1059421
Regression
Yes
Crash at aiContextGetTimeRange in Unity Alembic Importer
How to reproduce:
1. Open the attached Unity project.
2. Reimport a "camera.abc" model.
3. If the crash does not happen, reimport all assets and repeat step nr. 2.
Expected result: The model is reimported
Actual result: Unity crashes
Regression first introduced in - 2018.2.0a1
Reproducible with - 2018.2.0f2, 2018.2.0a1
Not reproducible with - 2018.3.0a5, 2018.1.9f1, 2017.4.7f1, 2017.2.3p2, 2017.1.4p2, 2017.1.0a1
Notes:
- The Alembic importer seems to crash during the import of a particular model when accessing its animation time range.
- Those versions, which are marked as "Not reproducible", only crash if the crash in 2018.2.0f2 has happened before.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment