The YouTube channel FlippedNormals just released a video tutorial on Blender 2.8 retopology. The video showed what they think is the most efficient way to do retopology right now without add-ons, where they discussed the pros and cons of the current tools that can be used for retopology. Since they are professionals and teachers of other 3D software like Maya and ZBrush, their input could be of some value in this discussion.

The most logical solution to me is to create a new mode altogether like was originally suggested. The ideal retopology workflow would need things like specific brushes like a relax and smooth brush to fix tight geometry, which would muddy the waters regarding the differences between Sculpt and Edit Mode if they were added to the latter. The workflow would also need to automate things like snapping to either selected objects or every visible object, creating a new mesh over the original, and more. There are way too many steps needed before you can even start doing retopology right now, and if you start pushing all those tools into Edit Mode, you really can't automate many of these steps since it would mess up the current workflow for Edit Mode.

@Sebastian Parborg (zeddb) , I checked the newest version, and it doesn't seem to crash anymore when using undo in sculpt mode back into edit mode, regardless of using hide selected/unselected or not. You can mark the issue as completely resolved. Thanks! :D

In T64647#699414, @Sebastian Parborg (zeddb) wrote:

I'm guessing this still happens for you with the latest blender beta?

In T60403#688145, @Brendon Murphy (meta-androcto) wrote:

hi, e66bf5191ff2 should fix this issue. I've checked that the addons keymaps are removed correctly. In the end I was able to reproduce your issue with load factory settings giving an error.

In T64647#684773, @Brecht Van Lommel (brecht) wrote:

I can't reproduce the issue.
Does it still happen in the latests builds?
If so, does it happen reliably, or only some of the time?

In T60557#601014, @William Reynish (billreynish) wrote:

Sounds good to me! It will make it a lot less likely to end in the bad state of having active object not be selected, or no active object at all.

In T54963#593809, @William Reynish (billreynish) wrote:

@Cezary Szadejko (cez): It's still alive but still waiting for issues to be solved with left click described here: T57918. Now that left click is enabled by default, it's paramount that we tackle these remaining issues anyway, and that will also pave the way for keymaps such as this one.

In T60403#599019, @Brendon Murphy (meta-androcto) wrote:

hi, Addons are specifically designed to interfere as little as possible with Blender default keymaps. They are also iirc, loaded at start up. You are using custom keymaps which can fall outside the scope of addons design and default key mappings at the moment. I feel that what you are requesting is outside of addons/keymap current design. To get around this you can edit the individual files that give you trouble with your custom keymap. I'm not sure this is a bug or a feature request or simply a limitation of the current design and the way things work.
A more knowledgeable blender developer may correct me if I'm wrong here.

In T60396#597608, @Philipp Oeser (lichtwerk) wrote:

Not sure if I understand correctly:
The Weld tool will move selected UVs to their average position, they will remain separate entities though.
If you weld two UVs that are slightly apart then these will hop into the same location [thats what you call "it works"], but you can still select one or the other, no?
So, unless I am misunderstanding something, two UVs can never be made into a single one.

In T60248#594984, @Benjamin Humpherys (brhumphe) wrote:

Could not replicate on 2edd32c168d3 on windows 10.