Previous one solution was actually right one. One of the most wrong use case of Repeat Zone nodes is to create this kind indices. Users actually should use node groups with just one `0123456789` instance geometry and instancing on points with using math to pars values to indices of digits. This is such both for performance reason (just computing of indices much faster than overhead of repeat zone) and for memory usage (we do not reuse the same digit geometry in instances for different calls of `String to Curve` node).
Definitely agreed that this is not the best use case and hacky and under-performative. Yet, it makes it more accessible than the "better and morea appropriate" way
It's working fine for me. But if needed, why not use Blender 3.6 LTS in this case? Clearly not all new functionalities can be enjoyed, but if I encounter large problems then I try to work in a previous version
@@UHStudio idk xd it crashed for me for some simple stuff when i went n repeated the stuff with 3.5 it worked well but if u saying it work well for u i might give it a Secend chance maybe there was something wrong with my projects n i didnt notice after all its not that hard to crash blender I appreciate u responding
Value to String node should have a field input to feed it vector of data, not just single value. I like SVERCHOK nodes for this sort of things. I always found the vectorization in SV a little bit easier to understand than GN fields. Also SV has a Viewer Index node which does this vertex index magic with just one noodle :) you can easily display indices for vertices, edges and faces... and of course you could get fancier with the text viewer node if you want to customize the text to be other than just an index value. I hope Blender/GN will get better at doing these sort of “simple” things like visualizing the indices in the viewport. Loops (albeit parallel) may not be the best way to handle this sort of things. I wonder why not make this font/string combo a field based instead of a single value.
Previous one solution was actually right one. One of the most wrong use case of Repeat Zone nodes is to create this kind indices. Users actually should use node groups with just one `0123456789` instance geometry and instancing on points with using math to pars values to indices of digits. This is such both for performance reason (just computing of indices much faster than overhead of repeat zone) and for memory usage (we do not reuse the same digit geometry in instances for different calls of `String to Curve` node).
Definitely agreed that this is not the best use case and hacky and under-performative. Yet, it makes it more accessible than the "better and morea appropriate" way
awesome vide but please, if you're showing us a node interface, make it bigger on the screen :(((
The "Sample Index" node is a bit more straight forward here (and probably more efficient) compared to using attribute statistics.
good point!
really amazing! thank you for sharing! :)
Cheers! Happy to help
Blender 4.0 is super unstable
Crahes in simple projects
How r u working with it?
It's working fine for me. But if needed, why not use Blender 3.6 LTS in this case? Clearly not all new functionalities can be enjoyed, but if I encounter large problems then I try to work in a previous version
@@UHStudio idk xd it crashed for me for some simple stuff when i went n repeated the stuff with 3.5 it worked well but if u saying it work well for u i might give it a Secend chance maybe there was something wrong with my projects n i didnt notice after all its not that hard to crash blender
I appreciate u responding
Value to String node should have a field input to feed it vector of data, not just single value. I like SVERCHOK nodes for this sort of things. I always found the vectorization in SV a little bit easier to understand than GN fields. Also SV has a Viewer Index node which does this vertex index magic with just one noodle :) you can easily display indices for vertices, edges and faces... and of course you could get fancier with the text viewer node if you want to customize the text to be other than just an index value. I hope Blender/GN will get better at doing these sort of “simple” things like visualizing the indices in the viewport. Loops (albeit parallel) may not be the best way to handle this sort of things. I wonder why not make this font/string combo a field based instead of a single value.
Awesome!
Thanks so much Jenifer!
damn this channel is saving my ass and sanity
Great summary for repeat zone! Great content. Thank you!
Cheers!
can it display text?
YES! 🤣
I meant, can geometry nodes read the text of the object name and display it with the string node? @@UHStudio