Transform F-Curve: Scale #42631
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
5 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#42631
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: Windows 8.0
Graphics card: Intel HD Graphics
Blender Version
Broken: 2.72b
Worked: Unknown
Short description of error
When a transform strip's uniform scale is selected it is key framed as "Scale X (Transform)"
Exact steps for others to reproduce the error
Add a transform strip and select "uniforms scale" then key frame the zoom factor. Then it will be displayed as transform x which it is not.
Changed status to: 'Open'
Added subscriber: @Blendify
Added subscriber: @ideasman42
Added subscriber: @Sergey
That's not really clear steps for me. Do you mind attaching simple .blend file which demonstrates the issue?
Sure here you go
Bug.blend
Added subscriber: @mont29
Well, yes, technically, it is Scale X which is used for uniform scale, as you can see when disabling that option… Maybe uniform scale should use another variable?
Antony, assigning to you, but not sure we really consider this a bug.
Changed status from 'Open' to: 'Archived'
I would not count this as a bug, it will be cumbersome to add a new property (which will have to be synchronized with the others for ease) just for that and scaleX/uniform scale is pretty self-explanatory.
Is it possible then to make it so that after you uncheck uniform scale the two fields have the same number. Instead of just the x value.
It is possible but why would you do that when the option is there?
It just makes sense that they should be the same number after unchecking the uniform scale
What if someone wants to switch between uniform scale and back with just one toggle? If we do that change you take away that possibility. Do we take away any possibilities by leaving it as is? This is not about preference (If you like it -of course- it makes sense to you), you have to explain the workflow to convince us.
Added subscriber: @jonata
Well, one workflow I could imagine is something like this: after making a lot of keyframes in uniform scale, then I decide to change just the X or Y of some in the middle of my animation. If the keyframes were inserted in both values, I just need to change the desired keyframes. But in the actual state, I would need to copy the X keyframes and paste into the Y keyframes, and then change the keyframes I want.