We need some kind of example so that we can reproduce this and understand what to fix. Can you also check the GPU Subdiv option?
Hello. The paragraph describing the steps is needed precisely so that we understand what needs to be done. If this will have a random factor, this is our fence to check many times. But what…
You attach really big video...? I can't open/download that
Can you tell if it ever worked?
It looks like a limit on the number of attributes. But the error message in the console doesn't hint at that...
Does this report still need to be sorted, or has it gone into investigation from the developer?
I did this to be able to get the node as a constant. Though maybe I can get out with something like ListBase * const lb;
Does this mean that it is possible to have a different function signature for declaration (without constants) and implementation (with constants)?
About groups. 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…
Traversing neighbors in order, with a field callback for each i-other pair, and the ability to return an array of indices would be the most general solution. Though that would be a mega node given…