Search Issue Tracker
Won't Fix
Won't Fix in 2.3.X
Votes
0
Found in [Package]
2.2.0
Issue ID
ABC-51
Regression
No
[Alembic Exporter] The resulting animation after export is 1 frame off compared to the original file
Given the attached file (backflip.abc)
Setup the scene so a recording of the attached file will trigger when pressing play. Recording for 100 frames will be enough.
Open the result .abc file in the scene. If needed, put both original model and the recorded model at the same position in the scene.
Notice a little offset as if some frame was skipped at the beginning of the recording. Note that if you uncheck the "Ignore First Frame" checkbox, the offset will still occur.
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
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
- The layout system is failing to correctly calculate or apply the height of the Japanese fallback font when the primary English font's metrics are used
Resolution Note:
There are no fixes planned for this Bug
Resolution Note (2.3.X):
Can't reproduce the issue in 2023.1.0a21.
I can repro the issue in 2021.3.1f1 but it doesn't happen anymore in 2023.1.0a21 when using the same version of the Alembic package.
This sounds like it was an issue on the trunk/unity side. Usually it would be nice to understand what was changed but this bug was reported more than 3 years ago by Joel (then Alembic QA) and never brought up by any "real" user afaik.
Because of this I'm closing it as "Won't Fix". We can re-assess if a user ever brings it up again.