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

Closed
opened 3 years ago by roman-13 · 28 comments

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

rotate_90.gif

**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)
Poster

Added subscriber: @roman-13

Added subscriber: @roman-13
Collaborator

#101571 was marked as duplicate of this issue

#101571 was marked as duplicate of this issue
Collaborator

#78623 was marked as duplicate of this issue

#78623 was marked as duplicate of this issue
Collaborator

#78209 was marked as duplicate of this issue

#78209 was marked as duplicate of this issue
Collaborator

#72035 was marked as duplicate of this issue

#72035 was marked as duplicate of this issue
Collaborator

#71762 was marked as duplicate of this issue

#71762 was marked as duplicate of this issue

Added subscriber: @MarcinTwarowski

Added subscriber: @MarcinTwarowski

Same in 2.81

Same in 2.81

Added subscriber: @Stan_Pancakes

Added subscriber: @Stan_Pancakes

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) :)
Collaborator

Added subscriber: @mano-wii

Added subscriber: @mano-wii
Collaborator

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
mano-wii closed this issue 3 years ago
mano-wii self-assigned this 3 years ago
Collaborator

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.

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)?

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)?
Poster

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
Collaborator

Added subscribers: @MassimilianoPuliero, @lichtwerk

Added subscribers: @MassimilianoPuliero, @lichtwerk
Collaborator

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.
Collaborator

Added subscribers: @brothermechanic, @vademenev

Added subscribers: @brothermechanic, @vademenev
Collaborator

Changed status from 'Archived' to: 'Confirmed'

Changed status from 'Archived' to: 'Confirmed'
mano-wii reopened this issue 3 years ago
Collaborator

Added subscriber: @Juangra_Membata

Added subscriber: @Juangra_Membata
iss commented 3 years ago
Collaborator

Added subscriber: @awoug8h

Added subscriber: @awoug8h
Owner

Added subscriber: @ideasman42

Added subscriber: @ideasman42
Owner

Changed status from 'Confirmed' to: 'Archived'

Changed status from 'Confirmed' to: 'Archived'
ideasman42 closed this issue 2 years ago
Owner

Even though this behavior isn't ideal, closing as small numeric precision issues are an inherent problem with transforming in different spaces that get applied back.

Even though this behavior isn't ideal, closing as small numeric precision issues are an inherent problem with transforming in different spaces that get applied back.

Hey!
How about 2.49, where there is no this problem?
2020-11-04 18-00-46.mp4

