Maniphest T30097

Motion paths range not correct (+ keyframe placement error)
Closed, Resolved

Assigned To
Joshua Leung (aligorith)
Authored By
Olivier Amrein (oenvoyage)
Feb 7 2012, 1:37 PM
Tags
  • User Interface
  • BF Blender
Subscribers
Joshua Leung (aligorith)
Olivier Amrein (oenvoyage)

Description

please open the attached file: it is a simple default scene with cube animated in straight line from 0 to 100
I enabled motion path Around frame. it should display 40 frames before, and 40 after.
but it stops at 50 .
go to In Range tab,
scrub the End value to 20.
Click Calculate Path, it does not update…
workaround is to Clear Paths, then recalculate path
now set End to 100. Clear path, recalculate path.
Go back to Around frame tab.
Now the initial problem is kind of fixed…

I understand the path calculation in not interactive (depsgraph?) but I do not think you first need to clear path, to recalculate…

also Around Frame and In Range are to separate tab, that look supposedly independent….

furthermore you can see the green square (keyframe at frame 50) is misplaced, plus it blinks when you scrub frames

sorry if this is a bit messy, it just shows some problems with motion paths

tested on trunk r43948 , release 2.61 , mac and windows

Event Timeline

Olivier Amrein (oenvoyage) edited a custom field.Feb 7 2012, 1:37 PM
Olivier Amrein (oenvoyage) attached 1 file(s): F17985: motion_path_250.blend.
Joshua Leung (aligorith) added a comment.Mar 8 2012, 11:55 AM

Fixed the current frame indicator bug.

The main problem in this report though I think is related to some mistakes made with the UI design for this stuff. It's been on my todo list for a while, but I'll try to accelerate a fix for this.

Joshua Leung (aligorith) added a comment.May 1 2012, 3:13 PM

Fixed the bug regarding changing the path range.

GUI changes in progress...

Joshua Leung (aligorith) added a comment.May 1 2012, 6:20 PM

Just committed some changes for this. Hopefully this improves the situation.

Joshua Leung (aligorith) changed the task status from Unknown Status to Resolved.May 1 2012, 6:20 PM