As I understand it, such reports are usually closed (referring to the fact that someday this will be decided in a general way), so for now I will also close this.
If you can't please everyone (why want at less single point, and other once, why dont't wnat to have curves at all), should we keep it open?
Is this problem reproducible?
This is not a bug. If the original geometry and the new geometry of the modifier do not explicitly intersect materials (due to the work of geometry nodes), then it should be so.
@lichtwerk It's strange, since I can make a lot of changes in time. Now it looks even weirder.
Issues: When reading notifications, the page may randomly switch.
Fine. Initially, it seemed to me that this was a collection of various bugs in a closed project, and the user wanted to try to fix them himself, without being able to give an example file. But…
F12 rendering a specific project crashes Blender without error message in release builds, therefore messages are from debug build. Sometimes rendering 4-5 times in a row is needed to see the…
Hey, please. Freestyle & python bug really unrelated with node tree problems. Please, open separate report for each bug, that you find, individually.
Hello. I can't reproduce this in last 3.4 and 3.5 master. Can you check this in today builds?
My problem to confirm this: I haven't Mix RGB node. This deleted now and i cant find this/
You sure that ypu project without addons/assets?
Hello. I can't reproduce that. Can you check this with default factory settings?
Hi, can you give an example file or demonstrate this? Not sure exactly what and how you are doing.
Not sure, needs to be checked. But it looks like it might be closed? 0ea15a6fbb