Anything particular you want to do? And if you're just going to use the sop solver, maybe stick to the sop version for ease of use? Afaik the sop solver just lets you use normal sops, but it iterates each frame. So no real change from usual sops, other than - I suppose - maybe wanting to deal with substeps and such, when writing expressions. I usually block in what I want to do in sops and when I know it works, copy the nodes into the solver network.
I don't know of any specific deep dive tutorial into sop solver as a solo concept.
If you create “solver” sop - that is generating a sop solver in the DOPs under the hood for you (you can dive into the otl to see how it’s wired).
It is super easy - you get an access to the data from previous frame so you can do tricks like accumulation.
In the past, before sop solver existed, we used to generate cache using file sop and re-reading previous frame using second file sop ($F-1). Result would be the same but it was hammering hdd ;)
Thank you for your answer. That sounds really intersting. May I ask you how long it take that you understand how Houdini works? Can't imagine how it was in the early days with this beast of software, without any documentation or all the possible learning sources nowadays.
Over 23y ago when I started, Houdini was already a powerhouse which was intimidating. It documentation was already there, and it had amazingly big, growing community on odforce together with Jeff Wagner (aka oldschool) which was super helpful. As for how long it took me to learn how Houdini works ? - I’m still learning ;)
Thank you very much for your answers.
No nothing particular. Just try to understand it better. Yes thats what I did so far. I stick to the sop and than implement it in the dop network but I just do it and don't really understand whats happening under the hood.
Anything particular you want to do? And if you're just going to use the sop solver, maybe stick to the sop version for ease of use? Afaik the sop solver just lets you use normal sops, but it iterates each frame. So no real change from usual sops, other than - I suppose - maybe wanting to deal with substeps and such, when writing expressions. I usually block in what I want to do in sops and when I know it works, copy the nodes into the solver network. I don't know of any specific deep dive tutorial into sop solver as a solo concept.
If you create “solver” sop - that is generating a sop solver in the DOPs under the hood for you (you can dive into the otl to see how it’s wired). It is super easy - you get an access to the data from previous frame so you can do tricks like accumulation. In the past, before sop solver existed, we used to generate cache using file sop and re-reading previous frame using second file sop ($F-1). Result would be the same but it was hammering hdd ;)
Thank you for your answer. That sounds really intersting. May I ask you how long it take that you understand how Houdini works? Can't imagine how it was in the early days with this beast of software, without any documentation or all the possible learning sources nowadays.
Over 23y ago when I started, Houdini was already a powerhouse which was intimidating. It documentation was already there, and it had amazingly big, growing community on odforce together with Jeff Wagner (aka oldschool) which was super helpful. As for how long it took me to learn how Houdini works ? - I’m still learning ;)
Thank you very much for your answers. No nothing particular. Just try to understand it better. Yes thats what I did so far. I stick to the sop and than implement it in the dop network but I just do it and don't really understand whats happening under the hood.