Thanks for reporting this problem, @krezrock. We tested on a couple different computers and didn’t see the problem, so it looks like it’s specific to the GPU. What GPU do you have?
We’re able to reproduce the problem on an AMD 7970. It happens in 1.2.6 but not 1.2.5.
Looking at exactly what changes caused the wrongly positioned points, we found that it was the workaround to the driver bug that caused crashes on AMD GPUs. The exact thing that fixed the crashes caused some of the 3D object filter nodes (Add Noise, Explode, Trim) to give wrong output.
So, we’ll see if there’s a workaround to what appears to be a second driver bug.