Page 1 of 1
Alembic "Animator Data" issue
Posted: Mon Mar 29, 2021 1:05 am
by spectacle
I have a .abc fluid sim exported from Houdini imported into Maya. When the Animator Data is set to "don't load" it shows up fine, but obviously frozen at the first frame. When I set it to "force load" it disappears from the render. I tried it with Constant Topology on and off. I've worked around it by importing the .abc in Standalone.
Octane X PR10, Plugin PR8
MacOS 11.2.3
5700 XT
Maya 2020.3
Thanks!
Re: Alembic "Animator Data" issue
Posted: Mon Mar 29, 2021 9:43 pm
by BK
Hello spectacle,
Thank you for reporting this.
Could you please share the alembic file from Houdini?
Cheers
Re: Alembic "Animator Data" issue
Posted: Tue Mar 30, 2021 2:28 am
by spectacle
Re: Alembic "Animator Data" issue
Posted: Tue Mar 30, 2021 4:48 am
by BK
thank you so much Spectacle,
We are able to render the alembic inside Maya 2020.2 with OctaneX vPR8 - 18.25.
Do you have motion blur enabled?
cheers
Re: Alembic "Animator Data" issue
Posted: Tue Mar 30, 2021 4:58 am
by spectacle
Oh interesting. I have tried it with the shutter speed set to 0 and more than 0.
I've attached a video of how it works in Maya for me. With it set to Force Load it is invisible. Once its set to Don't Load it shows up fine.
This is the case for all .abc for me. Maybe I'm missing something, but I know I've done this sort of thing a lot in the past and it's worked fine. Thanks for looking into it.
Update: the other .abc in the shot actually works fine with Force Load. But it has constant topology.
Re: Alembic "Animator Data" issue
Posted: Tue Mar 30, 2021 5:13 am
by spectacle
Ah, so I noticed the issue goes away with I lower my "Frames to pre-cache" to 0.
Re: Alembic "Animator Data" issue
Posted: Tue Mar 30, 2021 5:42 am
by spectacle
The plot thickens...The alembic shows up fine in Maya if I turn the frame cache off, but it doesn't export to an animated .orbx.
Re: Alembic "Animator Data" issue
Posted: Tue Mar 30, 2021 9:29 pm
by JimStar
I have a guess what may be your problem. Will do some workaround in the next version...