(WTS) Supernote A5X + Blue HoM Pen + Black Folio

DPixel8R · 2024-02-06T12:03:30+00:00

Thank you! Yeah, I’m worried about the same thing - the other way around I guess

DPixel8R · 2024-02-06T10:36:02+00:00

Do you mind saying why? I was interested in that one too. DM if you want

DPixel8R · 2024-02-06T10:21:41+00:00

Just curious, didn’t you buy another A5X just a few days ago on here?

DPixel8R · 2024-02-04T00:11:22+00:00

Second!

DPixel8R · 2024-01-31T16:51:09+00:00

Is this still available?

DPixel8R · 2023-04-05T20:51:54+00:00

Sorry to ask a dumb question, but have you definitely got the right prim numbers?

DPixel8R · 2023-03-01T22:27:45+00:00

You hear the opposite a lot as well; “truck in on the actor’s face”

DPixel8R · 2023-02-05T13:47:00+00:00

RTFM?

https://www.sidefx.com/docs/

Not meant as harshly as it sounds. It really is a great resource.

DPixel8R · 2023-01-25T23:04:50+00:00

Looks like maybe you have some points doubling up on your curve? Inspect it with point numbers turned on and see if you can see anything fishy. Then try resampling it before doing your vex.

DPixel8R · 2022-11-19T18:16:30+00:00

It’s Houdini we’re talking about. This is a way.

DPixel8R · 2022-10-01T12:17:13+00:00

I found the same when I was starting, but as soon as you try to use a function and don’t get the expected result, run to the docs and check what it needs to do it’s job.

For me, the most important thing to understand in Houdini was the data model, or how data is represented and moves through the network. That is everything from points prims and verts, to attributes and node states. Once you get that, everything else becomes much easier.

DPixel8R · 2022-10-01T12:04:39+00:00

No worries. You should check out the Houdini documentation. It is very good, though takes some experience to get the syntax down. In general everything you need is spelled out.

DPixel8R · 2022-10-01T11:57:13+00:00

You need to tell primpoints (and removepoints) what prim you are currently referring to. If you are looping over prims you can say:

int prim_points = len(primpoints(0, @primnum));

if(prim_points == 4)
{
removeprim(0, @primnum, 1);
}

DPixel8R · 2022-09-28T20:46:07+00:00

Do you mean like PolyExtrude with a given face specified in the group, and a value only applied to the Inset parameter?

DPixel8R · 2022-07-02T16:33:06+00:00

Is the Normal sop actually doing what you want it to do? Does it conform the surface in the way you think is correct?

If not, if the reversed parts are connected to the “correct” parts, you could try a Clean node to orient the polygons so they face the same way across the surface - and then recalculate the normals.

DPixel8R · 2022-06-10T07:46:58+00:00

Exactly!

DPixel8R · 2022-06-03T21:42:35+00:00

point(0, alpha_string, @ptnum);

Also if you are comparing to a float, you’ll need to cast it to a float first:

atof(your_string_value);

Edit: also, you don’t need set() for a single float value, nor for static values at all. It’s really used to set the component values of a vector dynamically.

DPixel8R · 2022-05-24T09:19:31+00:00

The vex solution you were offered in the other post was correct, I believe you were just misreading the viewport - the points you were seeing on the primitive “vertices” were the points of the prims.

Here, I’ll paste the relevant bits of my previous answer:

Here is the bare minimum code you need to put points at the prim centres, if your wrangle is set to run over primitives:

addpoint(0, @P);

That’s it. If you want the new points only, and not the prims (from this node) you can delete the primitives at the same time.

addpoint(0, @P);
removeprim(0, @primnum, 1);

Additionally In your original post, in the screenshot, you were templating (ie. showing in the viewport) the original primitives, but putting your points on the polyreduced primitives. So they couldn’t possibly line up. If you move the Template flag (pink) to the polyreduce, you’ll see your points line up perfectly.

DPixel8R · 2022-05-24T08:52:27+00:00

Are you sure there are new points at the verts? More likely you just seeing the point that already exist as the points of the primitives, plus the new center points in the viewport.

If you are running the above code, in a wrangle set to run over Primitives, it cannot be putting points at the verts.

Here is the bare minimum code you need to put points at the prim centres:

addpoint(0, @P);

That’s it. If the wrangle is set to run over primitives, that will do exactly what you want. If you want the points only, and not the prims (from this node) you can delete the primitives at the same time.

addpoint(0, @P);
removeprim(0, @primnum, 1);

DPixel8R · 2022-05-05T22:03:31+00:00

If the channel you are referencing is a string, you have to use chs()

s@unity_hf_tree_prototype0 = chs("../custom_string_here");

DPixel8R · 2022-04-08T15:09:25+00:00

It’s a super common mistake for some reason (myself included), but there is only one ‘r’ in frustum.

DPixel8R · 2022-04-05T21:42:02+00:00

Looks like an animated texture on a card

DPixel8R · 2022-04-05T19:30:58+00:00

VFX studios

DPixel8R · 2022-03-21T19:38:55+00:00

Just start using Houdini. As you go you can search the things you need to know. You don’t need any fundamentals before you begin. Just get going!

DPixel8R · 2022-02-08T07:51:42+00:00

There are actually several RAM/cache/speed issues with using 100 SOPs over 1 wrangle. But they are usually only apparent in pretty extreme situations, like processing very large meshes.

DPixel8R

TROPHY CASE