So I had some initial success with an alembic export out of C4D, but would seem the texture breaks and doesn’t map correctly whereas it was before. It’s some difference between using a TextureSample vs Texture Object node fed into everything - that and my ignorance on the WorldPosition node varieties that tell the UVs what to do.
Could also be import settings with alembic as well but haven’t had time to test those, just going over in detail the UV side of UE5 and how to get it working on animated meshes vs static meshes which there is lots of documentation about.
Will post on other relevant threads I also commented on, after much testing everything I know of I figured out something that seems to fix this issue. Issue is an import one apparently via UE’s alembic import window settings - needed to change the Compressed Texture Coordinates Number of Bits setting from 10 to 30, which seemed to drastically increase the resolution of materials displayed on moving alembics and solve my issue.
It’s weird in that, again, few people seem to have an issue with this when texturing and don’t need to change any settings at all on the import for alembics - as far as I can tell my alembic export from C4D is pretty standard, 5gb-ish about and nice subdivs but not anything out of the ordinary. Made a video documenting this so hope it helps somebody:
