what's the status on this, btw?
design question: should we output the index of the element from this node (/nodes) to be used in sample index (/evaluate at index), or sample the value directly in this node?
performance is…
@mod_moder you are saying it isn't stable and you can't convert things bad and forth. in that case, why and how to you have these conversion to a hash and from a hash. I'm unsure on the behavior.
may I recommend having two versions of this node like the sample index and evaluate at index, we should have an attribute map node with a geometry input and an attribute map node…
btw how does this work? what does a string turn into? and can you convert a hash into a string? that would be pretty cool. and what would a float look like after it's converted back and forth?
by application examples do you mean use cases or implementation on your part? because I have a lot of use cases.
regarding the design, I don't think the converter nodes should be in the same node as the separate nodes, unless those nodes are renamed to convert node (or the like) and are the conversion to a…
btw, why is the input the the rotation type displayed as an Euler when it takes in a quaternion? (and why is it named simply rotation?)
how to up priority? is there a vote thing, get more participants... or is it entirely up to the developers?
what's the status on this? I don't mean to push, I'm just curious; I've recently had to do some associative transferring (I used the sample nearest method). I remembered this was up for a while…
As you can see, there is a similar behavior for zero size domains. This is so by design, the attribute should always be created if possible. ![image](/attachments/52a63338-265d-4bd0-a614-e177c…
@mod_moder what additional information do you want?