Limit Scale does not Limit Scale on the Minimum Value #37623
Labels
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
8 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#37623
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Operating system and graphics card
OS X 10.8.5
Graphics AMD Radeon HD 6490M 256 MB
Blender Version
Broken: Blender 2.69
Short description of error
The Limit Scale constraint fails with a minimum value of 0.0. The user is able to bypass the minimum and scale all the way "down" to the negative maximum value. It is easiest to bypass the minimum value at 0.0. It is also possible at values close to zero such as 0.2 or 0.4, but the user must move the mouse rather quickly to jump over the minimum value into the negative side.
Exact steps for others to reproduce the error
This is reproducible with the default blend or with the attached.
limit_scale_bug.blend
Changed status to: 'Open'
Added subscriber: @DanielHoughton
#47692 was marked as duplicate of this issue
#40720 was marked as duplicate of this issue
#40873 was marked as duplicate of this issue
#38167 was marked as duplicate of this issue
Added subscriber: @willi-2
I agree.
"Limit rotation" also does not work (as expected). I post it here because it's closely related or even has the same cause:
Test_100_0001.zip
Z is limited to the range 180..270 degrees. Press - [x] - [x] to rotate the object around the Z axis. The object can not be rotated at all. I expect to be able to rotate it within the range 180..270.
Added subscribers: @BassamKurdali, @JoshuaLeung
◀ Merged tasks: #38167.
Added subscriber: @BeornLeonard
This would be great to get fixed soon!
When a minimum scale is above zero and the user scales below zero, the bone stops scaling at the minimum limit, but then flips to a negative scale as soon as the user input passes zero.
When the minimum scale is set to zero or a negative number, the constraint seems to do no lower limiting at all.
This is another one of those tricky matrix decomposition problems that we also have with rotations. In this case, the problem is that we cannot tell which axis got a negative scale factor - we just know that one of them did.
I'm beginning to think that maybe we need to overhaul how transforms get passed through the transform stack - basically, making it so that raw euler and scale values get passed through the stack, get modified by any math operations which modify the matrix, and are used to temper any results (i.e. doing compatible_euler() on rotations, and checking for -ve's for scale) as they go through. Of course, it helps that such an approach would be dead easy with some of the things I'm planning with the depsgraph refactor, but would be slightly trickier to retrofit onto the current pipeline.
Added subscriber: @alekulyn
◀ Merged tasks: #40720.
Added subscriber: @supergra
Added subscriber: @karja
◀ Merged tasks: #40873.
Added subscriber: @ideasman42
Moving to TODO, this isnt mistake in code, more something we could support (but as it turns out not trivial to do).
Listed here: http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Animation#Constraints
Added subscriber: @Cenda
Added subscriber: @rwman