search

pombreda / alembic

Automatically exported from code.google.com/p/alembic
Other
0 stars 0 forks source link

write visibility problem #261

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
i get a object has keyframes on visibility attribute in maya, 
and export it to alembic format with -writeVisibility option.

when i try to import the abc file back into maya, maya crashes.

i guess this option may not support keyframes on it.
what should i do if there is an animation on visibility attribut?

Original issue reported on code.google.com by cfp.gao...@gmail.com on 23 Nov 2011 at 6:44

GoogleCodeExporter commented 9 years ago 
What version of Maya are you using?

Original comment by miller.lucas on 23 Nov 2011 at 6:48

GoogleCodeExporter commented 9 years ago 
maya 2011 64bit
alembic 1.0.3

Original comment by cfp.gao...@gmail.com on 24 Nov 2011 at 1:08

GoogleCodeExporter commented 9 years ago 
-writeVisibility crashes for me, too (alembic 1.0.3, both on linux and windows).

Curiously, for the scene I tried, it started crashing above a certain frame 
range/file size (?). I tried exporting/reimporting of an animated hi-res 
character rig, for 10, 20, 40, 80 frames, and couldn't import the 40 and 80 
frames versions (40 frames were 798MB, 80 frames were 1.5G).

Might be something else than file size, though... But still, it's interesting 
that it works up to a point, then begin to crash.

I'll try to attach files as soon as I got smaller ones that still crash.

Original comment by tus...@gmail.com on 29 Nov 2011 at 10:14

GoogleCodeExporter commented 9 years ago 
I think there might be a bug in Maya 2011 involving connecting certain kinds of 
attributes.  This works much better in Maya 2012.

Original comment by miller.lucas on 29 Nov 2011 at 5:11

GoogleCodeExporter commented 9 years ago 
i hope this could be fixed soon, maya have not updated to 2012 in my company.

Original comment by cfp.gao...@gmail.com on 1 Dec 2011 at 3:04

GoogleCodeExporter commented 9 years ago 
Unfortunately, we don't currently have the resources to troubleshoot any maya 
2011 issues. We're happy to incorporate any fixes that the community comes up 
with, but this appears to be a maya bug that was fixed in 2012, so we don't 
expect a resolution on this.

Original comment by miller.lucas on 2 Dec 2011 at 5:14

GoogleCodeExporter commented 9 years ago

Original comment by miller.lucas on 9 Dec 2011 at 5:24

GoogleCodeExporter commented 9 years ago 
ok, finally i get a maya 2012, now i am sure it is not maya version's problem. 
try the visibility_test.py under maya/test comes with alembic1.0.3, 
testAnimVisibility function, 
maya 2012 crashes on this MayaCmds.AbcImport(self.__files[-1], mode='open').

Original comment by cfp.gao...@gmail.com on 14 Dec 2011 at 1:33

GoogleCodeExporter commented 9 years ago 
Are you sure you are running your test against Maya2012, and running the test 
suite correctly?

I just reran that test and it passed as expected.

The console output would help.

Original comment by miller.lucas on 14 Dec 2011 at 5:43

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
i solved the problem by removing line 214 in AlembicNode.cpp:
     status = gAttr.addNumericDataAccept(MFnNumericData::k4Double);

it could be a bug in older version maya api, i tried in maya 2013, did not have 
this problem.

Original comment by cfp.gao...@gmail.com on 28 Apr 2012 at 6:20

GoogleCodeExporter commented 9 years ago

Original comment by miller.lucas on 18 Jun 2012 at 5:39