← All ideas
  • Published 27 Jun 2021

Geometry Nodes: Get object by name (String)

Get Object by name (String input)

GET OBJECT.jpg

Example of use: Imagine having multiple set of objects: OBJ-T-1,OBJ-T-2 and OBJ-V-1,OBJ-V-2

Then you create a string by concating "OBJ" + "-" + "T" / "V" + "-" + "1" / "2"

From that string you would access one of your object (if exist), but if you say that for example the str "1" and "2" comes from an index, and "T" and "V" from a String Switch, you would have a complex way of getting your object and taging them by name.

PD: I would love to create it myself and submit it to blender, but I have no luck researching were to access geo nodes. Answers on this topic are welcome.

100%

Development Status: Open

Upvote 26 Downvote 0
TaiSeiButsU
27 Jun 2021

4 Comments

zorro.weaver

Ah, this would be one of the first steps to string manipulation. Remember, this would be a game-changing feature, and could muck up things in the future if not implemented well. This is something to start thinking about, but it will require much planning. I suggest putting a lot of thought into it before trying to create it yourself and implement it.

That being said, here are some other nodes that might be required in order to have a complete system. Might you consider adding them to your idea?

  • String combine (Takes any number of strings and joints them together joining them with a . , - , or _ )
  • String math (Mixes strings using add, difference, or numerical codes)
  • Value to string (Takes a float, integer, boolean, or vector and converts it into a string.)
  • Object and collection info nodes should output the name of the object/collection in a string.
5
Strike_Digital

Quite a lot of this stuff is already being worked on: devtalk.blender.org/t/text-mograph-nodes-design/19208/32 It's pretty exciting stuff.

3
TaiSeiButsU Author

I'll create some mock ups but I think logic for this is pure Strings, Will you post it together?

h.goudey

On a design level, my issue with this is that it requires the objects to be in the file already, it doesn't work very well with the linking workflow to bring in objects from separate files.

Even then, maybe it's still fine though. The trouble is the dependency graph currently doesn't support relying on the object name in this way.

1