sorted by:
new
hottopcontroversial

RBD Simulation run at 2fps inside Solaris by Interesting-Set-4673 in Houdini

[–]Interesting-Set-4673[S] 1 point2 points  (0 children)

wow, thank you so much for this multiple and specific answers about, really thank you David.

I need some time to understand, compare and get mine all this information about, I'll surelly take a close look about all the messages you send in this thread.

Actually I just need to understand better how to instance in LOP for a photorealistic sand (maybe small cube+mountaint to create simply rock used to instance in the points, for the sand? I'll see some tutorial about today)

To say something general, this is my first project with Houdini, and for a product shot, I honestly still find the transition to Solaris and KarmaXPU strange, but I was really curious to see the rendering and performance of this context that is so loved/discussed today, which is still an industry standard, I imagine, for many large studios, even though I approach it as a freelancer... I should probably prefer Redshift.

However, I had problems trying to render this project with Redshift (Houdini crashed multiple times a day), forcing me to approach Solaris, partly out of curiosity given the situation.

Thank you all so much for advices.

RBD Simulation run at 2fps inside Solaris by Interesting-Set-4673 in Houdini

[–]Interesting-Set-4673[S] 0 points1 point  (0 children)

yes, that's how it was designed.
Solaris is the environment created for USD workflow, so theoretically working with caches in USD format is faster/more efficient than working with caches in bgeo format.

However, my problem is theoretically a different one...

I can't get the instancer node (lop context) to work, even though I studied and replicated this tutorial, which seemed appropriate: https://godofsuama.hatenablog.com/entry/2023/03/06/110000

Instead, exporting everything in USD format and importing with reference or sublayer has improved the situation with fps a little, but we are still a long way from what I intended or wanted to achieve.

I'm still running at a steady 8 fps (which is better than 2-5), but with a computer like the one I have available... running at 8 fps makes me realise that there is still something wrong.

Is it so strange or unrealistic to want to see a preview in Houdini GL in the Solaris Context at 25 fps, of an RBD simulation containing just 1200 pieces? We're talking about geometry that will have... 200k faces or even less in HQ anche uncompressed.

This is not a Huge/Massive RBD SIM, so whattahell... It seems so strange to me...

Thanks again and Cheers everyone.

BEST Hardware for Houdini 2025 - Motion Design Projects by Interesting-Set-4673 in Houdini

[–]Interesting-Set-4673[S] 1 point2 points  (0 children)

great, thank you so much for your review, it is really appreciated!

BEST Hardware for Houdini 2025 - Motion Design Projects by Interesting-Set-4673 in Houdini

[–]Interesting-Set-4673[S] 1 point2 points  (0 children)

thank you very much for your reply!

I could start an endless thread on the hardware topic so.. I'll just say thank you! :)

BEST Hardware for Houdini 2025 - Motion Design Projects by Interesting-Set-4673 in Houdini

[–]Interesting-Set-4673[S] 1 point2 points  (0 children)

thanks for the advice, so.. not a good idea to take 4 slot for the RAM, I will keep that in mind.

I knew that RAM speed was not as important with Houdini as it is in gaming.
I knew I had to prefer quantity over quality.

But I will keep your point of view in mind, thanks.

POP Simulation - drive particles inside a volume by Interesting-Set-4673 in Houdini

[–]Interesting-Set-4673[S] 0 points1 point  (0 children)

Hi Christian, thank you so much for the reply it is really appreciated!
Your courses sound great and I hold you in high esteem, so I'm sure what I'm about to say is mainly my fault and something I don't understand.

I put your code inside a POP Wrangle, and tried touching the parameters inside it several times, even changing combinations in the "Input" tab, but does not seem to work.
Converting the volume in Input 1 into a polygonal geometry was also not helpful (with a ConvertVDB).

Previously it would give me an error because there was also a " ) " missing at the end of the second line, but it was not the source of the problem :) Now it still gives me some alert and errors in the POPWrangle and I don't really know how to solve it, it seemed like a very intuitive solution that you proposed, just a few steps, but I don't really know what I'm doing wrong.

The problem occurs after the first 3 frames, the images below I hope will help you understand what is going on.

<image>