- User Since
- Nov 21 2016, 12:05 PM (130 w, 1 d)
Fri, Apr 26
My apologies. In your own time.
I'm still experiencing this issue with the latest build.
Tue, Apr 23
Mon, Apr 22
Surprised no-one has given any attention to this bug report.
This is a serious problem with the renderer.
I've had to spend many hours going through each frame of my animation looking for bad cuts since discovering this bug.
Please look into it.
Apr 18 2019
I think I'm experiencing the same bug: T63697
I tried to reproduce it with the same file but I couldn't.
I think the bug is best observed in the file I've uploaded, where the timeline markers are clearly there and linked to camera objects but they are all simply ignored.
The issue appears to be resolved by blender-2.80.0-git.03bd024c077d
Not sure what good it'll be to upload the problematic file, anyway I've reduced it to its core elements but not sure if the issue will reproduce itself for others.
It's very long, and the only way to test it is to render lots of it from the 'editing' scene (which refers to the 'home' scene with a scene strip).
Apr 16 2019
Sorry, I was at fault. It's working fine.
Apr 11 2019
Sorry, forgot to follow up on this.
If I post an example and detailed steps tomorrow will you re-open or should I start a new bug report?
Apr 10 2019
I'm getting this problem a ton recently and it's very annoying.
Apr 9 2019
Apr 7 2019
Apr 6 2019
Not without uploading a large blend file with about 10 minutes of animation I'm afraid.
I tried recreating it in a simplified file but it rendered correctly every time.
Apr 5 2019
Apr 4 2019
Mar 30 2019
Mar 16 2019
I'm also experiencing this, but I'm sure I had the same issue back when I first tried 2.8 (December 2018)
Mar 11 2019
Dec 17 2018
Oct 30 2017
Jun 24 2017
No it has nothing to do with the modifers. Did you set remember to set use_base_parent=True, use_hierarchy=True?
Jun 23 2017
May 29 2017
May 22 2017
Mar 12 2017
I posted the question on BSE.