Currently you can Ctrl-click on the eye to solo.
Doesnāt work here. 
It must be on a Collection. I think it should be added to objects too, but for now it only works on Collections.
2 Likes
heat weighting: failed to find solution for one or more bones sounds like
āWell, your mesh is wrong in some way, ā¦ so fix it. Yeah, I mean one or more of your vertex is kinda strange. I wonāt tell you which but Good luck!ā
I hope it will be more informative, like moving to edit mode and select the wrong vertices.
When using pie menus (mode, render type) the numbering is not consistent. Is there a reason it canāt be 1ā¦ 2ā¦ 3ā¦ etc for all pie menus. For example Z/render-mode numbering is 2, 4, 6 (and not in radial order)
I understand the order might be not logical because some modes are much more used than others but the fact that numbers just get skipped is pretty confusing and annoying.
There is actually a logic behind this. The pie menu numbers are modelled after the numpad keys. So, 5 is the middle, 4 is left, 8 is up, 1 is down/left, and so on.
1 Like
OHHHHHHH they actually are. Okay that does make more sense.
My initial reaction was that āBut isnāt it pointless people will mostly use left hand and number lineā But I guess if you have detached numpad that can be switched to left side it could be nice.
Maybe it could be a general settings toggle for pie menus to be either numpad order or number line order?
Although I guess I can live with it knowing the logic behind it.
To be fair, I donāt even get why you would even ever use numbers with the pie menus. I mean, you can just hold a key (eg Z), flick your mouse in the direction and let go. Itās so fast and gestural, faster than having to type in a second character.
3 Likes
Why have the numbers at all, then?
Thatās not a real āSoloā since it just hides everything else. Solo should allow to revert to previous visibility state
1 Like
That would be possible with the āunlinkedā viewport visibility back. I think thatās still the plan to add this back before release.
i also noticed that alt+numbers are assigned to āhide collectionā they donāt do anything right nowā¦it was ported from 2.7x layers system, which worked as toggle per layer for second row? that could be used for something else.
however, an icon of a lock in place of the cursor might be more meaningful and consistent.
My reasoning: The cursor toggle effectively ālocksā the collection, preventing selection of any of itās elements. I believe some other panels use the lock icon already as well (Animation).
I think its placement is subjective though, because Iād prefer to the far right. 
1 Like
Agreedā¦
This error can be caused by alot more than just some double verticesā¦for example wrong scaling or to many loose parts in one object
This. Please. As an animator, Iām begging you.
2 Likes
Japanese translation is wrong. The correct Japanese translation of Translation is āēæ»čسā. It is not āē§»å(Movement)ā.
3 Likes
That is a strange translation indeed!
I think I can see how this occurred. Without any context, in a computer graphics application, ē§»å is a reasonable translation for āTranslationā. It has been used incorrectly.
My next concern about changing it is whether the msgid āTranslateā is being used elsewhere in the UI to represent movement. This should really be split into language:translate and motion:translate, but I donāt know the convention for namespacing in po files.
The source can be found in blender-git/blender/release/datafiles/locale/po/ja.po on line 36645
Look for msgctxt in gettext docs.
- Knife tool does not show vertex/edge highlight when doing first cut (after pressing e for a second cut it does)
- Transform value fields in the object > transform panel are cut on the right side where they meet the lock icons
- Values in fields are centered - I know this is by design but consider it a regression (cf https://developer.blender.org/rBSdde5e5ce2581ffd544b442c58d6eefbc1ff61772)
- Some checkboxes cannot be clicked on their label (all the toggles in the mesh options popover for instance) whereas most others are clickable either on the checkbox directly or on their label. Some of the un-clickable ones include āoverwriteā, āplaceholdersā, etc. in output panel of render properties, which were clickable up until 2.79.
- Since the timeline has been modeled after the dopesheet itās been able to display keyframes of all selected objects/bones just like the dopehseet, however it has a flaw when moving around in it (using mmb) : it allows moving vertically indefinitely even when there isnāt anything displayed, which can make you lose sight of the keyframes (they move out of view). My suggestion is either clamp view2d.scroller_activate so view doesnāt get scrolled too much, or just make the timeline simpler by removing sidebar and keyframe list (there is dopesheet for that after all).
2 Likes