Jesper Rahlff
-
Content count
392 -
Donations
0.00 CAD -
Joined
-
Last visited
-
Days Won
10
6 Followers
Recent Profile Visitors
3,554 profile views
-
This seems to be the way to do it. It is a bit complicated for such a simple thing but it works. DeleteVellumParticlesWithConstraints_fix.hiplc
- 5 replies
-
- 3
-
-
- particles
- constraints
- (and 1 more)
-
attached is an example of how it could be done. Keep in mind this is intended to be used with lower contrast images, for bump mapping etc and not a fully blown high contrast brick image. but it gets the point across I think. restratio_flipblend.hiplc
-
so how do I get around this?
-
popadvectfromvolume takes a vel field (from a smoke sim for example) and advects the points through it
-
Hey Guys. I was wondering if there is a way to delete particles in a Vellum simulations when they have had constraints? The scenario I have setup the particles have constraints, then I remove the constraints based on a condition, and when I try to remove the particle as well it craps out on me. Attached is a simple example file to showcase the issue.DeleteVellumParticlesWithConstraints.hiplc Thanks
-
I would say dual rest is quite useful. as stated previously by Atom a lot of the details you want will come from good shading and texturing. Dual rest will help you maintain a crisp look of your bump/ displacement on the surface
-
with a divide sop and a fuse to accompany the bend, I could push it to about 1200 degrees before it broke.
-
Based on your file I was able just to adjust the capture direction slightly to get it to curl up with no intersections. This will break eventually though if you need it to curl alot
-
Reduce Collision Velocity?
Jesper Rahlff replied to Midasssilver's topic in General Houdini Questions
the static object is internally converting v attribute from your incoming geometry to collisionvel even if you specify a proxy volume to sample collision from. In order for you to scale down your collision velocity you can simply just multiply down your v attribute on your geometry before it is sourced in like so: -
pre solve means before the timestep has been solved. Post solve means after the timestep has been solved. In a very simple term you can think of it like this: Before the point has moved, after the point has moved for the given timestep
-
can you upload the hipfile by chance?
-
This is a good starting point? its a Subsurface scattering shader, that has a milk preset you can use. You can put down this material in the /mat context
-
start off with the preset on the physical SSS shader
-
you can also disable the turbulence microsolver in the setup as well
-
The setup you have is pretty good. I tweaked just a few things (I actually just simplified everything a little) and optimized your sim so it runs faster. Attached is the modified file. I copied your geo node and renamed it so you can see the difference between the two. Feel free to ask questions if any may arise. Tornado_JR_v1.hiplc
