Importing Alembic Meshes to Nuke. Nuke imports Alembic via the āReadGeoā node.
Import your source footage to the nuke project
Create a ReadGeo node
Open the exported Alembic file via ReadGeoās file browser
Change the import parameters if necessary
ReadGeo will then ask how you want to set up the camera and geometry nodes.
You can use the ReadGeo in combination with the Scanline Renderer node to composite warped textures over the top of the original footage:
Create a Scanline Renderer node in the node graph
Feed in the ReadGeo, Camera and Source image into the inputs of the Scanline Renderer node. If you view the node, the mesh should now be correctly projected over the top.
Add an image or material to the āimgā input of the ReadGeo node. This will then project the texture onto the Mesh.
Scrubbing the timeline should show the texture warping to the mesh faces over time.
In Maya your workflow should look something like:
Importing the alembic file
viewing the mesh through the camera
Create a new Background object
Assign a new basic material and assign a material
Import your source footage to the material as a texture
But it has been a long time since I did anything in Maya so donāt quote that exactly. What version are you exporting for Maya? Anything youād export for Cinema 4D for example should come into Maya, I would think.
Let me know if that is still causing issues when you follow those instructions?
The power mesh alembic is now working in Nuke thank you . Maya 2022 however keeps on crashing when I import power mesh alembic file. Note that alembic from houdini works just fine in maya . I not sure what the issues between Mocha alembic and maya 2022/2020 is . Maya script editor spat out this error " PowerMEshPlateDCam.abc is not a valid Alembic file // " .
Same problem here, Alembic from Mocha Pro 9.0.1 crashes Maya 2019, Maya 2020 and Maya 2022. It imports well in Blender though (despite camera being wrongly orientated, which is pretty comon with Blender).
Sure Mary, how? (sorry is this is a dumb question, Iām pretty new on this forum and I canāt find a āsendā or PM button anywhere).
BTW, the Alembic is fine with Autodesk Flame too.
No worries, Iāve just repeated this crash with a separate file, so no need to send the data. Weāll try to get to the bottom of why Maya has a problem with some ABC files and not others.
And for what it is worth, Maya is so buggy and Autodesk really does not seem to fix things. So if possible, do not wait on the Maya team to figure it out.
Interestingly enough, If I run a python script to convert the gpuCache to real geo, the mocha_camera mysteriously appears. Not ideal but it will get me through the day. Alternatively, I believe you can do multiple mocha alembic exports ( not mesh ) and one will have a camera.
Here is the script from Roy Nieterau I used to get regular geo and the camera :
import maya.cmds as mc
Get selected leaf shapes (so we can filter to gpuCaches)
for gpuCacheShape in gpuCacheShapes:
transform = mc.listRelatives(gpuCacheShape, parent=True, fullPath=True)[0]
filepath = mc.getAttr(gpuCacheShape + ā.cacheFileNameā)
# Import everything from filepath and reparent under the transform
mc.AbcImport(filepath, mode="import", reparent=transform)
# Hide the original gpuCache shape?
mc.setAttr(gpuCacheShape + '.visibility', 0)
#(Or delete it?)
#mc.delete(gpuCacheShape)
Thanks for the updates and insight on this @chaney-interport_bfb .
The Autodesk Maya team is still investigating the issue as the ABC files work in other programs. Weāre following spec, so we have to wait to see where the problem is on their end so we can implement a workaround if possible.