[SOLVED] Octane crashes on loading big alembic

[Rikk The Gaijin]

I'm having a big problem here. I have a hair simulation done in Ornatrix for Maya, exported in alembic.
The animation has 2800 frames at 60 fps, and the alembic export of the hair alone is 32 GB.
As soon as I import the alembic into octane standalone, it crashes immediately.

A single frame of the hair in alembic is about 28 MB.
I can manage to import about 100 frames of animation in Octane, so around 3 GB of alembic seems fine, but if I go over that Octane crashes.

What's happening here?
Is Octane trying to load the whole file in memory? Isn't the point of alembic to be able to stream huge amount of data?

We are talking about less than 1 minute of animation of a human hair, this thing should be a breeze to render...

[Goldorak]

I'm having a big problem here. I have a hair simulation done in Ornatrix for Maya, exported in alembic.
The animation has 2800 frames at 60 fps, and the alembic export of the hair alone is 32 GB.
As soon as I import the alembic into octane standalone, it crashes immediately.

A single frame of the hair in alembic is about 28 MB.
I can manage to import about 100 frames of animation in Octane, so around 3 GB of alembic seems fine, but if I go over that Octane crashes.

What's happening here?
Is Octane trying to load the whole file in memory? Isn't the point of alembic to be able to stream huge amount of data?

We are talking about less than 1 minute of animation of a human hair, this thing should be a breeze to render...

Yes, alembic should stream frames from disk. I've tested 10-50+ GB .abc exports in SE in the past, so that is how it is meant to work. What happens if you start your render at frame 101 and render the next 100? Does this crash happen after any group of 100 frames being rendered in sequence, or are you not able even able to scrub or load a frame past the first ~100 in the timeline when the project is freshly opened?

[Rikk The Gaijin]

Yes, alembic should stream frames from disk. I've tested 10-50+ GB .abc exports in SE in the past, so that is how it is meant to work. What happens if you start your render at frame 101 and render the next 100? Does this crash happen after any group of 100 frames being rendered in sequence, or are you not able even able to scrub or load a frame past the first ~100 in the timeline when the project is freshly opened?

I'm not able do do anything at all. As soon as I drag the big alembic file in the Standalone interface, Octane crashes immediately.
I'm using v3.03.2b, but it crashes on v2.25 as well.

[Rikk The Gaijin]

Do you have an ftp or something where I can upload the file for you to take a look at?
My Google Drive is only 15 GB

[Goldorak]

Azen can you work this out with Rikk over PM? Thanks.

[Rikk The Gaijin]

Thanks Goldorak, I'll be waiting to be contacted by Azen.

[Rikk The Gaijin]

Her.. Is this gonna happen today or...?

[Rikk The Gaijin]

In meantime, I managed to reproduce the problem on a much smaller scale, so I guess the problem is not the size but something else.
I will send you a PM with two alembic, one has 100 frames and it works fine, and another with 200 frames of the same hair object, and it crashes.

[abstrax]

In meantime, I managed to reproduce the problem on a much smaller scale, so I guess the problem is not the size but something else.
I will send you a PM with two alembic, one has 100 frames and it works fine, and another with 200 frames of the same hair object, and it crashes.

Could you please send me the scene? We will have a look at it as soon as possible. Thank you.

[Rikk The Gaijin]

Sorry abstrax, I forgot to update this thread.
It turned out the problem was not Octane's, but Ornatrix for Maya exporter was exporting only in HDF5 format, and large files on that format are unstable.
I've contacted the devs of Ornatrix and they fixed the issue by adding Ogawa in the exporter. With that no more crash.
Sorry for the trouble.