.hbjson too large for 32-bit reader

Question

.hbjson too large for 32-bit reader

Opened this issue 2 years ago · 8 comments

Doing stress tests for a show and I'm hitting limits on the numbers/length of the cache I'm importing ( not a real time project.)

On import it fails with this message:

LogStreaming: Error: File 'XXXX.hbjson' is too large for 32-bit reader (50484506577), use TArray64.

Saw another user with same issue on the sidefx forum.

I can supply an example cache but I'm sure anything large enough will trigger this message.

UE5.1.1, win 10

Thanks!

Answer 1 · 2023-03-10T06:25:29.000Z

I am having the same Issue with large caches.
Also noticed that writing .hbjsons in Houdini gets really slow with increasing particle counts. Any chance this could work with sequences? Which would also solve the problem with large files.

Answer 2 · 2023-04-01T10:35:24.000Z

having the same issue on my end. i did try to import the .hbjson on 5.0.3 and it worked. there has to be something wrong with the importing method on the current version of 5.1.1.
the best i would suggest would be to create your scene in an older version of UE and reimport the niagara files directly. let's hope it gets fixed soon.

Answer 3 · 2024-06-08T08:50:29.000Z

Have you found a solution to this problem? I have same issue on my project. I have imported large hbjson file, but the Output Log says "File XXX.hbjson is too large for 32-bit reader, use TArray64"

I also did try to import it on 5.0.3 but it didn't work either. Why this plugin import particle caches into 32-bit array? I cannot understand why...

Answer 4 · 2024-06-08T21:54:51.000Z

We never found a solve that allowed us to use niagra caches. We went with a different approach using PCG in 5.3 that worked for our use case ( large animated set of instanced geo ).

Answer 5 · 2024-06-14T07:19:54.000Z

We never found a solve that allowed us to use niagra caches. We went with a different approach using PCG in 5.3 that worked for our use case ( large animated set of instanced geo ).

Can you explain your use case in more detail?

Answer 6 · 2024-09-03T03:36:39.000Z

I am running into the same issue. Did someone find a solution to this?

Answer 7 · 2024-11-11T13:51:29.000Z

We have the same issue in our team.
Looking at the source code of the plugin it seems that to fix this issue it would unfortunately require to revrite quite a bit of the plugin to use TArray64 instead.

Answer 8 · 2024-11-12T06:46:17.000Z

I have still not found a solution. I have opened a ticket to the SideFX support but they told me they will get back to me when an updated will be available…which is probably not going to happen anytime soon. So annoying!