(Fixed) (Closed) [HOU-1462] [HOU-1512] Possible Bug - Can't Render Packed alembic file

[stevejjd]

Hi guys,
I just noticed that there could be a possible bug.

I have an alembic file that’s quite complex, so I like to pull it apart, assign attributes then pack it. But I found that the latest nightly build doesn’t render packed primitives.

You can re-produce this bug by following these steps:
- Import the same alembic file twice
- Translate the alembic objects so they stand side by side
- Make one Packed and the other Unpacked
- Only the Unpacked one renders.

Is this a bug?

Windows 10
Houdini 17.5.360
VFH [Info] * Build number:6138 hash:08b56ea from 03 Jan 2020 05:03
VFH [Info] * V-Ray 4.30.00

Thanks.
Steve

[psanitra]

I just tried today's nightly with 17.5.460 they way you described and both render fine together. Probably best if you send the abc file and hip to support

[stevejjd]

Thanks for taking the time to veryify that.

[chakarov]

Hello stevejjd , can't reproduce it on my side. Can you send me a scene?

[stevejjd]

Im so sorry for my late reply. It happens with any Alembic file. Please dont worry though. I will just continue on.

[Gosho.Genchev]

It happens with any Alembic file. Please dont worry though.

I also checked on my end - I can't reproduce the issue either. I suspect it could be the alembic file itself causing this - could you please try with a simple sphere exported as ABC and brought back as described in your first post ?

Cheers!

[chakarov]

Is your alembic file exported from Blender?

[stevejjd]

Hi guys. I was able to work without this issue by exporting a cube from maya as alembic. It renders as a packed object. There must be a problem with my other alembic file.

The model was exported from Maya as an alembic.

[Gosho.Genchev]

I see. In that case, would you mind sharing the file so we can check what the issue is and hopefully fix it? It won't be shared under any circumstances. You could directly mail me or support@chaosgroup.com

All the best!

[Gosho.Genchev]

stevejjd , there was indeed a problem present. It wasn't the alembic file itself but the naming - the V003 part was incorrectly parsed as a variable (for example, $F4) instead of kept as is.

It was resolved on Jan 10 so builds starting from Jan 11 should render as expected.

Cheers!

[stevejjd]

Oh thats great, we fixed it. Sorry for my delay, I could have been a bit faster but I got bogged down with some Mari issues. No worries