Alembics and Material IDs

[cam.crichton]

I have a tyCache with three material IDs. The solve looks great and inside Max all of the IDs are correct on the live system and the tyCache.

If I use a tyselect to identify the matID's everything looks fine. If i use a poly select the selection sticks to the frame it was activated on and is incorrect for every other frame - as the point count is changing and it seems to not refresh automatically.

When I export to alembic the matID's are all messed up - as if it is not updating from the initial state.

Has anyone experienced this before and know a solution or workaround?

[tyFlow]

If you send me the Alembic file I can check the data, but unfortunately with the Alembic format you're at the mercy of the importer....and only some importers support dynamic material IDs (IDs that update each frame depending on topology). Older versions of Max don't, and it's possible Maya doesn't either.

If you have VRay installed, try loading the alembic file into a VRay Proxy object and assign your material so the IDs are visible...then scrub and see if they update properly. I've found that the VRay Proxy object is a pretty reliable importer and it tends to properly support dynamic properties.