I just tested it with 3.5 release and it does not crash. Unfortunately I cant provide the production model, I tried section it up and provide a portion but then it does not.
It seems like the processing time of the mesh to volume has doubled in the given example above
@erik85
The problem is that this change breaks compatibility and messes up points distributions in geonodes projects. It would be nice if this is kept for historical reasons.
I am not sure if I follow you but the file is crashing Blender upon opening it. There is no way for me to test those steps in 3.6
I can try to dissect the node group and provide it that portion if you tell me what you are interested in the file.
Hi
Sorry I can't provide my own production file, unfortunately. Since I do not know what is crashing in the setup I am not able to provide a reproducing file. I can try to give you more…
This was a simple demo scene, this haves exponentially horrible in complex scenes, as in I have to zoom stop zoomm stop zoom stop zoom stop... until I get to where I need on an object.
@DanielBystedt thanks for testing it out. I actually hit this bug long time ago but I kept going around it and using object to object bake to get what I need. I just ran out of patience this time…
Compositor uses blue/Z channel as alpha channel, see
MapUVOperation::read_uv()if alpha is 0, it skips further processing. Unfortunately i can't tell you why exactly this is designed this way.…
Can confirm this behaviour in the latest build (e4eb9e04e016) It seems however that this has been happening since at least 3.0.1 (dc2d18018171)
The issue is not in AOVs, but in the…
Would there a way to make it so that the thickness of the wireframe gets thinner as the object moves away from the viewer/camera? I love working with thick edges but one issue is that…