- User Since
- Jul 12 2018, 3:07 AM (219 w, 4 d)
Jun 30 2022
Apr 6 2022
Why would users want to go in “sculpt” mode to do “painting”?
Oct 24 2021
Oct 19 2021
Oct 15 2021
i went a bit enthusiastic too fast. it will trigger an update on change only if the socket is unconnected
just stumble into this
do not forget that
is available to get callback from anything
Oct 14 2021
Oct 11 2021
Sep 27 2021
Hello I'm the creator of Lodify
I'm sorry for the trouble caused here
Sep 24 2021
about the name, my first supposition about this node name is that it would create one point per middle of faces.
so it might mislead few users perhaps?
Sep 22 2021
Jul 3 2021
Apr 6 2021
Apr 1 2021
Mar 31 2021
This task need to be deleted,
Task in standby, math node are nod working with vertex color attr
Mar 29 2021
I believe the issue got fixed in february
Mar 18 2021
Mar 17 2021
Mar 12 2021
Mar 9 2021
Mar 8 2021
Feb 26 2021
Indeed the normal rotation and far away origin are not a good mix!
It indeed makes a lot of sense, once we reset the rotation there's no more patterns
Feb 23 2021
Feb 11 2021
Feb 10 2021
Additional video footage of the problem
After deleting nodes one by one
The phenomenon is still occurring
Feb 9 2021
It seem that unpinning the and re-pinning solved the issue,
(currently pinned geonode stored in "Scatter Object" sorry for the ton of empties in the scene)
Feb 2 2021
Let's not forget about Proximity for Volume,
That could be an extremely useful mode.
Feb 1 2021
From a technical standpoint I completely understand, but from a user standpoint that might create a lot of confusion? Isn't it?
Couldn't geonode instancing node just skip elements with (0,0,0) scale attr?
@Pablo Vazquez (pablovazquez) Do you think we could use such switch node to also switch geometry?
In shader node, we can enable/disable specific path by using the switch by index nodegroup technique, currently impossible in geo node as we cannot "mix" geometry by factor
Jan 30 2021
@Robert Guetzkow (rjg) Shouldn't blender simply ignore geometry with scale (0,0,0) ? it seems completely absurd that an object completely invisible is affecting performance right?
Jan 28 2021
The attr is clearly not being transferred correctly.
We can see in this gif that the object info node is doing the exact same thing from the prior modifier, but the attr is not passed correctly
It may be how the object info node is evaluating the transforms.
Maybe a third mode hybrid to Original/relative would do the job? the problem is that the Relative mode is applying the transforms, how about transfer them?
Jan 27 2021
Jan 16 2021
and since you are deliberately using the same attribute for input and output