Transformation constraint inconsistent behavior (scale) #48136

Closed
opened 2016-04-13 11:52:48 +02:00 by KiJeon · 10 comments

Blender Version
Possibly all versions?

Short description of error
While working on a project, I discovered an inconsistent behavior in the transformation constraint.

Because drivers have no way of referencing "self" value (as done in After Effects expressions, which is a needed feature, in my opinion) I found myself using the transformation constraint a lot to be able to manually alter a transformation parameter (location/rotation) beyond a driven value.

But that's the thing: I can have control of location and rotation, but not scale. As soon as the scale parameter is set, it's locked unlike location and rotation.

I'm not entirely sure if this would be more akin to a design flaw than a bug, but I thought I'd report just in case (couldn't find a discussion of this anywhere).

Exact steps for others to reproduce the error
Based on a (as simple as possible) attached .blend file with minimum amount of steps

**Blender Version** Possibly all versions? **Short description of error** While working on a project, I discovered an inconsistent behavior in the transformation constraint. Because drivers have no way of referencing "self" value (as done in After Effects expressions, *which is a needed feature, in my opinion*) I found myself using the transformation constraint a lot to be able to manually alter a transformation parameter (location/rotation) beyond a driven value. But that's the thing: I can have control of location and rotation, but not scale. As soon as the scale parameter is set, it's locked unlike location and rotation. I'm not entirely sure if this would be more akin to a design flaw than a bug, but I thought I'd report just in case (couldn't find a discussion of this anywhere). **Exact steps for others to reproduce the error** Based on a (as simple as possible) attached .blend file with minimum amount of steps
Author

Changed status to: 'Open'

Changed status to: 'Open'
Author

Added subscriber: @0o00o0oo

Added subscriber: @0o00o0oo

Added subscriber: @Sergey

Added subscriber: @Sergey

That is really hard to tell if issue you're encountering is a bug or not. Please always attach .blend file which demonstrates the issue you've got.

Currently it's sounds more like a limitation of a constraint which is not really considered a bug.

That is really hard to tell if issue you're encountering is a bug or not. Please always attach .blend file which demonstrates the issue you've got. Currently it's sounds more like a limitation of a constraint which is not really considered a bug.
Author

I'll do you one better than a .blend. Show and tell:
TransformationConstraintScaleConstriction.gif

I think that should clearly convey what behavior I was expecting vs. reality. As you can see, the location and rotation are still manually adjustable even when the transformation constraint is set, but scale isn't.
It seems to me the location/rotation function as relative numbers (which is great), but scale functions as absolute.

And I fear you're right about it being a limitation, but.. here's to hoping, haha.

I'll do you one better than a .blend. Show and tell: ![TransformationConstraintScaleConstriction.gif](https://archive.blender.org/developer/F303288/TransformationConstraintScaleConstriction.gif) I think that should clearly convey what behavior I was expecting vs. reality. As you can see, the location and rotation are still manually adjustable even when the transformation constraint is set, but scale isn't. It seems to me the location/rotation function as relative numbers (which is great), but scale functions as absolute. And I fear you're right about it being a limitation, but.. here's to hoping, haha.

Added subscriber: @mont29

Added subscriber: @mont29

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Bastien Montagne self-assigned this 2016-04-22 19:33:02 +02:00

Thanks for the report, but this is a known limitation (commented in code), which we cannot address currently because it would break many existing rigs, unfortunately…

Thanks for the report, but this is a known limitation (commented in code), which we cannot address currently because it would break many existing rigs, unfortunately…
Author

I'm still bumping up against this problem. Are there plans to remedy this limitation in 2.8? Even if it breaks older rigs, I'd be glad to have this limitation removed going forward.

I'm still bumping up against this problem. Are there plans to remedy this limitation in 2.8? Even if it breaks older rigs, I'd be glad to have this limitation removed going forward.
Author

Running into this issue again. Could this be possibly be fixed with the new depsgraph or something?

Running into this issue again. Could this be possibly be fixed with the new depsgraph or something?
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
3 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#48136
No description provided.