May 12, 2020, 01:39 (GMT) |
Update RNA Manual References |
March 12, 2020, 05:06 (GMT) |
Move 2.82a from beta to release |
March 10, 2020, 13:39 (GMT) |
March 10, 2020, 12:58 (GMT) |
Fix T74425: Cannot texture paint an images sequence anymore Caused by the introduction of UDIM (rBc30d6571bb47). We need to make sure the tiles ImageUser is set up correctly [especially the framenr], otherwise BKE_image_acquire_ibuf() and friends will fail to find the correct ImBuf. Also instead of initializing a minimal BKE_imageuser_default, now use an appropriate ImageUser if avaliable and pass this around (instead of just the tile_number). 2D painting can reuse the Image Editor ImageUser, for 3D painting we still rely on a default ImageUser in most places, but at least set the framenr correctly]. This also fixes crashes when doing image operations such as inverting or resizing on images in a sequence in the Image Editor. This also fixes color sampling (S) from the 3DView going wrong for image sequences (would fallback to OpenGL sampling because an ImBuf could not be found). Maniphest Tasks: T74425 Differential Revision: https://developer.blender.org/D7022 |
March 10, 2020, 12:58 (GMT) |
Fix T73369: corner pin & sun-beam nodes gizmos are too big Note that dragging isn't working well, however this was an issue in previous releases. |
March 10, 2020, 12:31 (GMT) |
Fix T74225: Image (from sequence) cannot be loaded If the current frame was not in range, the ImageTile's 'ok' was stuck at 0. Similar to the ImageUser being reset to 'ok' in BKE_image_user_frame_calc, we now do for ImageTiles as well. note: the crasher part of T74225 was fixed in rB5c490d437743. Maniphest Tasks: T74225 Differential Revision: https://developer.blender.org/D6939 |
March 10, 2020, 12:31 (GMT) |
Fix T63892: Tools cannot be registered into some contexts (e.g. PAINT_TEXTURE) This fails because some tool contexts define their tools with functions [see the following list for context that fail]: - PARTICLE (_defs_particle.generate_from_brushes) - SCULPT (_defs_sculpt.generate_from_brushes) - PAINT_TEXTURE (_defs_texture_paint.generate_from_brushes) - PAINT_VERTEX (_defs_vertex_paint.generate_from_brushes) - PAINT_WEIGHT (_defs_weight_paint.generate_from_brushes) - PAINT_GPENCIL (_defs_gpencil_paint.generate_from_brushes) - SCULPT_GPENCIL (_defs_gpencil_sculpt.generate_from_brushes) - WEIGHT_GPENCIL (_defs_gpencil_weight.generate_from_brushes) ToolSelectPanelHelper._tools_flatten() is usually called with cls.tools_from_context(context) [that already yields from the function]. But when registering a tool, _tools_flatten() will still give back this function, not a ToolDef - and we cannot get a bl_idname from that. Now check for this and yield None in that case. Also share logic across all tool_flatten functions: - _tools_flatten - _tools_flatten_with_tool_index - _tools_flatten_with_keymap Maniphest Tasks: T63892 Differential Revision: https://developer.blender.org/D6763 |
March 10, 2020, 12:31 (GMT) |
Fix bone envelopes displaying wrong when armature is scaled Object Scale was not taken into account. This lead to reports like T74247 where the user scaled the envelope distance and radii to the supposedly right values inthe viewport, but these were actually 'wrong' under the hood. Assigning weights from bone envelopes seemed like it would fail, but this code would actually take the armature scaling into account when checking envelope distance and weight. ref T74247 Maniphest Tasks: T74247 Differential Revision: https://developer.blender.org/D6964 |
March 10, 2020, 12:31 (GMT) |
Fix T72028: Crash switching to vertex paint This would happen when done from editmode, on a mesh with any modifier, after adding/removing geometry in editmode. Similar to rBba0870713b9b (which did this for weightpaint and sculpt already), ensure an evaluated depsgraph, otherwise 'runtime.mesh_deform_eval' would not be up to date causing problems later. Maniphest Tasks: T72028 Differential Revision: https://developer.blender.org/D7011 |
March 10, 2020, 12:31 (GMT) |
Fix Vertex weight gradient tool show wrong weight/strength values in the UI Main issue is that the UI doesn not respect the Unified Weight/Strength setting (but instead alwasy shows the brushes weight/strength) Was working before, but somewhat missed in rBfb74dcc5d69d. See discussion in T74025 on why the Gradient Tool in its current state is not very user friendly in general, what I think we should do though is at least have the values in the UI respect Unified Weight / Unified Strength since this is what the tool will use internally... ref T74025 Maniphest Tasks: T74025 Differential Revision: https://developer.blender.org/D6900 |
March 10, 2020, 12:31 (GMT) |
Keymap: Add front/back Alt-MMB absolute view axis switching Oversight in previous commit. |
March 10, 2020, 09:25 (GMT) |
Codesign: Make file watcher robust for network errors |
March 10, 2020, 09:25 (GMT) |
Codesign: Remove archive with files after they were copied |
March 10, 2020, 09:25 (GMT) |
Codesign: Harden check for archive being ready for sign Seems like sometimes files are being only partially ready, which makes it so there are unsigned files, failing to deliver fully signed bundle. Now expected archive file size is stored into stamp file and is checked against size of the archive file on another side. There are some bare prints used for debugging, would need to switch it to a proper logger (or to be removed). |
March 10, 2020, 09:25 (GMT) |
Codesign: Attempt to make macOS codesign more reliable Is still sometimes .ready file appears prior to an actual archive. |
March 10, 2020, 09:24 (GMT) |
Buildbot: Enable version character for development builds Allows to have 2.82a as a beta version on buildbot. |
March 9, 2020, 19:59 (GMT) |
Revert typo fix to ensure localisations don't break |
March 9, 2020, 19:55 (GMT) |
Update add-ons submodule with fixes for 2.82a |
March 9, 2020, 19:33 (GMT) |
March 9, 2020, 19:33 (GMT) |
Revert "Constraints: remove special meaning of Local Space for parentless Objects." This reverts commit 7728bfd4c45c634ba6b62e149176425ec5779945. Although this brings back an inconsistency in the behaviour of constraints on objects and bones, people were relying on the old behaviour, and the new behaviour broke their files. It is still desired to remove this inconsistency, but it will happen more gradually. |
|