Re: Alembic sticky memory properties
I ended up deleting it, so I could control it directly with overrrides - thanks for the tip :) Morten > Den 8. december 2016 klokken 20:14 skrev Steven Caron: > > > Yes, its useful for animating visibility of an object. But it can confuse > Softimage a bit when switching passes or overrides. Sometimes it just needs > a refresh. ie. toggle the partition visibility. Of course if you don't need > it, delete it. > > On Wed, Dec 7, 2016 at 12:59 AM, Morten Bartholdy > wrote: > > > Didn't know there could be alembic visibility ops but that was the culprit > > it seems - thanks! > > > > Cheers > > Morten > > > > > -- > Softimage Mailing List. > To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with > "unsubscribe" in the subject, and reply to confirm. -- Softimage Mailing List. To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.
Re: Alembic sticky memory properties
Yes, its useful for animating visibility of an object. But it can confuse Softimage a bit when switching passes or overrides. Sometimes it just needs a refresh. ie. toggle the partition visibility. Of course if you don't need it, delete it. On Wed, Dec 7, 2016 at 12:59 AM, Morten Bartholdywrote: > Didn't know there could be alembic visibility ops but that was the culprit > it seems - thanks! > > Cheers > Morten > > -- Softimage Mailing List. To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.
Re: Alembic sticky memory properties
Didn't know there could be alembic visibility ops but that was the culprit it seems - thanks! Cheers Morten > Den 1. december 2016 klokken 18:57 skrev Steven Caron: > > > Are there alembic_visibility operators on the Visibility property? > > On Thu, Dec 1, 2016 at 1:07 AM, Morten Bartholdy > wrote: > > > I am setting up some passes with imported alembic geometry and experience > > while overriding visibility and switching passes that if an alembic file > > had a raytype or visibility overridden to off in the previous pass, it > > stays that way in the alembics own visibility property even if the override > > is no longer present. > > > > Have anyone here run into something like this, and is there a particular > > workflow or way to fix this? > > > > Currently I have resorted to adding overrides to ensure visibility is on > > where needed, but it doubles the override workload which kind of sucks. > > > > Thanks. > > > > Morten > > -- > > Softimage Mailing List. > > To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com > > with "unsubscribe" in the subject, and reply to confirm. > > > -- > Softimage Mailing List. > To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with > "unsubscribe" in the subject, and reply to confirm. -- Softimage Mailing List. To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.
Re: Alembic sticky memory properties
Are you working on si2015 sp2? or Si 2014 sp2? maybe it's a shader thing. Does the log says something? verbose at command prompt maybe? On Dec 2, 2016 11:45 AM, "Morten Bartholdy"wrote: > Not at the office today so I will take a look on Monday. I have not used > alembic a lot so I am still finding my way around it. > > MB > > > > > Den 1. december 2016 klokken 18:57 skrev Steven Caron >: > > > > > > Are there alembic_visibility operators on the Visibility property? > > > > On Thu, Dec 1, 2016 at 1:07 AM, Morten Bartholdy > > wrote: > > > > > I am setting up some passes with imported alembic geometry and > experience > > > while overriding visibility and switching passes that if an alembic > file > > > had a raytype or visibility overridden to off in the previous pass, it > > > stays that way in the alembics own visibility property even if the > override > > > is no longer present. > > > > > > Have anyone here run into something like this, and is there a > particular > > > workflow or way to fix this? > > > > > > Currently I have resorted to adding overrides to ensure visibility is > on > > > where needed, but it doubles the override workload which kind of sucks. > > > > > > Thanks. > > > > > > Morten > > > -- > > > Softimage Mailing List. > > > To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com > > > with "unsubscribe" in the subject, and reply to confirm. > > > > > -- > > Softimage Mailing List. > > To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com > with "unsubscribe" in the subject, and reply to confirm. > -- > Softimage Mailing List. > To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com > with "unsubscribe" in the subject, and reply to confirm. > -- Softimage Mailing List. To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.
Re: Alembic sticky memory properties
Not at the office today so I will take a look on Monday. I have not used alembic a lot so I am still finding my way around it. MB > Den 1. december 2016 klokken 18:57 skrev Steven Caron: > > > Are there alembic_visibility operators on the Visibility property? > > On Thu, Dec 1, 2016 at 1:07 AM, Morten Bartholdy > wrote: > > > I am setting up some passes with imported alembic geometry and experience > > while overriding visibility and switching passes that if an alembic file > > had a raytype or visibility overridden to off in the previous pass, it > > stays that way in the alembics own visibility property even if the override > > is no longer present. > > > > Have anyone here run into something like this, and is there a particular > > workflow or way to fix this? > > > > Currently I have resorted to adding overrides to ensure visibility is on > > where needed, but it doubles the override workload which kind of sucks. > > > > Thanks. > > > > Morten > > -- > > Softimage Mailing List. > > To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com > > with "unsubscribe" in the subject, and reply to confirm. > > > -- > Softimage Mailing List. > To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with > "unsubscribe" in the subject, and reply to confirm. -- Softimage Mailing List. To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.
Re: Alembic sticky memory properties
Are there alembic_visibility operators on the Visibility property? On Thu, Dec 1, 2016 at 1:07 AM, Morten Bartholdywrote: > I am setting up some passes with imported alembic geometry and experience > while overriding visibility and switching passes that if an alembic file > had a raytype or visibility overridden to off in the previous pass, it > stays that way in the alembics own visibility property even if the override > is no longer present. > > Have anyone here run into something like this, and is there a particular > workflow or way to fix this? > > Currently I have resorted to adding overrides to ensure visibility is on > where needed, but it doubles the override workload which kind of sucks. > > Thanks. > > Morten > -- > Softimage Mailing List. > To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com > with "unsubscribe" in the subject, and reply to confirm. > -- Softimage Mailing List. To unsubscribe, send a mail to softimage-requ...@listproc.autodesk.com with "unsubscribe" in the subject, and reply to confirm.