Hey! How about 2.49, where there is no this problem? [2020-11-04 18-00-46.mp4](https://archive.blender.org/developer/F9196135/2020-11-04_18-00-46.mp4)
Collaborator

In #71535#1048056, @brothermechanic wrote:
How about 2.49, where there is no this problem?

Probably because the interface limits to only 3 decimal units.
But the problem is still there because it is the one that causes the -0.000 (0 with a negative sign).

> In #71535#1048056, @brothermechanic wrote: > How about 2.49, where there is no this problem? Probably because the interface limits to only 3 decimal units. But the problem is still there because it is the one that causes the `-0.000` (`0` with a negative sign).

In #71535#1048120, @mano-wii wrote:

In #71535#1048056, @brothermechanic wrote:
How about 2.49, where there is no this problem?

Probably because the interface limits to only 3 decimal units.
But the problem is still there because it is the one that causes the -0.000 (0 with a negative sign).

We need that rounding to 2.9!

> In #71535#1048120, @mano-wii wrote: >> In #71535#1048056, @brothermechanic wrote: >> How about 2.49, where there is no this problem? > > Probably because the interface limits to only 3 decimal units. > But the problem is still there because it is the one that causes the `-0.000` (`0` with a negative sign). We need that rounding to 2.9!
EAW commented 4 months ago

Added subscriber: @vojtech.salek

Added subscriber: @vojtech.salek
Sign in to join this conversation.
No Label
Interest/Alembic
Interest/Animation & Rigging
Interest/Asset Browser
Interest/Asset Browser Project Overview
Interest/Audio
Interest/Automated Testing
Interest/Blender Asset Bundle
Interest/Collada
Interest/Compositing
Interest/Core
Interest/Cycles
Interest/Dependency Graph
Interest/Development Management
Interest/Eevee & Viewport
Interest/Freestyle
Interest/Geometry Nodes
Interest/Grease Pencil
Interest/ID Management
Interest/Images & Movies
Interest/Import/Export
Interest/Line Art
Interest/Masking
Interest/Modeling
Interest/Modifiers
Interest/Motion Tracking
Interest/Nodes & Physics
Interest/Overrides
Interest/Performance
Interest/Performance
Interest/Physics
Interest/Pipeline, Assets & I/O
Interest/Platforms, Builds, Tests & Devices
Interest/Python API
Interest/Render & Cycles
Interest/Render Pipeline
Interest/Sculpt, Paint & Texture
Interest/Text Editor
Interest/Translations
Interest/Triaging
Interest/Undo
Interest/USD
Interest/User Interface
Interest/UV Editing
Interest/VFX & Video
Interest/Video Sequencer
Interest/Virtual Reality
legacy module/Animation & Rigging
legacy module/Core
legacy module/Development Management
legacy module/Eevee & Viewport
legacy module/Grease Pencil
legacy module/Modeling
legacy module/Nodes & Physics
legacy module/Pipeline, Assets & IO
legacy module/Platforms, Builds, Tests & Devices
legacy module/Python API
legacy module/Rendering & Cycles
legacy module/Sculpt, Paint & Texture
legacy module/Triaging
legacy module/User Interface
legacy module/VFX & Video
legacy project/1.0.0-beta.2
legacy project/Asset Browser (Archived)
legacy project/BF Blender: 2.8
legacy project/BF Blender: After Release
legacy project/BF Blender: Next
legacy project/BF Blender: Regressions
legacy project/BF Blender: Unconfirmed
legacy project/Blender 2.70
legacy project/Code Quest
legacy project/Datablocks and Libraries
legacy project/Eevee
legacy project/Game Animation
legacy project/Game Audio
legacy project/Game Data Conversion
legacy project/Game Engine
legacy project/Game Logic
legacy project/Game Physics
legacy project/Game Python
legacy project/Game Rendering
legacy project/Game UI
legacy project/GPU / Viewport
legacy project/GSoC
legacy project/Infrastructure: Websites
legacy project/LibOverrides - Usability and UX
legacy project/Milestone 1: Basic, Local Asset Browser
legacy project/Nodes
legacy project/OpenGL Error
legacy project/Papercut
legacy project/Pose Library Basics
legacy project/Retrospective
legacy project/Tracker Curfew
legacy project/Wintab High Frequency
Meta/Good First Issue
Meta/Papercut
migration/requires-manual-verification
Module › Animation & Rigging
Module › Core
Module › Development Management
Module › Eevee & Viewport
Module › Grease Pencil
Module › Modeling
Module › Nodes & Physics
Module › Pipeline, Assets & IO
Module › Platforms, Builds, Tests & Devices
Module › Python API
Module › Render & Cycles
Module › Sculpt, Paint & Texture
Module › Triaging
Module › User Interface
Module › VFX & Video
Platform/FreeBSD
Platform/Linux
Platform/macOS
Platform/Windows
Priority › High
Priority › Low
Priority › Normal
Priority › Unbreak Now!
Status › Archived
Status › Confirmed
Status › Duplicate
Status › Needs Information from Developers
Status › Needs Information from User
Status › Needs Triage
Status › Resolved
Type › Bug
Type › Design
Type › Known Issue
Type › Patch
Type › Report
Type › To Do
No Milestone
No project
No Assignees
10 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#71535
Loading…
There is no content yet.