Bad Alembic issues
Posted: Tue Oct 15, 2013 1:07 am
Hello again,
There are a few problems with alembic that came up in beta and still seems to be big issues.
1. The transform values from the alembic cache are relative to the existing values at any given frame. If the alembic is moving an object 1 unit starting at world center 0 the movement will put it at 1. If the user moves the unit 1(or any other value) the change will be +1 from that value. The change can not be undone or reset so unless the user knows the original starting point for the object it is impossible to return the object to the perfect, correct starting point. The undo passes over that movement and to whatever was done before that point. That is a very bad problem in any pipeline.
2.Once the alembic node has been moved from its starting point the extra transform is not accounted for during the scene scale. Original location at Geometry scale 1 <<0,0,1>> .1 <<0,0,.1>>, 10 <<0,0,10>>
If the user moves the object that extra transform is handled this way.
Geometry scale 1 <<0,0,1>> changed to <<,0,0,3>> will be very different at other scales.
Geometry scale .1 <<0,0,2.1>> (worse at small scale)
Geometry scale 10<<0,0,12>>
If this can’t be fixed at the very least I would like the option to lock the alembic nodes as done with SD files. Please let me know if there are any questions.
There are a few problems with alembic that came up in beta and still seems to be big issues.
1. The transform values from the alembic cache are relative to the existing values at any given frame. If the alembic is moving an object 1 unit starting at world center 0 the movement will put it at 1. If the user moves the unit 1(or any other value) the change will be +1 from that value. The change can not be undone or reset so unless the user knows the original starting point for the object it is impossible to return the object to the perfect, correct starting point. The undo passes over that movement and to whatever was done before that point. That is a very bad problem in any pipeline.
2.Once the alembic node has been moved from its starting point the extra transform is not accounted for during the scene scale. Original location at Geometry scale 1 <<0,0,1>> .1 <<0,0,.1>>, 10 <<0,0,10>>
If the user moves the object that extra transform is handled this way.
Geometry scale 1 <<0,0,1>> changed to <<,0,0,3>> will be very different at other scales.
Geometry scale .1 <<0,0,2.1>> (worse at small scale)
Geometry scale 10<<0,0,12>>
If this can’t be fixed at the very least I would like the option to lock the alembic nodes as done with SD files. Please let me know if there are any questions.