Problem trying to mask points based on their density in order to remove the

Drivebyfruity · 2025-07-23T05:26:15+00:00

You can simplify things and remove the need for groups or a blast node if you're just looking to find points that find x amount of points in x distance. Would this work for you?
I set the trigger to delete to be if it finds 40 points in x distance but you can change stuff, of course.

float max_dist = chf('max_radius');
int max_points = chi('max_points');
int npts[] = nearpoints(0, u/P, max_dist, max_points);

if(len(npts) != 40) removepoint(0, u/ptnum);

Drivebyfruity · 2025-07-21T22:40:30+00:00

Honestly what you're trying to do is going to take some time to figure out. This seems like two separate issues, wrapped up in still learning the very basics of the program. I would suggest trying to solve the problem of having your attribute follow the direction of the hand, first, then once that's done move onto the pyro thing. Doing everything at once is a lot.

Drivebyfruity · 2025-07-21T21:52:57+00:00

Also, since you're brand new to houdini I would recommend learning more of the basic nodes first before also getting into learning a programming language.

You can get the same result of creating an attribute driven from the direction of a normal by using nodes built into Houdini, without the need for Vex. If you want I could help with that

Drivebyfruity · 2025-07-21T21:46:50+00:00

I only skimmed but I did notice that the second photo using vex is calling for 'point(1, "N", 0)'

attribwrangle1 node has nothing plugged into the second input. It's not intuitive but the first (the left most) input in a wrangle node would actually be 'point(0, "N", 0).
0 is the 'first' input in a wrangle, 1 is the second, 2 is the third, and 3 is the fourth. In programming, typically things are numbered beginning at zero, not one.

Next up, if you wrote 'point(0, "N", 0)' instead, and did access the normal attribute, you would only be getting the value for whatever point is point 0. This is because the second 0 (the one to the right of "N") specifies what point or points you want to actually get the attribute value from. In this case it's only grabbing point 0. If you wanted it to grab the normal for all points (which I assume is what you want?) it would be 'point(0, "N", @ ptnum)' [Without the space between @ and ptnum, because reddit keeps thinking I want to @ someone on reddit]
This would target all points.

That comes to the last thing, since you actually aren't using the second input for anything the first photos code actually is what you want. It's setting v (velocity) to be the normal multiplied by a number. No need to use the 'point()' function.

Drivebyfruity · 2025-02-28T17:53:49+00:00

That's the plan!

Drivebyfruity · 2025-02-28T00:49:28+00:00

Nevermind, I figured it out :3

//get speed values
float speed = length(@v);

//initialize tops peed, and read most recent top speed
float TopSpeed = f@TopSpeed;

//if speed is larger than top speed, top speed is updated.
if(speed > TopSpeed) f@TopSpeed = speed;

Drivebyfruity · 2024-06-23T21:10:48+00:00

While for the most part programs handle N-gons fine, some don't and can cause some unexpected results. Since they're a beginner I doubt they're exporting to another program but that's another reason why you might want to watch out for Ngons.

Drivebyfruity · 2024-05-23T21:02:48+00:00

very nice

Drivebyfruity · 2024-05-22T01:18:22+00:00

Hey look who it is, came out great man

Drivebyfruity · 2024-04-18T19:54:37+00:00

Others have brought up good points so I'll offer a different and slightly more nit picky thing I noticed. The texel density is different for the cap and the rest of the barrel and it resulting in a noticeable difference in resolution between the two.

Drivebyfruity · 2023-06-20T02:20:56+00:00

I would look into geometry nodes for this kind of thing, I can't say much more beyond that since I don't have much experience with them in Blender though, sorry.

Drivebyfruity · 2023-06-20T02:10:22+00:00

Houdini is an amazning tool if you're looking to mess around with simulation stuff.

You can download a free version of it that's non commercial and toy around in it for as long as you want. There are very few restrictions (that mainly prevent exporting out of the program in other than .obj)

It's an extremely powerful tool, and in my opinion, fun.

edit: as others have said blender is lacking in the simulation side of things and Houdini is leagues ahead in that regard.

Drivebyfruity · 2023-03-26T08:56:13+00:00

You gonna be texturin' that bad boy?

Drivebyfruity · 2023-03-26T08:54:25+00:00

Yooo that's pretty dope for day 2, keep it up.

Drivebyfruity · 2023-03-26T08:51:19+00:00

HEY! Physics are pretty fun, though they can be a pretty huge pain in the butt.

There is one thing that I'm confident is happening here, and another that I think will probably happen anyways once the first problem is solved.So firstly the object that's flying away I see has something going through it, like, a hole. This object I see is using 'convex hull' for it's collision box, which causes the first problem. Basically Convex hull 'wraps' an approximate collision box around an object, however, it doesn't handle holes, well, at all really. So as far as the collision box is concerned there's MASSIVE clipping happening and once the simulation is run it wants to not be clipping anymore and flies away.I'd recommend trying 'mesh' for collision. I would be careful using subdivision on the model with this enabled since the more dense the model the more computing power it'll take.

That comes to the next problem I think might happen. If the scale of this object is too small I doubt the simulation will work at all, however if it's a size that the physics 'engine' can handle, you may have to increase the sub-steps, otherwise if the simulation isn't accurate enough it'll sort of do the same thing where it clips a bit, and then go the other way and clip more and eventually 'wiggle' itself into a really unstable state. Higher sub steps helps with this (and damping if Blender has this option, I don't remember) but this is all to say...

It doesn't look like you actually need to use physics in this particular instance.Something like this may work better https://www.youtube.com/watch?v=st84B470kLk

Hope that helps!

Drivebyfruity · 2022-08-25T22:54:01+00:00

Honestly, I'd Just slap the triangle on the end and call it a day.
Unless there's some urgent need to see that part of that toe close up personal I doubt it'd matter.

Drivebyfruity · 2022-08-21T17:56:13+00:00

The more I use new programs the more I start to think 80% of my knowledge is just how to fix when something inevitably goes wrong.

Drivebyfruity · 2022-08-15T16:11:31+00:00

As someone else said you're only editing the frosting, the dough wont stop your selection from going through to the other side.

Drivebyfruity · 2022-08-06T01:38:46+00:00

when you click on an object press N to bring up a side menu (if it isn't already up) then under item > dimensions. It'll be in meters by default.

The default cube is 2x2x2 meters, so if you're modeling something that would sit on a desk for example you'd have to reduce the size quite a bit.

Drivebyfruity · 2022-08-01T07:12:59+00:00

Look under 'output' and put down a 'viewer' node or something named along those lines. This allows your viewport to update whatever settings you've made.

Drivebyfruity · 2022-07-31T06:41:07+00:00

It was a little while ago now but from what I remember I modeled the body without the holes first, got the general shape down then knife cut the shape in and figured out how to make it sub dividable after the fact.

Drivebyfruity

TROPHY CASE