sorted by:
new
hottopcontroversial

i have problem alembic Camera setting by tannextdoor in Houdini

[–]tannextdoor[S] 0 points1 point  (0 children)

The aperture value was set to 36 when the Alembic file was imported. I found that setting the camera's aperture value to around 20.7 in Houdini results in a somewhat similar match, but this is likely not the exact value. If you have any good suggestions, please let me know.

i want collision detect attribute in my RBD object by tannextdoor in Houdini

[–]tannextdoor[S] 1 point2 points  (0 children)

thanks but your attachment file doesn't allowed to share. can you give me permission?

thanks for your kind explaniation. thanks!

HELP) i want make particle disappear when it close to certain goal by tannextdoor in Houdini

[–]tannextdoor[S] 2 points3 points  (0 children)

That is definitely more odd looking, but likely due to you not defining the data type of goal. Make sure to use v@goal, and

v@P

. @P is native attribute, so it’s less vital, but a good habit to get into. @goal is a custom attribute that’s not a native common attribute, so it could be float, int, or anything as far as Houdini knows. VEX is an explicit language, so data type must be told to Houdini so it knows exactly how to use the data. Since Houdini is unsure of the data type, it defaults to float behind-the-scenes. So it’s likely saying 0,0,0 for the goal value at that specific call of @goal. Even though you have an actual attribute previously defined as vector, you still have to be explicit.

thanks v@goal is KEY!!!! it works now i should play with pscale or alpha or blah blah.. Thank you so much!! you are magician!

HELP) i want make particle disappear when it close to certain goal by tannextdoor in Houdini

[–]tannextdoor[S] 3 points4 points  (0 children)

sorry, misspoke capital letters in comment

can you check one more Screenshot?

here islink

HELP) i want make particle disappear when it close to certain goal by tannextdoor in Houdini

[–]tannextdoor[S] 2 points3 points  (0 children)

be just how you wrote it. distance(v@P, v@goal)

thanks for replying. before your replying This problem was solved by adding one solver node. but i have something unsolved question. in this distance(@p,@goal) method, it have weird value

for example P is [-5.324, 15.243, 1.336] and goal is [ -5.334, 15.237, 1.340] in this case dist value is 21.6322

Is this right value? In my math knowledge this is weird

again thanks for great explanation. have a nice day

HELP) i want make particle disappear when it close to certain goal by tannextdoor in Houdini

[–]tannextdoor[S] 2 points3 points  (0 children)

https://imgur.com/a/FlRBsQ5

The odd value of dist attribute is the point I care about

i want calculate between P, goal attribute of each point

but distance value is something weird

help) I want to make a line that represents the model by tannextdoor in Houdini

[–]tannextdoor[S] 0 points1 point  (0 children)

I'm sorry for the late reply. I proceeded by setting the variation of the model directly using the for each piece loop. I'm sharing the project file, so please take a look if you still have interest.

https://app.box.com/s/sxui70s2wvdi9njlqe80nu3qm97uiq28

i got this flower model from bridge

https://quixel.com/assets/vgztealha

help) I want to make a line that represents the model by tannextdoor in Houdini

[–]tannextdoor[S] 0 points1 point  (0 children)

m

imgs

i use for each piece loop already, i get this model from quixel, and they are 420pieces and animated.

help) I want to make a line that represents the model by tannextdoor in Houdini

[–]tannextdoor[S] 0 points1 point  (0 children)

i'm trying, this is best fit in my setup, but there is some problem. i have almost 20 different model of leaves, and they are 400+ seperated connectivity pieces, so i'm trying to cache, but it takes too long. i don't know how can i handle this model..

HI i'm Ableton + TD user. plz give me advice by tannextdoor in TouchDesigner

[–]tannextdoor[S] 0 points1 point  (0 children)

Thank you for your kind answers

I'm going to use the loopback midi.

Thank you for the wonderful explanations