I'm a developer and enjoy using Blender, creating patches, addons and animations
- User Since
- Aug 22 2011, 2:53 PM (390 w, 5 d)
This is how the triangulation works. It's almost impossible calculate this type of polygon fill (you can see the same limitations in other 2D softwares)
Fri, Feb 15
This commit solves T61456 also.
This must be solved with the yesterday commit 76747d0a1158
Thu, Feb 14
Wed, Feb 13
Yes, this is a limitation of the current drawing method. We are looking for a solution, but it's not easy to fix without adding a lot of drawing overhead.
Tue, Feb 12
@Dalai Felinto (dfelinto) Yes, I think this is the issue... the eraser poll return false because no active strokes, so the next operator is executed.
Really Ctrl+F must be removed. This is a code from old grease pencil. I'm going to remove this keymap.
69b2f5268114-windows32 has brush damaged... maybe it's the template.
Mon, Feb 11
I think we can close this report because the crash is fixed. If we need work on modal operators, we can reopen it or create a new task.
The eraser brush is damaged and the same for the default draw brush.
@Jacques Lucke (JacquesLucke) I got to open it once...now get the assert. The problem is related to brushes. They have forgotten the gp_settings... I'm investigating.
Sun, Feb 10
I cannot reproduce in Windows 10.
If you can open the file with the fix, the corruption is fixed (the read process review the error and fix it automatically). THe reason of the corruption is more related to modal operators.
Sat, Feb 9
I have done a change, and now the open file crash has gone (b85d5dd9b1a0).
I can see the crash opening your file, but it looks the file gets corrupted for any reason.
Thu, Feb 7
Wed, Feb 6
Tue, Feb 5
Mon, Feb 4
Sun, Feb 3
@Benjamin Humpherys (brhumphe) Must be fixed now!
I have removed the default flag from UI, and now all it's internal. It was a easy fix and we don't need change anything in tool system or brush management. Really, to have a external flag to decide default eraser was a little weird.
Maybe one solution would be remove from interface the "default" eraser toggle button and set internally to the last used eraser. In this way always will use the last used eraser.
Yes, it's not a bug, but we could change how works today. There is a problem here, @Campbell Barton (campbellbarton) redesign how the current brush is used with Paint mode and I don't really fully understand how it's working.
We know this issue and the dependency with Zoom factor. We are working to improve the tool.
Sat, Feb 2
This is a problem with the size of topbar, not only a grease pencil problem.
Fri, Feb 1
I have been looking at the code and the missing feature is in gp_stroke_delete_tagged_points() function and not only affect the cutter, but any delete operation when the stroke is cyclic.
Thu, Jan 31
This is not a bug, it's a limitation of the box primitive (same for circle).
Wed, Jan 30
Tue, Jan 29
I think we can merge it.
This is problem we know. There is already a tasks for this T59425
@Sergey Sharybin (sergey) I have done the change (remove any <DEG_get_original_id>) in greasepencil object branch to test the draw manager. If all works fine, I will move the change to master.
Mon, Jan 28
What do you mean with clamp? Could you paste a screenshot of the parameter?
Sun, Jan 27
I cannot reproduce it. I have added segments to the default cube and delete all ans the panel is still visible.
Delete all remove all measures, but I don't see any relations to Blender installation.
Sat, Jan 26
The simplify reduce the number of points, if you have too much the noise is furry. It's good idea keep simplify modifier and sometimes Simplify+Smooth to get smooth results. If you viewport is too slow, set the modifiers to render only.
@Brecht Van Lommel (brecht) Could you take a look on this? I don't know why is not working. @Dalai Felinto (dfelinto) duplicated the object modifier to grease pencil modifiers basics and after that I added all the modifiers.
Fri, Jan 25
@Campbell Barton (campbellbarton) Could you take a look to the toolsystem assert?
@Paulius Mscichauskas (freemind) I have done small change that fix the issue. Could you test (you need compile yourself or wait for tomorrow build).