I didn't understand your explanation, but if it's solved, then it's solved :P.

Doubt this bug will affect anyone beside me, ever, so lowering its prio :)

This sounds like it's working as intended, and when you say it worked in some June build, it was either broken then, or you weren't doing the same thing. If you have a child and parent bone that are already parented to each other via regular parenting, and then put a Child Of constraint on top to do the same thing, moving the parent will result in twice the amount of movement in the child. This is how the Child Of constraint is expected to work, afaik. That said, you'd probably never want to use it in this way.

You didn't fill out the description of the error and reproduction steps. The devs can't do anything with this amount of info.

Putting here what I put in chat and tagging @Brecht Van Lommel (brecht) for opinion: How about forcing Weight Paint mode into Flat->Single Color->White shading? It makes no sense to mix color information with the non-color information that is weights, and it's frustrating to switch into and out of weight paint mode right now, see: https://developer.blender.org/T61486#702654

Sounds like the first issue is the Auto-Normalize feature, and the second is intended behavior.

I'm glad that's the easier solution, since that would make sense to me. What other operator works on objects that are not even selected? Since remember, the other weight paint mode objects in the scenario are not even selected at all.

I agree, I can still reproduce this in today's build.

Oh well. Maybe you were running out of memory!

Maybe you could reduce the project to just a single object/material that still produces the bug, but doesn't contain any assets you're not allowed to share? Sorry if it's a bit of a hassle, but without a way to reproduce on the dev's side, there's not much they can do to look into it.

Would you be able to attach a zip with the blend file and textures from the beginning of the problem, so we can follow your steps and see if we can reproduce it?

Try the following, if you haven't already:

Although I don't think there's any "rules" against NSFW content around here, but it sounds like the problem is contained within the armature object, so I advise you to make a minimal blend file which is recommended anyways, by just deleting everything except the armature, and upload the file that way.

You could try cleaning your userprefs(make a backup) under C:/Users/username/appdata/Roaming/Blender Foundation/2.80/. Just rename the 2.80 folder to 2.80_bkp.

Thanks for the report, but this could not be more vague if you tried. Please make a new report where you:

Ask the author of the rig. Probably not a Blender bug.

+1. Here's me trying to go from studio lighting textured viewport into weight painting on a face.

I want to recommend this bug to be considered High prio, since I think it will confuse or even turn off a lot of people from 2.80, if god forbid it stays in for the final release. Just a thought tho.

I gave it a shot real quick, what I came up with was to derive the "raised-ness" of the arm using a helper bone at the original location of the shoulder, and point it toward the hand, then look at its rotation. Then just use that value to control the clavicle. The helper bone is parented to the spine, so no dependency cycles here.

A child should never affect its parent, since a parent always affects its child, if a child in turn affected its parent, it would always be an infinite loop of maths.

@Sebastian Parborg (zeddb) suggested to re-open and edit the report with strike-throughs, so I'm doing that.

Thanks for the patch!

I am retarded. The scaling thing was because of a constraint. The rest still apply but T65671 covers it.

Putting this in a comment because it's more of a feature request:

You can try wiping your user prefs by simply re amimg the 2.79 folder to something else, located in C:\Users\username\AppData\Roaming\Blender Foundation\Blender.

Aren't there inner faces at the mirror axes in one of the meshes, while they are not there on the other? Can you provide your blend file?

Can reproduce. First time it throws this error in the console:
TypeError: bpy_struct: item.attr = val: enum "MATERIAL" not found in ()
Second time onwards it works, until you reload the file or run the script from a different screen area.

Looks like you found the viewport clipping feature. Press Alt+B! :)

When you say it was probably some addon causing it, do you think it was one of the built-in addons? Since that would still be an issue worth looking into. If you think it was most likely some random addon you downloaded then I guess this can be closed.

Closing because no info in over a week. Feel free to reopen.

Closing because no info in over a week. Feel free to reopen.

