Syntax-wise, I'd suggest what we could use pairs of characters that commonly prohibited by usual operating systems. I propose that adding shortcut path variables that user themselves could define…
Ah, how can I missed the explicit evaluate on domain way! Thanks, Hans!
Hi, Hans. All I came up so far is to mix like this.
Can you make a demo file of your method?
If you use the "Evaluate on Domain"…
All right. Then this behavior may cause confusion that it differs from the exisiting displace modifier which actually interpolates like I described above. And it's been used like ages. ![image](/a…
I mean is it really reasonable to lerp the face corner coordinates instead of lerping the attribute itself?
What I mean is that sometimes the "selection" sockets' domain is always vague and hard to guess. I'd suggest that we tell the instruction in the socket lable it self like "point selection/face…
The normal mode is stored on the curve domain rather than per point. Then why would the "switch" way worked?
Another example could be adaptive subdivision, which is made so much easier when you can split edges, subdivide selection, and subdivide edges of inverse selection (and merge by distance). One…
the old multiscatter GGX model has been replaced in 4.0 aplha I tested the demo file, it's been fixed.
It is possible that the difference is caused by the viewport GPU subdivision, which isn't implemented in GN at the moment. Otherwise in my test it's not prominent enough.
Edit:
…
please close this report and it's been fixed in recent 4.0 alpha builds
this BUG has been resolved in the recent 4.0 alpha builds!