G X and move results in crazy number in the position box. #60047

New Issue

Douglas E Knapp · 2019-01-02T00:27:20+01:00

Douglas E Knapp commented

2019-01-02 00:27:20 +01:00

Linux Manjaro fully updated.
Nvidia 580 GTX
1,1 2019 64bit linux blender 2.8

new -> general
select default object (changed to a sphere for my system)
G ->X move backwards and at some point and it changes the numbers box goes from [x -418] to [-100000000000] or so. and then with more movement back starts with other numbers. When you come back it jumps right back to x -418 and at the same location of mouse movement. At is not always at -418 and I can reproduce the error on the Y axes as well. It also fails with two objects selected but it seems to happen at a lower number (-418 was with two objects).

Linux Manjaro fully updated. Nvidia 580 GTX 1,1 2019 64bit linux blender 2.8 new -> general select default object (changed to a sphere for my system) G ->X move backwards and at some point and it changes the numbers box goes from [x -418] to [-100000000000] or so. and then with more movement back starts with other numbers. When you come back it jumps right back to x -418 and at the same location of mouse movement. At is not always at -418 and I can reproduce the error on the Y axes as well. It also fails with two objects selected but it seems to happen at a lower number (-418 was with two objects).

Douglas E Knapp commented

2019-01-02 00:27:20 +01:00

Added subscriber: @DouglasEKnapp

Douglas E Knapp commented

2019-01-02 01:07:13 +01:00

I reproduced the error in 2.79b also.

Sebastian Parborg commented

2019-01-02 14:37:11 +01:00

Added subscriber: @ZedDB

Sebastian Parborg commented

2019-01-02 14:37:11 +01:00

Changed status from 'Open' to: 'Archived'

Sebastian Parborg closed this issue

2019-01-02 14:37:11 +01:00

Sebastian Parborg self-assigned this 2019-01-02 14:37:11 +01:00

Sebastian Parborg commented

2019-01-02 14:37:11 +01:00

This is because it tries to track the movements to the mouse cursor. If you move the cursor to far up, the calculated transform location will almost be perpendicular to the X axis. So the transform value will jump to a really high number.
You can see that this is not a problem if you change to the top view and transform along the x axis.

This is because it tries to track the movements to the mouse cursor. If you move the cursor to far up, the calculated transform location will almost be perpendicular to the X axis. So the transform value will jump to a really high number. You can see that this is not a problem if you change to the top view and transform along the x axis.

Douglas E Knapp commented

2019-01-02 21:43:03 +01:00

It is still a BIG bug. I can position my model where it should be. Here is a video of the problem.Kazam_screencast_00000.mp4

It is still a BIG bug. I can position my model where it should be. Here is a video of the problem.[Kazam_screencast_00000.mp4](https://archive.blender.org/developer/F6153770/Kazam_screencast_00000.mp4)

Sebastian Parborg commented

2019-01-02 23:08:53 +01:00

If you want to workaround this limitation, you can click and drag on the X location in the N-panel.

Douglas E Knapp commented

2019-01-02 23:18:52 +01:00

OK, thanks for your time!

Sebastian Parborg commented

2019-01-02 23:20:00 +01:00

Sorry this couldn't be solved in a better way.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

G X and move results in crazy number in the position box. #60047