I feel like it'd make sense to temporarily close this so it doesn't attract triager eyeballs. When your project deadline has arrived and you're able to provide the .blend file, you should feel free to reopen this task. (Add Action->Change Status->Open).

Considering 2.7 bugs are no longer being fixed, should this be closed? Or can you check if your original issue happens in 2.8? If yes, please attach a minimal blend file(delete everything that isn't relevant to the bug). Note that you can pack textures into the blend file using File-> External Data-> Pack All Into .blend (then save the file).

Note that you're using confusing terminology here, because "Smooth Weights" is the name of an operator. It's a good thing you made a video, so I can see you're actually talking about the Blur brush. I checked in 2.8 and I can't reproduce the issue, although by default, the "Front Faces Only" option is enabled, so I can get the behavior you're looking for by disabling that option.

I'm assuming it crashed during Eevee shader compilation(but then again, you didn't even specify what render engine you were using), and I think a lot of those crashes were fixed somewhat recently. I'm closing this for now, please try on the latest 2.80 and if it still happens you can feel free to re-open this. And if you do, you should also attach a blend file to help reproduce it and/or make a video of the crash.

I can't reproduce either and it's been a while since any new info, so closing. If anyone can reproduce it, feel free to reopen.

Closing because by the sound of things this is not a bug, just another victim of the crappy undo history in 2.7. Thankfully it's fixed in 2.8, rejoice!

Closing because no info in over a week. Reopen if you like.

Closing because no info in over a week. Reopen if you like.

Closing because no info in over a week. Reopen if you like.

Closing because no info in over a week. Reopen if you like.

Closing because no info in over a week. Reopen if you like.

Closing because no info in over a week. Reopen if you like.

Closing because no info in over a week. Reopen if you like.

I also can't reproduce this.
Could you check if it's still happening for you on the latest version? And does it happen on a newly created file?

Closing because no info in over a week. Reopen if you like.

Constraints also get lost in the same way. This is more important than the original report, but I feel like I shouldn't edit it now that it's been confirmed.

You can attach a .blend file by drag and dropping it into the text editor here. Surely you don't expect a developer to type out the script from the screenshot, and on top of that reconstruct your scene based on the script. :P

I think there is something here that to me looks very close to what might be considered a bug:

It makes some sense to average weights with Remove Doubles, but Merge is probably a different story, and definitely feature request territory. It's unclear to me if we're talking about both of them or just Remove Doubles.

You can attach blend files directly to here by drag and dropping (or using the upload file button that looks like a cloud with an uparrow inside it). I don't know what the devs' policy is on downloading off-site files, but I recommend attaching it.

Works the same way as it did in 2.79. You need to have more than one edge selected, otherwise what you need is the "Rip" operator(default hotkey V).

Just wanted to point out that the mesh also updates when sculpting a shape key in lookdev mode.

I hope it's okay if I close this, I'm pretty sure there won't be a bug here.

Everything in the screenshot looks normal. Can you describe what you think the issue is? If it's the small text in the properties panel, you can change zoom with Ctrl+Middle Mouse drag.

There's a setting in the operator called Strip Numbers which should do this! You can find the operator settings in the bottom left corner of the viewport, after you use an operator.

Works fine for me, man.

Happening on my end too, 2.80, d7d180bd3d8d, Win10.

and found out that I needed to place in a opengl32.dll into the Program file for Blender itself to start working.

Does other software have transform operators in the UI? After all, we have gizmos, so this seems somewhat redundant, and would clutter the UI imo.

I know I'm not a dev but I hope you'll excuse me if I invalid this? :P Save someone a couple of clicks?

Good points from everyone, I didn't mean to derail the topic to removing buttons, afterall that's a completely different thing from changing defaults, which is the topic at hand. Either way I'm not too bothered by the random seed button's existence or its current default, just wanted to throw it out there for consideration! :P