Page MenuHome

Usability – "follow path" with nonsensical path-parameters not caught, and I was utterly lost.
Closed, ArchivedPublic

Description

System Information
OS/X High Sierra, MacBook Pro current

Blender Version
2.79b

Short description of error
Usability – obvious-in-retrospect "follow path" mistake not caught

Exact steps for others to reproduce the error
Create an object and a path, then set a "follow path" constraint. Click on the path, and in "Object Data" specify the Evaluation Time but ("I plead n00b1e innocence!") fail to realize the importance of also specifying a non-zero value for Frames

Well, the resulting system behaviors are "genuinely 'WTF?!?!'" (Try it .. you'll see what I mean..)

When I clicked on "Animate Path," Blender sort-of correctly told me that "the path was already animated," but actually it wasn't – because it is nonsensical for either or both of these parameters to be zero. (Oops.) This would have been a stupendous time to alert me to this.

If there are no keyframes, and if the present set of parameters is nonsensical (frames=0), then I think that the software should stop and throw a meaningful exception.

Details

Type
Bug

Event Timeline

Philipp Oeser (lichtwerk) triaged this task as Incomplete priority.Jul 12 2018, 1:10 PM

Not sure I can follow:

  • How are you actually setting a value of zero for Frames (curve.path_duration)? This should be clamped to 1?
  • This should be set to 100 Frames by default?
  • at a value of one for Frames (which should be the minimum), or above one, the system should behave as expected? Also see the manual

Marking as incomplete until we know how it actually happened that Frames can be zero...

More than a week passed without a reply.

Due to the tracker policy, archiving until the required additional information / data is provided.