Closed GoogleCodeExporter closed 8 years ago
Could you provide a simple scene which has this data filled in?
The approach isn't terrible, but will only work without any hints in a Maya to
Maya workflow. motionVectorColorSet is being written out as an arbitrary
geometry parameter, and not as velocities on the mesh.
Original comment by miller.lucas
on 10 Feb 2012 at 12:57
Hello Lucas,
From further study it looks like I'm just dealing with a special case, page 14:
http://www.realflow.com/documentation/realflow-maya.pdf
It looks like there's some kind of workaround being applied and not storing
motionVectors as an attribute, it would explain the crash. I tried sampling at
0.5:
AbcExport -j "-sl -uv -wfg -fr 26 70 -step 0.5 -file c:/temp/motion.abc";
It doesn't crash but it doesn't render them either, so I guess I'll need to
work with some other solution, ideally I think realflow should add alembic
support. :)
I can send you the abc but I think the realflow plugin does something weird,
should I send the -step 0.5 abc or the -a motionVectorColorSet? (btw the new
velocity in 1.0.4, is that exposed yet and if so, can I enable it somehow?)
Original comment by alex.ful...@ambiencedigital.com
on 10 Feb 2012 at 1:27
Hello Lucas,
After further investigation I noticed the -wfg flag was set, removed that and
kept -step 0.5 on there and let realflow calculate the subframes and now
alembic exports correctly, and also renders a motion vector pass correctly, so
I didn't need to extract any motion vector attributes.
Sorry about this, it works well now thanks for the reply.
Original comment by alex.ful...@ambiencedigital.com
on 13 Feb 2012 at 12:02
Original comment by miller.lucas
on 14 Feb 2012 at 2:34
Original issue reported on code.google.com by
alex.ful...@ambiencedigital.com
on 10 Feb 2012 at 12:37