วีดีโอ

;)

I'm afraid I don't but when I made this tutorial it began as a windy forest scene I was messing with that I must return to at some point. Though the tutorial I was looking at for that is right here - th-cam.com/video/NMlYf_T9Nb0/w-d-xo.html My specific tutorial was for the process of making all your instances in Houdini as merged packed objects so I could instance them, like for debris.

th-cam.com/video/WOCcT93D0rk/w-d-xo.html actually this one might be easier to follow. I'm going to have a go of it today.

​@@KevRyanCGthank you. I took advantage of having a long weekend and just completed part 3. It seems to be a decent approach, although looking in the comments section there are other folks who think that perhaps it's a bit cumbersome. But I have to say It's very effective. Certainly better than what I've done on my own. There's another gentleman named Josh Weber, who has put out a tutorial regarding animated instances although his tutorial has very poor audio. It's more of a casual mention than an actual structured tutorial. Difficult to follow / interpret.

​@@KevRyanCGha, that's on my list too!

@@tomallen5837 Man I've been on this all day and I can't really figure it out right. Best I did was make an instance set-up in Sops and referencing that in and creating native instances. There's some method with Value Clips that I just couldn't get to work, though I saw it on a sped up video on vimeo and it seems to be the way to do it. Sadly the artist didn't divulge too much more information. I'm going to look into it further then I'll make a video once I find out.

Yeah it's the kind've thing you'd use on particle sims quite a bit, on the volume sop there's a tab that lets you create a volume from your camera which you can use to group points and then delete. Potentially saving on memory at rendertime. But it's also worth looking up fromNDC and creating frustrums from boxes too. I had covered it in this tutorial but clipped it for time. Again, it's incredibly handy stuff.

Ha I don't know, I've been thought to use Houdini in a very script heavy way so my knowledge of constraints isn't up there. Even for a look at I'm finding the position of the object, getting a vector direction and converting that into matrix rotation. Why? Flexing I guess.

Thank you! Yeah it's just handy to have things at SOP level sometimes, and being able to extract and create the euler parameters is good to know too.

@@KevRyanCG Indeed, sir, thank you once again

HA! There is, I said it right at the start, with constraints and stuff. But this is more about learning things via an elongated and silly process that can be applied to other situations. Matrices and Cracktransform tend to pop up when doing any sort of serious Houdini work.

You're very welcome :)

Oh thanks! I'll have a look at that myself, I was having trouble with adding wind having the smoke just getting eaten by the colliders as well.

substeps wouldve fixed it too most likely but if you dont need pixel accurate colliders its not necessary to do over the fill interior

@@SwipeLess For really big geo I just manually adjust it to what I needed by using the interior/exterior voxel band instead of fill interior. It worked better and way faster than adding more substeps. Adding substeps can help, but didnt solve the problem no many how many I added.

@@evanrudefx good that it worked, using volume colliders too with vdb from polygons etc sdf name "collider" and having same voxel amount as the sim itself will be the most accurate way

what if we need to different material for each types of instance object

Yeah that's where I started but it kept hitting walls with the newer Sparse Solvers and so it needed some extra tweaking to get working. I stand on the shoulders of giants! Hell I even did an Entagma Tutorial today for living particles.

Well done! @@KevRyanCG

Ya know, I've not really tried the OpenCL in simulations, my card is a bit out of date and I find it chugs along a bit. But I'll look into it, thanks!

@@KevRyanCG if your GPU memory is low (mine is 12G), you can limit the loop range, size of the simulation, or voxel size , just for quick tweak. And then switch to sparse to cache.

hi, how to do that ?

Oh, absolutely. The framing of this tutorial was for the specific instance of having multiple packed objects, either custom debris or just merged objects that you'd typically wire into the Copy to Points with a variant attribute on the points, as that information wasn't obvious to me from any thing I was reading online. As in having multple objects coming in from SOPs to LOPs from an object merge in a SOP create. But really the power of the instancer comes from being able to reference in objects via USD and by using a similar method with the Collection set-up and dragging objects in, being able to instance them on points using just Solaris. It lets the renderer optimize the data going into it, rather then loading in unpacked scenes of billions of polygons. You're simply telling it here's these few objects, and they go on these points at these sizes and orientations. Try it yourself with something good and hi-poly and see how much you can render.

@@KevRyanCG but you can specify on the sop import how to instance (giving that you did a copy to points packing and instancing the pieces), so is there a benefit in doing so in solaris? I usually have it setup at obj level with a copy to points, pack and instance and then in solaris I just import that specifying "point instance" as the instance setting.

@@brencaaa Ah nice! I didn't know this. I just tried it there on another project I'm working on and it seems to be more or less the same. It's also circumvented an issue I was having with the instancer which kept crashing my scene. So I guess it just comes down to circumstances then. If you just need to do a handy copy to points and have that replicated as is in LOPS then using the Create Point Instancer option is the way to go. But if you wanted that extra bit of control at the LOP level, and to swap things out then at least the instancer is there. I can't remember which tutorial it was but to figure out what I needed I found a video where the guy was using the collections to bring in USD files and basically doing the majority of his work through the Solaris context. It'd be the same idea as folks who never use the seperate MAT or OUT contexts and instead create Material or ROP networks at the obj level, and I've worked with TDs who create nested networks and tools which have a ridiculous level of automation built in thanks to this. Nevertheless cheers for the tip Massimo! I'll be sure to mention it in a future video.

@@KevRyanCG Happy to hear that! I've always did it like that but I was wondering if there where benefits of doing so at LOPs level (coming from Redshift, I was curious to know if it worked like the "rs proxy workflow", basically instancing at render time instead of using packed prims, but it seems not to make a real difference, plus karma is way happier to work with packed prims than Redshift was)

I'm not 100%, but it should work on earlier versions of the Sparse Pyro Solver too. Result might be a little different but it's worth a shot still!

You're very welcome!

Ah yeah I had trouble with this when I was making the video. You have to make sure the volume is correctly named, and that it has the velocity attribute if it's moving. When you add the point.v you should see the collision volume change appearance which lets you know something is there. Then you have to make sure it has the same name on the collision Tab on the solver. I kinda talked a bit too quickly through the Trace Sop for that part. Also it could be substeps if it's passing through or disappearing, something about using wind in the Sparse solver causes the issue. But keep at it and try a few different things and see if it works.

Haha yup, I have another tutorial with the Pighead in Blender too!

I found a carbon Fibre texture online somewhere years ago that I just had in my asset library. Plugged in the maps as you should in the Material but then used the coat to add an extra layer on top. So it looks as if the fibres are below a shiny coat.