this post was submitted on 08 Jul 2023
14 points (100.0% liked)

Blender

2724 readers
39 users here now

A community for users of the awesome, open source, free, animation, modeling, procedural generating, sculpting, texturing, compositing, and rendering software; Blender.

Rules:

  1. Be nice
  2. Constructive Criticism only
  3. If a render is photo realistic, please provide a wireframe or clay render

founded 1 year ago
MODERATORS
 
all 6 comments
sorted by: hot top controversial new old
[–] [email protected] 4 points 1 year ago (2 children)

I've noticed that this happens alot while messing with simulation nodes what am I doing wrong?

[–] [email protected] 2 points 1 year ago

Weird. I'm surprised that this is working at all. I thought there would be no points to instance on after creating the first instance. The simulation zone isn't the culprit here though. The same happens here if i simply chain a few (7) instance on points nodes after another. I have to investigate this further. You can fix it by adding a realize instances node after the simulation. Be careful though. this gets ugly quickly :) And use radians if you pipe a vector into the rotation socket. -pi to pi should give you the 360° you are aiming for.

[–] [email protected] 1 points 1 year ago (1 children)

Ok, I got it. What you are doing is called nested instancing (instancing on an instance) https://docs.blender.org/manual/en/latest/modeling/geometry_nodes/instances.html#geometry-nodes-nested-instancing the page states:

Warning Only eight levels of nested instancing are supported for rendering and the viewport currently. Though deeper trees of instances can be made inside geometry nodes, they must be realized at the end of the node tree.

[–] [email protected] 1 points 1 year ago