Page MenuHome

keyframe hair particle timing
Closed, ResolvedPublic


System Information
Operating system: Windows 10 Pro 10.0.16299 Build 16299
Graphics card: NVIDIA GeForce GTX 1070

Blender Version

Date: 2019-01-14 11:43
Hash: 7707bf203c0f

Short description of error
When I try keyframing the End value under the Timing tab in ParticleSystem, the number keeps jumping back to 0.0 or whatever the previous number was.

Exact steps for others to reproduce the error

  1. add particle system to object (in this case, "quick fur")
  2. add keyframe in dope sheet and press I to add beginning keyframe on End
  3. move to a new frame in dope sheet and then either slide or type in new value for End.
  4. value keeps returning to previous keyframe value.

I've tried all the right-click options I can find, but none seem to make the new value stick.

Based on the default startup or an attached .blend file (as simple as possible).



Event Timeline

Jacques Lucke (JacquesLucke) triaged this task as Needs Information from User priority.

Thanks for the report.
Could you prepare and upload a .blend file that makes it easier to reproduce the issue, please?

I'm a bit confused. For normal particles the "End Frame" value should not be animateable and for hair this property does not exist.

Perhaps I am using the wrong terminology. Here's a screen shot showing the area under "Timing" that I'm having an issue with. When the timeline is at 34 frames, I want the End value to be 1.000. At frame 1, I want it to be 0.000. This works in 2.70b, but in 2.80 when I drag the value down to 0, or type in 0 (or any number) while on frame 1, it jumps back to 1.000. Screen shot 3 shows the same problem in a new file with quick fur added to the cube. In frame 24, I set a keyframe for value .464. In frame 43, I tried setting a new value for "End" and it keeps jumping back to .464.

Jacques Lucke (JacquesLucke) raised the priority of this task from Needs Information from User to Needs Triage by Developer.Jan 16 2019, 5:08 PM
William Reynish (billreynish) triaged this task as Confirmed, Medium priority.

Can confirm that it's not possible to keyframe this property. In 2.7x it was, so this is a regression since then.

Hi, I noticed that this patch seemed to "fix" the issue:

but this needs to be reviewed by a core developer I think

I can't reproduce this bug in last master. Thanks very much to blender devs for their work on the fix/es

This seems to have been fixed by the recent particles commit by @Sergey Sharybin (sergey)