Allow retreiving geometry from the object the modifier is on.
I have nodes that I made by putting them on planes and using object info nodes. I was converting them over when I noticed this error. Just thought it was odd that this doesn't function when the result you would get from it can be gotten by placing the modifier on another object but then using the object info node to bring in the modifier object.
Object info node should be able to take the object the modifier is on as input, since this is technically possible with the workaround. It would be more convenient if you could just use the object info node with the object you are modifying as an input.
Just to be extra clear, I'm only suggesting this since the exact desired result is possible by making a plane, placing the modifier on it instead and swapping the source to the original object that couldn't be modified. It just confuses me why that workaround makes it possible when it doesn't work by default. Is there any other way to access the values from object info easily like location, rotation, etc. on the modifier object itself?
It seems the only way to easily access those values is to use a buffer object like a plane to hold the modifier, which makes it so i can't drag and drop my modifiers on to the objects I want to modify. A node with the same output (scale, rotation, location, etc.) but taking in your input geometry instead of a separate object would be useful.
Is this workaround the way geometry nodes are supposed to be used?
6 Comments
Have you tried "Self Object" node?
Have you tried it? if you plug it into an object info node and try to access the geometry, it just tells you "Geometry cannot be retrieved from the modifier object". You need to use a group input instead to get the original geometry.
Doesn't work for simulations. If I move the object the simulation moves, not an issue when using a plane with object info node pointing at geometry, was wondering if there was a workaround to not have to use a separate object with object info node to move the geometry being simulated around without moving the simulation itself. Like translating up would also translate the points up too, which doesn't happen when using a separate object with the object info node instead of using geoinput and using it as a modifier.
It's similar to the issue I get trying to use constraints on an empty in the object info node, motion hasn't been calculated yet, so even with self object it doesn't work correctly.
If you need to access the geometry of the object with the modifier on it, can't you just use a group input node?
Doesn't work for simulations, if I move the geometry the simulation space moves, not an issue if the geonode is on a seperate object like a plane and using the object info node. Was wondering if there was a workaround to just use it as a modifier, I feel like I used one many many tutorials ago but don't remember it. Self Object does not work.