After talking with Campbell, have decided to close this one for now. If we can reproduce that second issue in 2.8, then can reopen with a repeatable test case (using script or knife project).

There are two things going on here and I am not sure which you are trying to report.

this is a bug if you cut out a line using knife lines appear all over the mesh.

@Howard Trickey (howardt), @Campbell Barton (campbellbarton) not sure whether this is bug or expected limitation?

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Hi, Has there been any progress on this bug?

More than a week without reply or activity. Due to the policy of the tracker archiving for until required info/data are provided.

Confirmed. @Campbell Barton (campbellbarton) maybe you want to check on that one? Thanks.

Also effects other tools such as sheer (cant select x or y axis)

More than a week passed without a reply.

From what I could see, due to the COW, there are two BMEditMesh. One for the Mesh of the original object and other for the one of the evaluated object.

@Germano Cavalcante (mano-wii) looks like crash happens in raycasting code, maybe you are interested in investigating that one? Especially since it seems to only be reproducible on windows. :/

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

yep, weird ugly things are happening here… probably due to mixing undos. @Campbell Barton (campbellbarton) think that one is for you?

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

I think the new tool system does not handle that preference? @Campbell Barton (campbellbarton) think that one is for you. :)

Definitively not a bug, user forums like blenderartists.org or blender.stackexchange.com should be used for that matter.

Hi @mathieu menuet (bliblubli) I've attempted to resolve this discontinuity in my branch with all possible limit methods. Hope you can test it out.

Weights do not work when I combine just armatures. (Vertex groups)

Afaics, you are parenting the blade to the existing "Armature" (which doesnt have the corresponding bones for the blade anymore -- you deleted them in 0:15 of the video)
You could actually join the imported "Armature.001" object (that came with the FBX import -- and that was working nicely) to the existing "Armature" object. Just select both Armatures and Ctrl+J

In T54643#503068, @codemanx wrote:

Submitted a patch for MESH_OT_sort_elements: https://developer.blender.org/D3379

Open question: Can the selected BMEditMeshes have different selectmodes? The current assumption is, that the selectmode is the same for all selected meshes in editmode.
If they can in fact be different, why? Isn't the mode something global in 2.8?

Hi @codemanx : Still a little bit early for 2.8 bugs due to following policy:

sorry for the duplicate and thanks for the answer :)

Unfortunately operations that alter topology are not supporting Custom Split Normals:

Closing revision: issues with performance of selection history can be addressed separately from this patch.

Fixed bad indexing of select_history in modified select_prev, updated benchmark results with code changes

Am not too keen on this, mainly because the selection history is typically not a very large list.

Commit with minor changes: 5a431be629940e0ecffba047e80e0946a01f3aa4
Thanks for your contribution.

Alpha sorting was a long-standing 'problem' but it will be fixed in 2.8.
This has been reported a couple of times, see T43093, T51964, T46349, T49376, T44826, T41731