I made an addon that lets you store presets for some of the view and snap settings in the 3d viewport. I also have a script that I use that switches all of the Viewport Display settings needed for object that is going to be used for retopology (In Front and Wireframe enabled). I think this would be a good approach for the problem of the long setup times when switching tasks in the 3d view. Blender could still allow the power of modifying all of the snap and display settings individually (instead of having separate retopo settings), but also have a preset system built in with a few predefined setups - retopo being one of them. This would make switching to retopology workflow as simple as changing the preset in the display settings and the snapping settings.
Fri, Oct 18
Can confirm, @Pablo Dobarro (pablodp606) : mind checking?
Thu, Oct 17
OKi, back to @Pablo Dobarro (pablodp606) then :)
Think I got a fix.
I think it would benefit to embrace the new Sculpt painting system as well as keep the current vertex color painting mode.
Wed, Oct 16
I guess this can be confirmed then
Tue, Oct 15
Can confirm. (wonder why this hasnt been reported before...)
This looks like the same issue: T58473: Multires: changes not smoothly propagated from low to high, for example with apply base, will merge these reports...
Mon, Oct 14
More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.
Fri, Oct 11
ctrm + m
Wed, Oct 9
Hi, don’t know every much about code and I'm fairly new to blender, can anyone help me out with an explanation on how to fix this issue or which blender scripts to change, I'd very much appreciate it. Thank you!
I'm not sure about flushing the queue where you suggest. handleTabletEvent() does not seem to modify the event in the queue, it just sets some tablet parameters (pressure, tilt) in some window context object, and then presumably some other code uses that info when it comes to processing the event. For drawing, then, you want the latest tablet info available when the event gets processed or else you're always using old pressure data. The only instance where you don't want tablet data smashing is on the leaving proximity event because it leaves tablet mode, and no drawing is going to happen anyway.
can conform this fix works also on astropad and duet.
thanks @Tim Lesher (tim) Carroll (codrus) for this!
@Brecht Van Lommel (brecht) Van Lommel (brecht) is there any reason why this fix can't go in master?
Good catch. I was looking for something like dispatchEvents() yesterday but couldn't find it.
Tue, Oct 8
This may or may not be an acceptable fix, but adding dispatchEvents() when leaving proximity in handleTabletEvent() flushes out the event queue and fixes the issue for me in both grease pencil and texture paint modes:
I can confirm that if I comment out tabletPoint and tabletProximity in WindowCocoaView, the problem goes away. The mouse up messages have tablet information so pressure get released as appropriate. This was just a test; those events are important for tablets with proximity sensors. Also, I found that later events (like window deactivation) were showing tablet events, which would clearly not be the right thing.
I've got a partial answer for what's going on -- will try to pick this up again tomorrow night, but thought I'd pass on some notes.
The same issue happens in the release version of Catalina with Sidecar and an iPad Pro/Apple Pencil.
Mon, Oct 7
It is really easy to reproduce:
This started getting weird with rBd0fb602e2c36 (here sculpt mask strokes would still be visible while doing the stroke, but chances are high these get invisible when stroke ends, then on a new stroke everything gets visible again, ...)
@Philipp Oeser (lichtwerk) I talked with sergey and apparently it only got implemented in 2.79 and didn't transition over to 2.8.
Will confirm for now, I am bisecting atm... [to at least know when this changed...]
@Philipp Oeser (lichtwerk) Just for clarification, Blender does tell the user that "Hide, Mask and optimised display is disabled" when modifiers are being used.
But at some point last year, @Sergey Sharybin (sergey) at least implemented that masks are visible when using shapekeys, as far as I remember. This feature seems to be gone now.
Sun, Oct 6
@Pablo Dobarro (pablodp606) I made a video highlighting the problems with Voxel Remesher and QuadriFlow a bit better:
This should be fixed in D5933, I can make another patch without the shrinkwrap fix.
Sat, Oct 5
I have noticed that Snake Hook correctly fixes the direction when Original Normal is activated, and also press the control key. Together it works, but not separately.
@Demeter Dzadik (Mets) I think it is the former, but since it is super hard finding non-manifolds on a dense mesh, I can't confirm if this is the case. My best guess is that it is Voxel that creates non-manifolds.
We require a .blend file and exact steps to reproduce the issue to be provided.
So if I understand correctly, the issue is either that Voxel Remesh is creating non-manifold or inconsistent face normal mesh OR Quadriflow is doing its safety checks incorrectly, and identifies the mesh as non-manifold, or having inconsistent face normals, when neither of those are true?
Fri, Oct 4
Happened for T69227 as well, not sure what they have in common though. May be a phabricator bug after the latest update.
Hm, I wonder why this didnt get closed automatically?
Thu, Oct 3
I have tried with the latest build, i cannot reproduce it. The thread can be marked solved :)
Hi @Jeroen Bakker (jbakker) this problem still here.
as in picture,left was problem, right are close multithread scuplt in option ,
2,in edit mode,subdived several times
3,switch to sculpt mode
4,create brush texture
5,switch to texture node editor, checked use node
6,back to sculpt mode, checked dynatopo on, set pix to 2
7,draw on mesh
the problem appeared use today master git branch
I can't reproduce this, is this still an issue in the latest builds?
Please try again with the very latest build, there were some fixes in this area:
Wed, Oct 2
Caused by rBc31a849a1474.
Tue, Oct 1
@Henrik Abreu (kafonah) please do not reopen old tasks like that, instead create a new, complete and valid bug report.
Found it in the weight brush tools panel. Screenshot for anyone else looking. I wish answers were more specific for noobs.
Where do I find the "Front Faces Only" and "2D Falloff" options in the UI???