1
$\begingroup$

Here is a simple collection info example:

Simple Collection Info example

Blue cube is the original cube in the collection named Test, red is the one modified trough the collection info node acting on the Test collection. Is there a way to turn off the visibility of the original (blue) cube both in the viewport as well as in the rendered image from within the geometry node?

$\endgroup$
2
  • $\begingroup$ You can make a driver $\endgroup$ Commented Dec 2, 2024 at 7:30
  • $\begingroup$ Brilliant idea! In deed you can put a driver on an objects "Hide Viewport" attribute. Unfortunately this doesn't work on collections. Now I have to find a way how to script bpy.data.collections["Test"].hide_viewport = True/False into another driver... $\endgroup$ Commented Dec 2, 2024 at 9:45

1 Answer 1

1
$\begingroup$

Geometry nodes can only change the objects they're modifying.

If your geometry nodes are on the red "plane", it can only change the "plane".

You can always click the buttons to make the original object invisible (it will still work int the "collection info" node).

Image

$\endgroup$
4
  • $\begingroup$ Thanks, I know that but that means I can't automate a task based on Collection Info as the user needs to manually turn off the visibility of the collection. It's a half baked solution. :-( The Collection Info node refers to a collection and modifies it's content and it could also "see" the collection's properties. (These properties are available in BPY so the programmer of the node could also have added this functionality. It would have been a logical step. $\endgroup$ Commented Dec 1, 2024 at 21:24
  • $\begingroup$ No, it's not logical. The collection info does not modify its content. Nothing in geometry nodes is intended to modify anything that is not the object containing the modifier with the nodes. $\endgroup$ Commented Dec 1, 2024 at 22:43
  • $\begingroup$ "Geometry nodes can only change the objects they're modifying." - more specifically, it modifies the data of the object. It's the mesh or curve data, or pointcloud... Geometry Nodes won't modify constraints, transformation matrix, Line Art settings etc. $\endgroup$ Commented Dec 2, 2024 at 8:22
  • $\begingroup$ I think it is logical. The Collection Info is referring to objects which have otherwise no relation to the object which actually has the GN modifier. From a user's point of view it is entirely logical that I want to do something with the objects in that referred collection and that might mean that I don't want to see the initial state of those objects. A simple "Hide Source" checkmark in the Collection Info node would be sufficient to achieve that. That's what I meant with half baked. $\endgroup$ Commented Dec 2, 2024 at 8:54

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.