Timeline for Understanding how "vertex of corner" works in geometry node
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 11, 2023 at 9:42 | history | edited | Markus von Broady | CC BY-SA 4.0 |
added 90 characters in body
|
| Jun 21, 2023 at 11:47 | history | edited | Markus von Broady | CC BY-SA 4.0 |
added 386 characters in body
|
| May 8, 2023 at 20:08 | comment | added | Markus von Broady |
@lemon the "evaluate at index" node also changes context, but it doesn't switch to another geometry. The context it changes is it can switch domain or index from currently evaluated context. E.g. For every vertex you can read a position of a previous vertex by connecting index-1 to the index socket. For "Sample index" node, you can do the same, but also connect a different geometry.
|
|
| May 8, 2023 at 17:48 | comment | added | lemon | I think the key point is 4. in the last part of your explanation. Though, the documentation is not clear (my last edit in the quesiton). But yes, the context is the key and that works (I think) without "vertex of corner" because the other inputs are not context dependent (constants). But so, what is the solution? Capturing all before "mesh to points"? (PS: in this context "store named attributes" were only here for debug purpose) | |
| May 8, 2023 at 17:24 | comment | added | lemon | Thank you for the time you took for these explainations, I really appreciate. I've to read again before I can feedback on your answer (as it is late here, that will be tomorrow). | |
| May 8, 2023 at 17:11 | history | answered | Markus von Broady | CC BY-SA 4.0 |