Alembic crashes in Nuke

377 views
Skip to first unread message

Jedidiah Mitchell

unread,
Nov 28, 2016, 12:18:17 AM11/28/16
to Brekel Kinect
Hello,

First off just want to say thank you for writing such a great piece of software. You've really built something impressive and I'm going to be putting it into production on some VFX projects very soon. 

Anyway, my question relates to Alembic imports in Nuke (9.x & 10.x). When I import with a ReadGeo node I get a proper file interpretation of the .abc exported from Pointcloud (i.e. it shows the internal Alembic structure in the Nuke properties tab), but when I connect that node to a viewer Nuke instantly crashes. 

Have you seen this behavior elsewhere? In Maya the same .abc imports fine and plays back well, and OBJ sequences display successfully in Nuke. 

Thanks!

Jedidiah Mitchell

unread,
Dec 5, 2016, 1:07:52 AM12/5/16
to Brekel Kinect
Actually, I have more to add to this -- 

Both Alembics & OBJ sequences are exhibiting the same error (fatal crash on playback) in Maya WHEN I use the "Resync Dropped Frames" feature to reconstruct shots with frame drops. If I leave the files un-synced they mostly import to Maya without issues (still no joy in Nuke). What could be happening in the resync process that's causing it to create invalid geometry? 

Thanks!

Jedidiah Mitchell

unread,
Dec 5, 2016, 1:16:04 AM12/5/16
to Brekel Kinect
Actually, I stand corrected -- I had a good couple hours of this working, but now all Alembic & OBJ imports from Brekel are crashing Maya. 

Ever seen this issue before? I can give you machine specs or whatever you like, but this is happening on at least 2 systems. 

Thanks!

Brekel

unread,
Dec 5, 2016, 4:51:56 AM12/5/16
to Brekel Kinect
I have seen Maya become unstable when using Viewport 2.0 with Alembic files, especially when they contain geometry that varies vertex/poly count per frame.
May have something to do with it's internal aggressive caching mechanism.

Jedidiah Mitchell

unread,
Dec 5, 2016, 11:47:29 PM12/5/16
to Brekel Kinect
I think I responded to this by email this morning by accident, but just to put it on the Google Groups for future reference: yes, Viewport 2.0 appears to be the issue. I still have more testing to do on different systems to say for sure, but it immediately fixed several files that were unuseable. Thanks for the tip! 

Jedidiah Mitchell

unread,
Dec 7, 2016, 12:14:06 AM12/7/16
to Brekel Kinect
Updating for future readers: with Viewport 1.0 re-activated in Maya I'm importing multiple 3000+frame alembics from multi-Kinect setups without issues. They aren't quite "scrubbable," but not bad at all! 
Reply all
Reply to author
Forward
0 new messages