Unit Scale change undone when using redo menu #103647

Closed
opened 2023-01-04 22:51:25 +01:00 by jon denning · 4 comments
Member

System Information
Operating system: Linux-5.11.0-49-generic-x86_64-with-glibc2.33 64 Bits
Graphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86

Blender Version
Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: 55485cb379
Worked: (haven't tested)

Short description of error
Whenever the redo menu is used, any recent changes to unit scale are undone. When this happens, the redone action can be scaled incorrectly.

Exact steps for others to reproduce the error

  1. start blender with factory settings
  2. delete default cube, then re-add cube (lol)
  3. expand the redo panel for Add Cube, and notice that the cube has Size 2m
  4. open the N panel, switch to Item tab, and notice Dimensions are 2m
  5. under properties, switch to scene tab, and change Unit Scale to 0.1
  6. notice that the cube's Dimensions are now 0.2m and Size in redo panel says 0.2m also
  7. in redo panel for Add Cube, change Size to 2m

The last step is where the problem occurs.

  • the Scene's Unit Scale are reset back to 1.0 (the 0.1 change was undone)
  • the Dimensions of cube are now 20m instead of the 2m entered in redo panel
  • the Size of cube in redo panel is now 20m instead of the 2m entered in redo panel

Changing Unit Scale does trigger an undo step (changes can be undone). Redo rolls all changes done since the redone action was performed. But, weirdly the inputted redo field is computed before redo's undoing happens (so the field has the value based on the settings at exact time of changing, before the action is undone then redone).

Workaround is to change Unit Scale before adding cube, or delete and re-add cube manually.

**System Information** Operating system: Linux-5.11.0-49-generic-x86_64-with-glibc2.33 64 Bits Graphics card: NVIDIA GeForce GTX 1050 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 470.86 **Blender Version** Broken: version: 3.4.1, branch: blender-v3.4-release, commit date: 2022-12-19 17:00, hash: `55485cb379` Worked: (haven't tested) **Short description of error** Whenever the redo menu is used, any recent changes to unit scale are undone. When this happens, the redone action can be scaled incorrectly. **Exact steps for others to reproduce the error** 1. start blender with factory settings 2. delete default cube, then re-add cube (lol) 3. expand the redo panel for `Add Cube`, and notice that the cube has Size `2m` 4. open the `N` panel, switch to `Item` tab, and notice Dimensions are `2m` 4. under properties, switch to scene tab, and change Unit Scale to `0.1` 5. notice that the cube's Dimensions are now `0.2m` and Size in redo panel says `0.2m` also 6. in redo panel for `Add Cube`, change Size to `2m` The last step is where the problem occurs. - the Scene's Unit Scale are reset back to `1.0` (the `0.1` change was undone) - the Dimensions of cube are now `20m` instead of the `2m` entered in redo panel - the Size of cube in redo panel is now `20m` instead of the `2m` entered in redo panel Changing Unit Scale does trigger an undo step (changes can be undone). Redo rolls all changes done since the redone action was performed. But, weirdly the inputted redo field is computed before redo's undoing happens (so the field has the value based on the settings at exact time of changing, before the action is undone then redone). Workaround is to change Unit Scale before adding cube, or delete and re-add cube manually.
Author
Member

Added subscriber: @gfxcoder

Added subscriber: @gfxcoder
Member

Added subscriber: @PratikPB2123

Added subscriber: @PratikPB2123
Member

Hi, thanks for the report. As far as I understand root issue is same as #78171 (Adjust Last Operation: Other changes outside that panel are reverted back automatically)
I'll mark this as duplicate. Feel free to reopen if you think both are different :)

Hi, thanks for the report. As far as I understand root issue is same as #78171 (Adjust Last Operation: Other changes outside that panel are reverted back automatically) I'll mark this as duplicate. Feel free to reopen if you think both are different :)
Member

Closed as duplicate of #78171

Closed as duplicate of #78171
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
BlendFile
Interest
Collada
Interest
Compatibility
Interest
Compositing
Interest
Core
Interest
Cycles
Interest
Dependency Graph
Interest
Development Management
Interest
EEVEE
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
Metal
Interest
Modeling
Interest
Modifiers
Interest
Motion Tracking
Interest
Nodes & Physics
Interest
OpenGL
Interest
Overlay
Interest
Overrides
Interest
Performance
Interest
Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds & Tests
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
Interest
Vulkan
Interest
Wayland
Interest
Workbench
Interest: X11
Legacy
Blender 2.8 Project
Legacy
Milestone 1: Basic, Local Asset Browser
Legacy
OpenGL Error
Meta
Good First Issue
Meta
Papercut
Meta
Retrospective
Meta
Security
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
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 Info 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
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#103647
No description provided.