Alembic Import Crash

Hi Kestrelm,

I’ve created a ticket for this crash that you can track here: Unreal Engine Issues and Bug Tracker (UE-35551)

I did find that I could make sure your file work by importing it into 3Ds Max and exporting it as Alembic again with all the frames (6750), where as your test asset when imported into UE4 it would only recognize the first 226 samples. I see this is in your first part of your post as well. Not sure if there is a specific reason you had this even though you had more frames.

Regardless, when I export from Max again and specify any range of frames whether it’s 0-6750 or 0-250 things work as I would expect and import fine into 4.13 and our latest internal build. That may be something worth checking on your end to make sure there wasn’t an error there.

The other thing is the test asset only clocks in at 2.10mb but when export all frames I get around 62mb in size. Again, not sure what your full intentions here were, but something seems like it didn’t save correctly with the asset.

-Tim