Rotating an object in front or back view adds value to X and Z #71535

New Issue

System Information
Operating system: Windows-7-6.1.7601-SP1 64 Bits
Graphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.13

Blender Version
Broken: version: 2.82 (sub 1), branch: master, commit date: 2019-11-12 13:30, hash: c69872bd2f
Worked: (optional)

Short description of error
[Rotating an object in orthographic front or back view adds value to X and Z,if you use hotkeys without specifying an axis of rotation.
If you rotate the object 90 degrees in Z, while rotating, deviations will be added for X and Y in other views, and indicating the axis of rotation does not help.]

**System Information** Operating system: Windows-7-6.1.7601-SP1 64 Bits Graphics card: GeForce GTX 750 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 388.13 **Blender Version** Broken: version: 2.82 (sub 1), branch: master, commit date: 2019-11-12 13:30, hash: `c69872bd2f` Worked: (optional) **Short description of error** [Rotating an object in orthographic front or back view adds value to X and Z,if you use hotkeys without specifying an axis of rotation. If you rotate the object 90 degrees in Z, while rotating, deviations will be added for X and Y in other views, and indicating the axis of rotation does not help.] ![rotate.gif](https://archive.blender.org/developer/F8057793/rotate.gif) ![rotate_90.gif](https://archive.blender.org/developer/F8057794/rotate_90.gif)

Roman commented

Added subscriber: @roman-13

blender-admin commented

#101571 was marked as duplicate of this issue

blender-admin commented

#78623 was marked as duplicate of this issue

blender-admin commented

#78209 was marked as duplicate of this issue

blender-admin commented

#72035 was marked as duplicate of this issue

blender-admin commented

2019-11-13 10:42:15 +01:00

#71762 was marked as duplicate of this issue

Marcin Twarowski commented

Added subscriber: @MarcinTwarowski

Marcin Twarowski commented

2019-11-13 10:42:15 +01:00

Same in 2.81

Stanislav Blinov commented

2019-11-13 11:20:02 +01:00

Added subscriber: @Stan_Pancakes

Stanislav Blinov commented

2019-11-13 11:20:02 +01:00

Indicating the axis of rotation does help. With it, at "worst" you only get sign switching for 0. Without it, these small errors. For what it's worth, there was a time when this didn't happen (i.e. 2.49b) :)

Indicating the axis of rotation **does** help. With it, at "worst" you only get sign switching for 0. Without it, these small errors. For what it's worth, there was a time when this didn't happen (i.e. 2.49b) :)

Germano Cavalcante commented

Added subscriber: @mano-wii

Germano Cavalcante commented

Changed status from 'Open' to: 'Archived'

Germano Cavalcante closed this issue

Germano Cavalcante self-assigned this 2019-11-20 19:07:07 +01:00

Germano Cavalcante commented

2019-11-20 19:19:58 +01:00

Although visually bad, this is normal since single precision floats only have 6-7 digits of precision.
Starting with Blender 2.80, default units are set (meters, degrees) and some have more decimal digits than "Blender Units".
So what is happening is that this inaccuracy is now seen.

There are ways to work around this problem internally by using operations that work with double precision.
But for this other things need to be taken into consideration (such as peformanse, code complexity, etc.).
This is a known limitation and not a priority at the moment.

Although visually bad, this is normal since single precision floats only have 6-7 digits of precision. Starting with Blender 2.80, default units are set (meters, degrees) and some have more decimal digits than "Blender Units". So what is happening is that this inaccuracy is now seen. There are ways to work around this problem internally by using operations that work with double precision. But for this other things need to be taken into consideration (such as peformanse, code complexity, etc.). This is a known limitation and not a priority at the moment.

Stanislav Blinov commented

I don't follow. Why would there even be a difference between R, Y (no extra decimals) and simply R in front view (extra decimals)?

Roman commented

2019-11-21 11:17:21 +01:00

In #71535#813863, @mano-wii wrote:
Although visually bad, this is normal since single precision floats only have 6-7 digits of precision.
Starting with Blender 2.80, default units are set (meters, degrees) and some have more decimal digits than "Blender Units".
So what is happening is that this inaccuracy is now seen.

There are ways to work around this problem internally by using operations that work with double precision.
But for this other things need to be taken into consideration (such as peformanse, code complexity, etc.).
This is a known limitation and not a priority at the moment.

If this is an inaccuracy, then why show it?
Better limit to 3 decimal places

> In #71535#813863, @mano-wii wrote: > Although visually bad, this is normal since single precision floats only have 6-7 digits of precision. > Starting with Blender 2.80, default units are set (meters, degrees) and some have more decimal digits than "Blender Units". > So what is happening is that this inaccuracy is now seen. > > There are ways to work around this problem internally by using operations that work with double precision. > But for this other things need to be taken into consideration (such as peformanse, code complexity, etc.). > This is a known limitation and not a priority at the moment. If this is an inaccuracy, then why show it? Better limit to 3 decimal places

Philipp Oeser commented

2019-11-22 11:22:28 +01:00

Added subscribers: @MassimilianoPuliero, @lichtwerk

Philipp Oeser commented

2019-11-22 11:44:31 +01:00

Afaict, constraining to a specified axis vs. using the ortho projection is not the same.
Dont think there is a special flag on the view that tells us we are in top/front/... but there could be ways to check [text info overlay knows at least...]

Not sure though if this would be a priority either.

Afaict, constraining to a specified axis vs. using the ortho projection is not the same. Dont think there is a special flag on the view that tells us we are in top/front/... but there could be ways to check [text info overlay knows at least...] Not sure though if this would be a priority either.

Philipp Oeser commented

2019-11-29 09:28:51 +01:00

Added subscribers: @brothermechanic, @vademenev

Germano Cavalcante commented

2020-06-25 18:57:59 +02:00

Changed status from 'Archived' to: 'Confirmed'

Germano Cavalcante reopened this issue

2020-06-25 18:57:59 +02:00

Germano Cavalcante commented

2020-06-25 18:58:18 +02:00

Added subscriber: @Juangra_Membata

Richard Antalik commented

2020-07-08 05:19:12 +02:00

Added subscriber: @awoug8h

Campbell Barton commented

Added subscriber: @ideasman42

Campbell Barton commented

Changed status from 'Confirmed' to: 'Archived'

Campbell Barton closed this issue

Campbell Barton commented