Tue, Oct 10
Mon, Oct 9
Confirmed. Crash is:
Sat, Oct 7
@Bob Smith (uvwxyz) - Mirror, Radial, Tiling could be displayed on a single line. Lock IMHO isn't needed since the reason to show text is to show you geometry not in the view is being edited.
Thu, Oct 5
@Campbell Barton (campbellbarton) I agree having text in the corner has a good balance in terms of easy to notice vs. too distracting. It's kind of a separate issue but I have always thought the text in the 3d view should be white/light with a black outline or vice versa (which is legible on any background) because of situations like these: (the second image is the auto key you mentioned).
For me at least, it doesn't seem like too much info on the brush since the indicator disappears while sculpting. Yes this is a useful feature while working with asymmetry model. You want the brush to remind you if the symmetry is on or off.
Something similar would be great to have for the lock option. The lock option needs this option so much because it used for in a short amount of time.
But "radial symmetry" or "tiling offset"?
Having a hint that symmetry is on seems useful since as you say - it can be left on by accident.
Committing fix, note this patch misses a brace: see our code style guide (some old code doesn't follow)
Sun, Oct 1
Thu, Sep 28
Sep 21 2017
Sep 15 2017
Here's a fix for that last issue D2843
Sep 13 2017
I think it's doing what It's supposed to. You can mangle up the mesh using any brush type if you sculpt a certain way with particular settings.
Sep 12 2017
Sep 11 2017
I've added it to the list here:
Confirmed on Windows 8.1 (rB65582e7) with Intuos Pro 5.
I think it's a divide by zero in paint_stroke_integrate_overlap in paint_stroke.c
Sep 10 2017
I can reproduce it in the 2.79 RC2 using a wacom intuos 4 stylus, mouse works fine.
nvidia 1070 drivers 382.33
Just noticed a new detail; when this occurs, the object dimensions change to 'inf' then to nan after I try to change them.
The earliest version which has this issue for me is 2.72... 2.71 and earlier is OK.
Couldn't redo this with dyntopo or multi-res or neither.
Sep 8 2017
Sep 7 2017
The issue is that the brush painting code in the image editor does not not work at a sub-pixel level. Supporting that would be good to improve quality, but it's a lot of work and for that reason out of the scope of what we handle in this bug tracker.
The crux of this seems to be - "it's not a bug because the code works as intended, therefore it's a feature request" vs "the original design specification has a bug".
Sep 6 2017
This is no bug, period. Triaging tracker is heavy and annoying enough task not to have to do it twice.
Some examples drawn in the 2d editor and 3d viewport:
I can't see how this would be considered either a feature or enhancement.
Sep 5 2017
Thanks for the report, but that is no bug, rather feature/enhancement request. which are not accepted on this tracker.
Sep 3 2017
I'm thinking this is normal with a low pixel width line.
I wouldn't think it would generate a scalable vector type file.
I'll let someone else decide though.
Sep 1 2017
Aug 24 2017
Aug 19 2017
ok, sorry for that.
No point in keeping twice the same report open…