Houdini: Alembic Load do not create unpack, normal and null

[BigRoy]

Changelog Description

On Alembic loading to SOPs do not automatically create unpack, normal and null

Additional info

Fixes #253 based on comments by @fabiaserra

Also removed the assignment to self[:] since it's unused.

Testing notes:

1. Loading and managing loaded Alembics should work
2. Managing "legacy" loaded containers should also work
   • They will still have the unpack, normal and null - only newly loaded containers will not.

[MustafaJafar]

It works on my side.
I wonder if we should add output node or null node at the end.
I think it can save sometime for artists.

[BigRoy]

It works on my side.
I wonder if we should add output node or null node at the end.
I think it can save sometime for artists.

I wouldn't do that. We want to provide the minimal. It being the only node inside of it - it's already the "output" and we're also not doing this for e.g. the bgeo loader or other SOPs loaders as far as I know.

Wonder what @fabiaserra thinks?

[fabiaserra]

It works on my side.
I wonder if we should add output node or null node at the end.
I think it can save sometime for artists.

I wouldn't do that. We want to provide the minimal. It being the only node inside of it - it's already the "output" and we're also not doing this for e.g. the bgeo loader or other SOPs loaders as far as I know.

Wonder what @fabiaserra thinks?

Yeah I don't think it's necessary, although it would be good to add support to switch to the context where it gets loaded with the new node selected so it's clear to the artist that something was loaded

[BigRoy]

Yeah I don't think it's necessary, although it would be good to add support to switch to the context where it gets loaded with the new node selected so it's clear to the artist that something was loaded

Ah yes, I think that's a different beast to tackle since currently it loads into the avalon container which (at least for us) isn't a workspace one usually works in, but usually gets object merged.

Anyway, definitely different issue.