Ok, I found the solution. I uploaded a screenshot of the patch to ChatGPT and it immediately spotted the issue — even without me explaining the problem. I have to admit I was impressed.
Anyway, the actual solution is that a DynamicMesh needs a bounding box.
Without defining bounds, I was getting these kinds of rendering artifacts.
It goes without saying that ChatGPT also had an opinion about this workflow — according to it, rendering meshes as points like this is somewhat unstable and I’d be better off rendering small spheres instead.
@vincent.now Kind of crazy that GPT solved it looking at your screenshot only! Anyway thanks for bringing this up, had a similar issue and had no idea whats wrong. In my case it was a NullMesh that needed a bounding box to work properly.