when i select all circles and move them to the center of the cplane either with dragging on the gumball center then hitting 0 or using the move tool and hit 0 to send it to center of origin the circles lose their relative position to each other. the same happens when i group them.
the geometry is rather far from the origin 1,5 km but should that impact the precision of relative distances within selected geometry?
dealing with such issues when you dont notice can have severe consequences down the road.
there is some history at play, purging history makes it work again, but that should just break in worst case, positioning all circles at once should not change their relative position.
Not just to the origin: select and drag/move minimal distance within their current vicinity and they cluster together just the same.
Other objects created nearby all move correctly so it isn’t being far from origin per se, but as you observe, purging history makes your objects move correctly too.
Replicated on Rhino 8 Windows (8.24.25280.13001, 2025-10-07).
Wow this is a weird one.
I used select parent to find the parent circle and moving that results in the same weird bug where all the circles overlap. That shouldn’t happen. I can move a child object and get the break history warning in v7. But if I select all the circles and move them they go back to being stacked.
Another oddity is that “history update” command makes all your circles overlap or relocate in space to the parent object. And I made a bunch of copies using your parent circle with history and that works as intended.
Did you have yet another circle that all these are made from? Did you copy twice or thrice with history on? Like copy in place then you copied again using history to where the locations are now, then hid or deleted the original/original parent circle?
Most likely you know as a work around leave your current circles but using history copy new ones to their locations and that works so something in the past process that did this to your circles.
See attached V7 file:
nope.. by all means, i even created circles anew 1,5 km from the center of origin. did all the moves i did before including scaling and that did nothing, beaming it back to the origin or moving generally did nothing to the relative position.
not from a different circles, but i think i copied a 2nd set from the one parent once more because i had to create a 2nd layer if i remember well. i also tried to recreate that scenario but i can not reproduced the issue in a new file. that might be one in a million.. it still is disturbing, if that happens less visual and unnoticed the outcome can have severe consequences.
to reproduce … what about history-rotating around the origin in 1.5 km distance ? this will result in a very ugly transformation matrix…
see what command - the history will be a “transform” and this means a transformation matrix is saved somewhere.
and of course a suspicious matrix can mess up coordinates
here are my weird circles - but i get a history warning… not fully successful rebuild…
