Can you please get rid of the attribute search in the mograph related nodes?
It gets annoying to click or press enter every time I want to change it.
1 Like
I’ve been playing around a bit with different effects and realized if part of a string is replaced with other characters in an animation, the layout will also change and cause flickering unless a monospaced font is used. This lead to experimenting with a new input on the String to Curves-node called “Override Characters”. When this is used the main input will generate the layout, and the override will be the characters distributed at those points. You can see this in the image below.
I think this can be a useful feature for effects like “Decoder” that can be seen near the beginning of this thread. What do you think?
6 Likes
I’m not a pro motiongrapher by any chance, but I think the decoder effect works by using the same type of characters in each character. I mean, if the string being decoded is a word, it doesn’t make sense for numbers or punctuation marks to appear during the decoding. Same for a large number: it doesn’t make sense the letters appear during decoding. My point is: other than ‘j’ and ‘i’, I don’t think decoding strings will be too affected by the width of the character. So, it seems to me that trying to solve the flickering effect to cover every possible case could be misplaced effort.
Someone with more experience correct me if I’m wrong.
Btw, have you looked how Animation Nodes’ Text nodes work? They have a whole bunch that are really useful and I imagine they could be the base for some of the stuff in Geo Nodes (Random String seems to do the decoder effect, and Decompose Text seems to offer the fundamental functionality of transforming characters, words and lines separately).
Anyways, I don’t want to discourage you about the work you’re doing. You’ve given me years of life by implementing a very needed feature in Blender. I just wanted to mention my opinion as an observer and noob motiongrapher. Keep it up!
Yeah I think you’re underestimating the flickering a bit. I made a sample here that better shows what I mean. The middle is using the new override input.
edit: This example makes it more clear how modifying the input string affects the layout:
9 Likes
Ah, the third one is really bad 
Edit: ahhh, your second gif shows it much, much better.
I’m playing the text nodes in the daily build of 3.0. I want to have my string as a mesh object with a certain thickness. Purpose is to do a boolean operation with the rest of the geometry. I cannot do it because I cannot find a way to add thickness to the text. Is that possible at all?
For the time being the only way I know of is using a solidify modifier (there’s a solidify node coming and also the extrude one but I’m not sure when they’re going to land in master)
@HooglyBoogly, do you know if 3.0 eventually will have geometry nodes that allow thickness to be added to curves or meshes?
1 Like
Probably not at this point, but I bet 3.1 will.
3 Likes
Is it planned for the translate/rotate/scale instance nodes to make it into 3.0?
2 Likes
I’d say probably, since they are a straightforward continuation of the changes we already made to the instances workflow.
6 Likes
Yes, please. This is very important for anyone working with text and motion graphics.
3 Likes
The instance transform nodes are now available in the latest master build if someone wants to try them. 
I’m not sure if anything more related to text nodes are going to make it to 3.0. Would like to get the String Replace node in too but we will see about that.
I think what we need now is lots of artists trying the workflow to know what the next steps will be (other than solidify/bevel and attributes on instances).
9 Likes
Yes! I downloaded last night and tried out one of the animations you did earlier in this thread.
I was wondering: is there a way to split a string by words? Maybe I’m dense, but I couldn’t figure it out.
When we have a way of putting attributes on instances I will create outputs for selecting instances by line and probably word.
By word is a bit more involved and ideally I would like to use the ICU library that supports other languages like Thai where there’s no (atleast in some cases, not sure if all) way to separate words other than by using a wordlist. Other asian languages as well.
If you mean separate a string to words, then no. With the Replace node you will be able to replace white space with new line or something like that maybe… Or use some smart regular expressions.
4 Likes
Right, I was thinking something along the lines of just using spaces somehow to split into instances a string input.
Could it be worth it for devs to check how Animation Nodes does it?
What would the output be though? Lists of strings are not supported so you would have to specify the index of the “word” to output then but I’m not sure if that’s a good idea. It might be useful, I don’t know. This could maybe be a job for string fields in the future.
Sorry, I’m not sure I follow. The output would look the same as the original string, but you could use the Translate/Rotate/Scale Instances node to translate/rotate/scale each word individually, for example. Just like it currently works with individual characters.
1 Like
Ah, ok. That’s what I was talking about above then. Attributes on the character instances that tell which word/line it belongs to.
1 Like
Ah, cool then. Well, let’s hope it makes it into the next release. In the meantime, I have to thank you very, very much for the work you did for this release. I’ll put into good use these new nodes. 
1 Like