- User Since
- Apr 15 2017, 11:30 PM (127 w, 13 m)
Jun 14 2019
yes, still happening, following the same steps and here's a video, now I understand, it moves the frame one frame further without updating the frame that should be drawn upon to (active frame??) when you draw it places the strokes in the old frame, then going from draw mode to object mode and back to draw mode when you place a stroke it updates and places the strokes in the new current frame. Ok I change the issue, it doesn't get corrupted, sorry, apparently it doesn't update the active frame, for example If I change the frame with the arrow keys and draw it draws in the current frame.
May 17 2019
Apr 16 2019
I ran blender --debug-all and --debug-gpu and stored the output for each one, if it helps
I'm using amdgpu-pro drivers. The ones are supported
Apr 15 2019
Mar 31 2019
Mar 22 2019
To hide and unhide collections you have to change the layer collections, like this:
for coll in bpy.context.view_layer.layer_collection.children: coll.hide_viewport = False
What you are doing is hiding the collection for all views (right click on collection > visibility > disable in view ports), so if your collection was hidden before and you execute your code then you are hiding what was hidden before, and then when you unhide with your code it returns to the initial hidden state.
Mar 19 2019
Mar 17 2019
Mar 11 2019
I can confirm this with all types of selection, box selection, circle selection, and lasso selection, they act like the cutter tool
Mar 9 2019
Mar 6 2019
Blender is multiplying the number of render samples to the denoise clean pass
Mar 5 2019
I tried to make it as simply as possible, 3 drivers controlling the RGB channels of one light, with 2 properties in one empty and one script appending a function to the namespace, also appended a video.
Feb 22 2019
Feb 6 2019
Jan 31 2019
Jan 28 2019
Hi, when you refer to "its contents" it also includes the objects themselves or only the collection hierarchy?