Motion Paths off by one #70381
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#70381
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: Darwin-17.2.0-x86_64-i386-64bit 64 Bits
Graphics card: NVIDIA GeForce GTX 1050 Ti OpenGL Engine NVIDIA Corporation 4.1 NVIDIA-10.27.6 378.10.10.10.20.109
Blender Version
Broken: version: 2.81 (sub 12), branch: master, commit date: 2019-09-29 23:17, hash:
64c222ff58
Worked: (optional)
Short description of error
It seems that the end frame will calculate up to but exclude the end frame, which is inconsistent with the rest of Blender.
(ie - if you want to include frame 40 in the motion paths, you must choose to end the motion paths on frame 41. But if you want to end your animation and render it to frame 40, you set the end frame to be frame 40)
This has been present in 2.79 as well, it is unneccessary though afaics (but I need to double-check the following comment still)
Also in 2.8 (that was not present in 2.79) in that the indication around the current frame (green fading lines) are "off-by-one" [drawn at the previous frame]
Exact steps for others to reproduce the error
motion_paths.blend
this one is not considered a bug
blender_bug_MOTION_PATHS.mp4
Added subscriber: @WayneDixon
Added subscribers: @LucianoMunoz, @Sergey, @dr.sybren, @lichtwerk
I think the issue about the changed range not reflected in the update mechanism is not really a bug, each motionpath that is updated acts upon the range it has been created from.
This could be changed I guess, but would not be considered a bug in my opinion.
The "off-by-one" I can confirm (in 2 forms):
Will look into both "off-by-one" issues, for the issue about "changed range not reflected in the update mechanism", I would like to hear an opinion of @dr.sybren, @LucianoMunoz, @Sergey (but like I said, I would not consider this a bug...)
Will confirm (temporarily) for the "off-by-one" issues...
Motion Paths don't update correctly.to Motion Paths off by one (also updating is not taking changed range into account)I believe i had seen this firs hand a couple of days ago, will test again.
So after talking to @dr.sybren, looks like the "update mechanism" is not considered a bug, will update report description accordingly
Motion Paths off by one (also updating is not taking changed range into account)to Motion Paths off by oneThat, and a report should not be about two things at once anyway.
Changed status from 'Confirmed' to: 'Resolved'
This seems to have been fixed in the mean time already:
@WayneDixon It looks like part of your report was working as intended (the path update mechanics), and part has been fixed already. I'll mark this report as 'Resolved' because of the latter. If we have totally misunderstood your issues, please feel free to add a comment or write a new bug report to clarify this.
@dr.sybren: what about this then?:
Also not sure about the drawing (this might be nitpicky, but...shouldnt the green part be around the current frame?):
2.8 (current frame is black and next frame seems to be fully green)
2.79 (both current frame and next frame seem to be fully green?)
These (endframe not included & drawing) could be split into two different reports, but I actually assume this is rooted in the same issue...
Changed status from 'Resolved' to: 'Confirmed'
After digging into it, it turns out they aren't rooted in the same issue. The endframe not being included is as it is designed now, so not a bug. The drawing being off by one is a bug, though.
This issue was referenced by
c20caec7f0
Fixed:
Changed status from 'Confirmed' to: 'Resolved'
thx digging and fixing!