I found an issue. this adds more width to collapsed node per i/o that is not exposed. see:
i think this UI element would be useful for sample nodes, which have two context (e.g. the raycast, sample nearest, sample index, etc.), so visually distinguish what inputs come from the context…
Btw, is it possible to get a menu option on the menu switch, so i can use a menu to switch between other menus?
to clarify. it's not working now. that version still doesn't work, but the aphas afterwards do. so I don't think I was a one time glitch. maybe the built bot built it wrong or something else.…
@ChengduLittleA I checked the temp folder and i didn't see anything. but the new alpha works so if no one else reported anything then i…
Seems fine here. Did you accidentally download the arm64 version instead of x64?
No, I'm sure I downloaded the x64 version. I original encountered this problem through steam, where I get…
@mod_moder I added a .blend file.
I mean .blend file.
okay, I'll do that later.
the result shouldn't change if I am sampling it or whether it's constant. (this is only an issue on the spline domain, remember. )
I can not reproduce issue. Mainly due to random value node. Please, add simple example file and describe certain cases that looks like bug.
I did add a simple example. see the second video
I see that the inverse option would be very useful. That is, don't look for the nearest one in group A, as the search is for group A, but look for all of non-A, for every A. But this only makes…
This quet unrelated, but limited by lists of strings (attribute names).
what I had in mind was something that would interpolate captured attributes aswell, not just named attribute.
is…
I don't think this really makes sense for subdivision; subdivision is suppose to output only quad topology. and your example only shows how the triangulated result looks, how about not triangulated…
how about smoothing out the rotation over a surface that would otherwise have a jagged rotation. as potentially use case 🤷♂️.
I second that.
what is holding this node back. is it just that no one got around to it, or are there concerns about the node?