Skip to main content
5 of 13
edited body

How to "unhook" position node in math calculations from attribute "parent"?

I am trying to create a system for aplying same gradient on different objects (hereinafter "objects") and control it with another object(hereinafter "controler"). And now the main problem is to "replicate" Texture coordinate "Object" output in geometry node. If i put obect info node inside geonodes of object everything works fine,enter image description here but when i trying to transfer attributes of obect info node from controler, blender starts calculating vector math not with objects, but with controller, although calculations take place inside geonodes of the object.enter image description here (small wire cube is controler)

How to avoid this? I tried to use capture attribute to object position, store attribute to object position, store attribute to gradient location, nothing helped.

UPD

The problem with the position of the gradient is solved by adding the position of the gradient and the controller in the GN of the object (translation into the coordinate system of the object), enter image description here but if you rotate the objects, everything breaks. enter image description here Again I understand why this is happening, but I don't have the brains to solve it yet. (or just digging in vector math for 5 hours on end doesn't affect me very well:)).