Page MenuHome

Motion Path - Changing endframe clamps startframe to 1
Open, Waiting for Developer to ReproducePublic

Description

System Information
Operating system: Windows 10 Pro 64 bits (10.0, compilation 17134)
Graphics card: AMD Ryzen 5 1500x Quad-Core Processor

Blender Version 2.8 Official release

Motion path changing number automatic and path update

Exact steps for others to reproduce the error

GIF - https://giphy.com/gifs/jovteyAEQr21IYJW1o

Description: Go to the motion path field, place the start frame to 0, change the end frame from any number to another number, exemple, 250 to 30. Then when you press enter the starting frame will always change from 0 to 1 and you have to change the starting frame number again.

2 bug, you have the motion path already done, you change from 0-30 to 0-45 or any other lenth then you press Update range and noting happens, he doesnt change from 0-30 to 0-45 he keeps at 0-30. You need to always delete and make it again.

Thank you for your time.

Details

Type
Bug

Event Timeline

This looks like T70381: Motion Paths off by one (also updating is not taking changed range into account) (will quickly check if the Frame Range Start issue is actually the same thing...)
For bug (2), please refer to T70381 already...

Philipp Oeser (lichtwerk) lowered the priority of this task from Needs Triage by Developer to Waiting for Developer to Reproduce.Thu, Oct 17, 12:01 PM

Might be a problem in rna_AnimViz_path_end_frame_set, rB0049c22ad90f.
I think this is best checked together with T70381 (but not the same issue on first sight -- even though related).
Needs a bit more investigation, will claim for now...

Philipp Oeser (lichtwerk) renamed this task from Motion Path - Changing number automatic and path update to Motion Path - Changing endframe clamps startframe to 1.Thu, Oct 17, 12:15 PM