You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tested this issue with a variety of different blender file sizes and it seems persist throughout. The location of the cursor doesn't seem to matter. I did a few new tests in a brand new blend file, which resulted in not being able to move a cube next to another using a vertex selection, while along the 0 coordinate of the y-axis. My running theory is that it depends how close an operation (mostly just move in my case, though i have had issues with rotation in the past) is to the world origin. Upon doing further tests I've noticed that it is not always a repeatable issue along the 0 coordinates of both the x/y axis nor the proximity to the world origin.
Blender version 3.5.1 Stable
Some of my system specs if that helps:
-Windows 10
-gtx 1070 ti (2x)
The text was updated successfully, but these errors were encountered:
I tested this issue with a variety of different blender file sizes and it seems persist throughout. The location of the cursor doesn't seem to matter. I did a few new tests in a brand new blend file, which resulted in not being able to move a cube next to another using a vertex selection, while along the 0 coordinate of the y-axis. My running theory is that it depends how close an operation (mostly just move in my case, though i have had issues with rotation in the past) is to the world origin. Upon doing further tests I've noticed that it is not always a repeatable issue along the 0 coordinates of both the x/y axis nor the proximity to the world origin.
Blender version 3.5.1 Stable
Some of my system specs if that helps:
-Windows 10
-gtx 1070 ti (2x)
The text was updated successfully, but these errors were encountered: