- User Since
- Oct 14 2004, 8:42 PM (765 w, 3 d)
Tue, May 21
Thank you for the quick reply. It might make a difference, hard to tell. But it is important for a developer to be able to reproduce the bug. So what you could try is to build the same scene from a new empty file, because you said it's quite simple. Try to add the background movie and test, then add similar strokes and see if that was the cause for the crash.
I can't reproduce this problem on today's build hash: 21d065af5d70 it works without problems.
Perhaps this just changed today - but it is not located in Frames > Interpolate > Sequence, but instead in the 3D view in Strokes > Interpolate > Sequence.
I drew a stroke on two frames, moved the current frame in between and called interpolate sequence. I tried this both on an Intel UHD 620 and an NVIDIA 1060 GPU just to be sure.
May 4 2019
Upon looking further, I discovered scene.frame_set(), which works and is probably better anyway. But still, a crash is disproportionate and this worked yesterday, so I'll keep this report open.
Apr 16 2019
Hi Atomic and Sybren,
Jan 16 2019
This no longer happens in the latest builds, so I'm changing the status to resolved. Please excuse my late response and thanks for fixing it!
Dec 17 2018
A user of The Grove reported that this bug now sometimes causes crashes when opening a Blender file, making the file unusable. I can confirm this, and Blender crashes with a segmentation fault and the following crash.txt, which leads me to believe that it is a bug in the dependency graph.
Dec 14 2018
It actually got worse. I just made a fresh build on OSX and now particle instanced objects don't show up unless I check "Use modifier stack". This could be a different bug, but I suspect it may be related because I saw that with "make update", a file called "object_relations.c" was updated. And given the terminal message starts with "add_relation", this may be related.
Dec 12 2018
Sep 18 2018
I went ahead and took the plunge into the Blender source and sure enough I fixed it! I submitted a patch at https://developer.blender.org/D3704 along with some more info on indexed writing.
I attached an Alembic file that contains a tree model with several vertex color layers. I tested it extensively in Houdini. Please test it and post back your success or failure. I hope it fixes this bug for at least Houdini and Maya.
Jun 16 2018
Hi Sybren! I've been following this thread with great interest. I've had reports that in addition to the software already mentioned above, Clarisse and Cinema 4D also don't import the vertex colors written by Blender. I have confirmed that with my own tests.