"Follow path" constraint subframes calculated incorrectly #29113

Closed
opened 2011-10-31 18:42:39 +01:00 by Miika Hamalainen · 5 comments

%%%Subframes calculated for "Follow Path" constraint's "Offset" property are calculated incorrectly, making object appear ahead it's real position. Same thing probably happens with other Blender components as well, but at least with this one. :)

How to reproduce:

  • Red cubes are position markers showing where object should be each frame.

  • Blue cube's location is animated by keyframes. It's interpolated correctly.

  • Green cube is animated by the follow path constraint. It's drawn more ahead for every subframe.

However, if you render whole frames or preview it through the timeline, it's shown correctly.

That scene is rendered with full sample motion blur of 6 samples and shutter time of 3 frames. So from the code point of view, the last "blur sample" is rendered at full frame (scene->r.cfra) of 1, and subframe (scene->r.subframe) of 3.0.

(This isn't isn't a bug in full sample motion blur calculation but in animation system. I originally run into this while testing Dynamic Paint subframes. :)%%%

%%%Subframes calculated for "Follow Path" constraint's "Offset" property are calculated incorrectly, making object appear ahead it's real position. Same thing probably happens with other Blender components as well, but at least with this one. :) How to reproduce: * Open the "curve_subframe_bug.blend". (Attachment) * Render the image. It looks something like this: http://www.miikah.org/blender/curve_subframe_bug.png - > Red cubes are position markers showing where object *should* be each frame. - > Blue cube's location is animated by keyframes. It's interpolated correctly. - > Green cube is animated by the follow path constraint. It's drawn more ahead for every subframe. However, if you render whole frames or preview it through the timeline, it's shown correctly. That scene is rendered with full sample motion blur of 6 samples and shutter time of 3 frames. So from the code point of view, the last "blur sample" is rendered at full frame (scene->r.cfra) of 1, and subframe (scene->r.subframe) of 3.0. (This isn't isn't a bug in full sample motion blur calculation but in animation system. I originally run into this while testing Dynamic Paint subframes. :)%%%
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'

%%%Joshua: old style motion blur is using subframe steps. Can you check if the new animation system correctly uses it?
Thanks!%%%

%%%Joshua: old style motion blur is using subframe steps. Can you check if the new animation system correctly uses it? Thanks!%%%
Member

%%%For starters, this file is going about things in the wrong way.

  • If you're going to animate the constrained object moving along the path by animating it through the constraint, you should change it to "fixed position" and then animate the "offset factor" slider (0-1 value).
  • Otherwise, the object moving along the path should be done by animating the path's "evaluation time" property.

The "offset" value you've animated here actually acts like a user-controlled "time lag" on top of the curve evaluation time (+ subframe offset) if "fixed position" is disabled. %%%

%%%For starters, this file is going about things in the wrong way. - If you're going to animate the constrained object moving along the path by animating it through the constraint, you should change it to "fixed position" and then animate the "offset factor" slider (0-1 value). - Otherwise, the object moving along the path should be done by animating the path's "evaluation time" property. The "offset" value you've animated here actually acts like a user-controlled "time lag" on top of the curve evaluation time (+ subframe offset) if "fixed position" is disabled. %%%
Member

%%%EDIT:
However, checking more carefully (i.e. even in case with animating "evaltime" directly), it seems that the problem here was actually applying the subframe offsets, instead of forgetting to apply them. This is because by the time the constraint gets the time, it has already had time offsets applied, but applying manually just compounded the problem!

So, fixed in svn!
%%%

%%%EDIT: However, checking more carefully (i.e. even in case with animating "evaltime" directly), it seems that the problem here was actually applying the subframe offsets, instead of forgetting to apply them. This is because by the time the constraint gets the time, it has already had time offsets applied, but applying manually just compounded the problem! So, fixed in svn! %%%
Member

Changed status from 'Open' to: 'Resolved'

Changed status from 'Open' to: 'Resolved'
Sign in to join this conversation.
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
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/blender#29113
No description provided.