Change Details

By design the modified object transformations should still work and affect the geometry nodes results. The current behavior, however, make the geometry from the object info node not affected by the modified object transformations. In a similar fashion the Location, Rotation and Scale sockets outputs should be aware of whether the output should be in the global space or in the space of the nodetree. To solve this, the patch introduces a new transformation space "enum" where users can pick "Local" or "Global" space. Global Space violates a bit the design of the nodetree. The geometry in this case is transformed so that moving the modified object doesn't interfere with the geometry. This is particularly useful for the boolean node for instance. In this case the Location/Rotation/Scale are also outputted in global space. Local Space is the default space. In this case Location/Rotation/Scale are provided in relation to the modified object space. This is useful to check if an object is close to vertices and act accordingly. The geometry in this case matches the obtained by the point instance node. This will be particularly important once the the point instance node gets a new input type "Geometry". In that case plugging the geometry from the object info or using the object input should yield the same results. Old files have the space as GLOBAL by default to prevent any changes in behavior. --- Bonus design consideration. The same behavior is expected for the collection info node (T84603) in relation to the offset setting of the collection.

By design the modified object transformations should still work and affect the geometry nodes results. The current behavior, however, make the geometry from the object info node not affected by the modified object transformations. In a similar fashion the Location, Rotation and Scale sockets outputs should be aware of whether the output should be in the global space or in the space of the nodetree. To solve this, the patch introduces a new transformation space "enum" where users can pick "Local Space" or "No Transform" space. No Transform space violates a bit the design of the nodetree. The geometry in this case is transformed so that moving the modified object doesn't interfere with the geometry. This is particularly useful for the boolean node for instance. In this case the Location/Rotation/Scale are also outputted in global space. Local Space is the default space. In this case Location/Rotation/Scale are provided in relation to the modified object space. This is useful to check if an object is close to vertices and act accordingly. The geometry in this case matches the obtained by the point instance node. This will be particularly important once the the point instance node gets a new input type "Geometry". In that case plugging the geometry from the object info or using the object input should yield the same results. Old files have the space as "No Transform" by default to prevent any changes in behavior. --- Bonus design consideration. The same behavior is expected for the collection info node (T84603) in relation to the offset setting of the collection.

By design the modified object transformations should still work and affect the geometry nodes results. The current behavior, however, make the geometry from the object info node not affected by the modified object transformations. In a similar fashion the Location, Rotation and Scale sockets outputs should be aware of whether the output should be in the global space or in the space of the nodetree. To solve this, the patch introduces a new transformation space "enum" where users can pick "Local Space" or "GlobalNo Transform" space. Global SNo Transform space violates a bit the design of the nodetree. The geometry in this case is transformed so that moving the modified object doesn't interfere with the geometry. This is particularly useful for the boolean node for instance. In this case the Location/Rotation/Scale are also outputted in global space. Local Space is the default space. In this case Location/Rotation/Scale are provided in relation to the modified object space. This is useful to check if an object is close to vertices and act accordingly. The geometry in this case matches the obtained by the point instance node. This will be particularly important once the the point instance node gets a new input type "Geometry". In that case plugging the geometry from the object info or using the object input should yield the same results. Old files have the space as GLOBAL"No Transform" by default to prevent any changes in behavior. --- Bonus design consideration. The same behavior is expected for the collection info node (T84603) in relation to the offset setting of the collection.