Could it be possible to use the normal of a lower subdivision when using multires mesh modifier as a workaround for that zbrush-style behavior? Basically, when given the option, you use the resolution of the preview to guide a smoothing algorithm so that the brush preview is more performant on high res models? I don't know what could be done about using dynotopo, but for cases like the above, I would imagine the really high resolution details would be utilizing the multires modifier anyway.

@Bastien Montagne (mont29) I believe this should be reopened as blender continues to crash when dynotopo is on w/ tiling enabled. I just tested this on b201196c2e5 and it continues to crash.

I really like this change. It should dramatically improve the sculpting experience in Blender!

@Dalai Felinto (dfelinto) No worries, and sorry I didn't respond right away. Yeah that's OK with me, I'm just glad to have helped contribute a bit to blender. :) I'll be back to supply whatever I can, so no worries.

Any updates on my pending updated diff @ D3338 for MESH_OT_bridge_edge_loops?

So I've isolated the body of the for loop into its own function (taking in an edit mesh and a wmOperator for any additional information). I decided to pass in the user-configurable values as arguments since those shouldn't change during the process of iterating through all the mesh assets. It may be ideal to break those options into a struct in order to make the function call more clean in the future (in case more arguments will need to be passed further down the line.)

Yes, I'll try that when I get back today. Sorry for the delayed response!

MESH_OT_quads_convert_to_tris and MESH_OT_tris_convert_to_quads appear to be already implemented in the blender2.8 branch. Someone should cross them out.

I've submitted a patch for MESH_OT_bridge_edge_loops. D3338

Hi Everyone! I've put a MESH_OT_fill patch in for code review. D3332