Use other frame range for new motion paths instead of 1-250 #93047
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
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender#93047
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?
The new motion path feature was just added recently; however, when creating a new motion path, the default frame range is 1-250.
The idea is to replace this useless range to a context dependant one.
Many frame ranges possible for this purpose :
Options :
1- Make by default the range to be the scene preview range.
2- Or, the "Path type" property could be changed to "Frame range", and contain these situations :
Changed status from 'Needs Triage' to: 'Confirmed'
Added subscriber: @Kdaf
Use scene frame range for new motion paths instead of 1-250to Use other frame range for new motion paths instead of 1-250Added subscriber: @LucianoMunoz
I think what you propose is generally correct, I'd also like to see a proposal for these options to be implemented in the right click menu for creating motion paths.
which is where I feel we should put more energy because now it's the actually more handy one that i believe animators use way more.
I think a dropdown could fit there with all options listed :
What I think would be perfect is to have the start and end property exposed, but slightly darker, and when modifying a defined range( ex preview range ), it switches to custom range (normal light then).
Added subscriber: @dr.sybren
This design task was discussed in the last Animation & Rigging module meeting. Overall people are positive about the design. Especially thearound frameand*selected keyframe range// options are already highly anticipated :)
I think @LucianoMunoz 's idea is also good. By having the "Add Motion Path" functionality as an operator that can be triggered at any time, it can pick up on the then-appropriate values. For example, if there are any keyframes selected it can use that range, and if not it could either go for "around frame" or the preview/scene frame range. Such context-dependent values are harder to do from the current properties panel (finding the first/last selected keyframes is kind of a slow process, so I wouldn't do that on every redraw of the panel).
I'm so sorry for my inactivity. I'll do it in the following days.
Welcome back dude :)
This issue was referenced by
1558b270e9
Changed status from 'Confirmed' to: 'Resolved'
This issue was referenced by
4e57b6ce77