FIX: When motion path is updated, make sure frame range is inclusive #107753

Closed

Nate Rupsis wants to merge 1 commits from nrupsis/blender:motion-path-off-by-one-bug into main

pull from: nrupsis/blender:motion-path-off-by-one-bug

merge into: blender:main

blender:main

blender:blender-v4.0-release

blender:blender-projects-basics

blender:universal-scene-description

blender:brush-assets-project

blender:temp-sculpt-dyntopo

blender:blender-v3.6-release

blender:tmp_libupdate_41

blender:blender-v3.3-release

blender:anim/animation-id-113594

blender:bridge-curves

blender:sculpt-blender

blender:asset-browser-frontend-split

blender:asset-shelf

blender:tmp-usd-python-mtl

blender:tmp-usd-3.6

blender:blender-v3.5-release

blender:blender-v2.93-release

blender:realtime-clock

blender:sculpt-dev

blender:gpencil-next

blender:bevelv2

blender:xr-dev

When changing the target branch, be careful to rebase the branch in your fork to match. See documentation.

Conversation 2 Commits 1 Files Changed 1 +2 -1

1 Commits

Author	SHA1	Message	Date
Nate Rupsis	9f04278736	When motion path is updated, make sure frame range is inclusive	2023-05-08 14:18:36 -04:00