I downloaded the May 21 build and just tried it with the same file. Still crashes in Cycles, regardless of GPU or CPU. I started deleted objects and rendering and it continued crashing. In fact, when I deleted all objects, it still crashed. Is there a way to delete the textures from a file? Or can I disconnect them? As mentioned before, it only crashes in this file and other older versions of the same root file. Not in any other. Obviously some weird anomaly.
May 21 2019
May 16 2019
I tried the same file using the 16-May build and it crashed. But other files do not crash. I'll keep experimenting with the crashed file and see what I can find.
May 15 2019
May 9 2019
My apologies. I started a bug report, but then I couldn't reproduce the bug on any files except for the one, so I'm trying to figure it out. But I didn't know how to delete the empty bug report.
Apr 9 2019
Just downloaded and opened the new build. You guys are the best!
Mar 29 2019
@Julien Kaspar (JulienKaspar) Agree with all. Adding to it, in my work, the ability to control keying of the camera/render visibility of an object is even more important than viewport visibility. Hopefully, both are something that can be addressed.
Mar 28 2019
do I gather from this thread that it is currently not possible to keyframe the render icon to affect the visibility of objects during animation, as we can do in 2.79? If it's not currently possible, is that likely the change? It's an extremely helpful and time-saving feature in my work.
Mar 18 2019
Hi. Anything new to report on the issue of highlighting in the Dope Sheet?
Mar 1 2019
Feb 7 2019
I'm not sure if this will be helpful or not, but here's the .blend file. When I create a new camera, the Z location shows up right below the X and Y where it normally does. So I must have done something to the first camera that changes the behavior.
Feb 6 2019
Jan 31 2019
It is working using the graph editor, but the workflow makes keyframing very slow compared to the dope sheet.
Hello again. I'm using build 2019-01-31 01:07 Hash: 8c8979067490 Branch: blender2.7 and again having all kinds of issues with camera keyframes. I set a keyframe, I move ahead several frames, move the camera (or rotate) and it snaps back to the original spot. Sometimes all the time, sometime most of the time. But regardless of the right-click options I choose to clear or set or delete keyframe, I cannot get it to work consistently correctly.
Jan 24 2019
Jan 23 2019
Thank you. Build 2019-01-23 00:32 Hash: cd 3b5024be1a is working great this morning.
Jan 22 2019
For someone like me who doesn't know how to apply patches, is there a timeframe yet for resolving the issue in an upcoming Beta release on the blender.org page?
Jan 16 2019
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.
Jan 15 2019
Jan 2 2019
Thanks, Ian. I'll give this a try with the newest build. Also, have you / has anyone else noticed that in the dope sheet, there are issues with the text of the selected object(s) not becoming bold, and its line not being highlighted? Seems like sometimes it works and other times it doesn't.
Dec 19 2018
I downloaded build a2466049376 just now and tried it. All works fine.
Dec 17 2018
Dec 4 2018
Dec 2 2018
Sorry. I just discovered that you no longer need to hold down the Crtl key. My mistake. It works fine.
Nov 30 2018
Nov 5 2018
I opened the file, and first, deleted about 15 keyframes with no crash. Then I deleted about 30 and it crashed. Then I reopened the program and deleted the BezierCircle.001.
Where can I go to see exactly what file I uploaded? I was working with a number of variations, and I want to make sure I'm looking at the right one.
Nov 2 2018
Not sure what happened. I just dragged the file in again. I hope.
Nov 1 2018
Oct 30 2018
I deleted about 90% of the objects from the file, then added a bezier circle and parented a camera to it. I could not get the crash to reproduce itself. It's impossible for me to know what changed, and deleting one object at a time and retesting would take an extremely long time. If I come across anything I think might help, I'll let you know.
Hi, and thanks for attending to this. I disconneted the font and it still crashed, but when I deleted the BezierCircle.001 (which I'm using as a guide to track a camera), moving keyframes no longer crash the program. And I just relinked my text to the HLBC font and moving keyframes still works, so it was definitely something with the bezier circle. As a test, I just added a new BezierCircle and parented my camera to it. When I tried to move a keyframe, the program crashed again.
Oct 29 2018
FYI, the same thing happens when selecting multiple keyframes with the B box select. As soon as you trying moving them with G, the program crashes.