Hmm, didnt actually check the code, but it possibly draws triangles in sculpt mode due to usage of MLoopTris instead of MFace, aka triangle only mesh representation vs tri and quad like before.
( I doubt sculpting supports ngons and polys directly, but i could be wrong here.) Could also be the drawing code does own triangulation there.

Tried the provided blend with 76650402f300 and a master version from september 13th.
Except maybe the extraneous green dot "far away" from the active vertex I also had no flicker or locking.
Windows 10 Pro 64-bit
Intel UHD 620 (laptop) (Lol, a miracle 2.8 seems to run flawlessly with this hardware :) )

improved sharpening mode : usable for csg objects and now threaded with tbb::parallel_for

sharpen features works with accumulate now + a few cleanups

some linux compile fixes

removed some now unnecessary old experimental, active code

Not necessary any more since particle meshing functionality is included as mode toggle inside D4960 (voxel remesher / metaball remesher)

• Improved the gaussian smoothing algorithm and using this instead of openvdbs standard gaussian
• added sharpen edges / corners feature for voxel remesher to try to preserve original features of the mesh
• included particle meshing mode into voxel remesher. It belongs there too, since it shares openvdb and volume csg logic. This would be duplicated otherwise. A new modifier also creates more noise as other modifier devs need to take care of new numbering, modifying a lot of more files etc. It is just more hassle to add a new modifier than to add a new mode to a thematically totally related modifier, aka remeshing. It is also easier for users to remember to look for one modifier and know that the functionality is grouped in there.

Ok, seems the desired effect of variable speed control can be already achieved by animating the override frame and / or the frame offset. Furthermore it would have introduced hassles with the previous frame state being potentially inconsistent. Closing.

• changed the RNA wording
• exposed a readonly timecode to the UI
• attempted to get rid of backward moving of objects when reducing the frame scale interactively or via keyframe, but objects seem to be temporarily stuck, any ideas for this ? Probably not properly solveable... hmm

Now showing both the source and the call locations of the operator for addon python operators and included python operators like uv smart project.
Also added a "Source" button to toggle back to the source if you changed to one of the call locations.
Furthermore now (mostly) pointing to the correct line of the call in the according draw function.

added context.area.tag_redraw() after executing the operator. This correctly now draws the populated box layout without need to hover over it.

Maybe just as another idea: what about volume-based boolean operations with OpenVDB ? But... the remesher can so far only make "soft" edges / beveled edges… it is (imho) very hard to nearly impossible to get sharp edges.
But you get different advantages like not needing to worry about self-intersections for example (although a volume of a flat object still is an issue, obviously).

since @Brecht Van Lommel (brecht) and me discussed the revival of the particlemesher in blender.chat, setting him as reviewer here.

Solved the particle issue by treating the particlemesher modifier like the dynamic paint and smoke modifiers regarding particle system copy and deletion.
Fixed some crash bugs regarding loading and saving as well as copying objects with this modifier too.
Need to deal properly with Ngons still for the mask object, like using looptris or something like that.
But i think a first pass of general review may already happen.

add an inline comment marking the area of the problem

Setting on "Planned Changes" since the particle issue is to be solved yet.

i solved that modifier puzzle now... turned out i had to update the customdata pointers in the mesh and set the modifier to Constructive and SupportsMapping.
Had to look in the draw code for it and found a reference to mesh->mloopcol, thats the customdata pointer for the MLOOPCOL layer.

got vertexcolor reprojection operational BUT... in order to see it on the active modifier, you need to add e.g. an array mod with count 1 after it... There is surely some hack somewhere in either the modifier system or in the vertex paint mode preventing the remesh modifier outputting the reprojection data, but it is there.

In rBe2f23d91b989e05ff743260d18c85a17f78439a9#225315, @Metin Seven (MetinSeven) wrote:

Hi Martin,
There's a (paid but very affordable) Blender OpenVDB add-on called OpenVDB Remesh that has an option to reproject the vertices in the latest update.
ZBrush also projects vertex color onto a mesh when using the Project All function. I assume it analyzes the vertex color data of the existing mesh and transfers it to the nearest vertices of the remeshed mesh. The more vertex detail in both the source and the destination mesh, the better vertex color details will be kept.
Thanks.

In rBe2f23d91b989e05ff743260d18c85a17f78439a9#225305, @Metin Seven (MetinSeven) wrote:

Sorry, I forgot a very important wish: reprojection of vertex colors, so vertex paint is preserved after OpenVDB remeshing.
Thanks again!

In D4530#104032, @Campbell Barton (campbellbarton) wrote:

Before getting into code review or looking into details I'd like to see example uses cases for this modifier.
Otherwise we could:

• Postpone until nodal modifiers are supported.
• Make this an optional post-process for the decimate modifier. -----

All BMesh operators _could_ be made into modifiers, however the modifier system isn't designed for constructive modelling (at least not with many fine grained operations).

Hi, another patch incoming :)

Hi, i have made a small patch in order to attach that new remesher option to the remesher modifier. Should apply to sculpt-mode-features branch from April 5th, 2019.