Revision 81a7f6c by Sebastian Parborg March 10, 2019, 11:06 (GMT) |
Fix T62125: snapping not working if invisible object is between you and the target If we were not in x-ray/wireframe mode, the snapping would treat all objects like they were in solid mode. This were not desirable if you had objects that were in wire or bounding box display mode. Now objects that are in bounding box mode is ignored (unless the object is in edit mode) and objects with wire display mode is treated as if they were in x-ray mode. Reviewed By: Brecht Differential Revision: https://developer.blender.org/D4493 |
Revision 81958a1 by Antonio Vazquez March 10, 2019, 10:18 (GMT) |
GPencil: Fix user count for autocreated materials The user count was 2 when the value must be 1. |
Revision b7bcc30 by Antonio Vazquez March 10, 2019, 07:55 (GMT) |
GPencil: Set brush material after copying a material This change updates the brush material in the topbar when a new material is created using copy button. Related to task T62384 Thanks to @matc for suggesting the fix. Still pending a problem whith user number. |
Revision 9ad1563 by Clément Foucault March 10, 2019, 02:57 (GMT) |
Fix T60171: Hair Particles Not Displaying in Viewport This patch fixes T60171 by adding a dummy read from the `dummy` vertex attribute to `hair_get_pos_tan_binor_time` in `common_hair_lib.glsl`. Confirmed to work on my machine (macOS 10.14.4 Beta, Radeon R?9 M295X). According to my experiments regarding this issue, the problem is triggered when all of the following conditions are met: (a) the shader has no vertex reads; (b) the index buffer is ? 256KiB. I can't really give an explanation of this misbehavior because of the video driver's closed-source nature. Reviewers: fclem Reviewed By: fclem Subscribers: zeddb Maniphest Tasks: T60171 Differential Revision: https://developer.blender.org/D4490 |
Revision d77b7b0 by Clément Foucault March 10, 2019, 02:35 (GMT) |
Fix T58890: Sculpt Mode not updating in LookDev or Rendered This fix is a hack and will slow down update performance. But at least, all shading features are supported. This is only in "normal" sculpt mode (no dyntopo, no multires). |
Revision 4041249 by Julian Eisel March 9, 2019, 16:19 (GMT) |
Merge branch 'blender2.7' Conflicts: intern/cycles/blender/addon/properties.py intern/cycles/device/opencl/opencl_split.cpp |
Revision 0a28bb1 by Julian Eisel March 9, 2019, 15:58 (GMT) |
Fix stashed full-screens returning to wrong layout Steps to reproduce were: * Maximize area (Shift+Spacebar in 2.7, Ctrl+Spacebar in 2.8) * Open temp file browser (Ctrl+O) * Cancel file browser (Esc) - should return to previous full-screen * Press "Return to Previous" button The previously maximized area would turn into a file-browser. Note that the issue will still happen when opening old files saved while in maximized area full-screen. |
Revision ba4d07c by Antonio Vazquez March 9, 2019, 15:50 (GMT) |
GPencil: Material panel is hidden after adding new material This bug was introduced by previous Pin fix commit. Maybe it's not the best solution, but this bug is critical and need a quick fix. This commit fix the problem, but not totally sure this is working fine with pin. @dfelinto Could you review and adapt if required. |
Revision 9c43520 by Clément Foucault March 9, 2019, 15:33 (GMT) |
GPU Extension: Add OS defines This makes possible to have os specific workaround inside the shaders. |
Revision 7e5d1a9 by Julian Eisel March 9, 2019, 12:11 (GMT) |
Fix T57655: Crash opening 2.79 file saved with maximized area During screen to workspace/workspace-layout conversion, the first layout of each workspace would be activated. For temporary full-screens, this used to be the full-screen layout (IIRC), apparently it's now the the layout to return to on "Back to Previous". So the 'previous' layout would be activated, not the full-screen one. When actually pressing "Back to Previous" now, the operator would first free the active layout (which it assumes to be the temp full-screen - wrongly in this case) and then try to activate the non-full-screen one, causing use-after-free. |
Revision 36cd310 by Sebastian Parborg March 9, 2019, 10:45 (GMT) |
Fix T62104: VertexGroup.add() doesn't push depsgraph update for the mesh. When adding and removing weights from the python api, no depsgraph updates were triggered. This would cause the mesh geometry to be out of sync in the viewport if there were any modifiers that used the vertex groups in question. Reviewed By: Brecht Differential Revision: https://developer.blender.org/D4439 |
Revision fede272 by Sebastian Parborg March 9, 2019, 10:41 (GMT) |
Fix T61737: Gizmo refresh issue When using a transform.select_orientation keyboard shortcut, the orientation change would not update the viewport. So if you had the move gizmo visible, it would not change transform orientation. Reviewed By: Brecht Differential Revision: https://developer.blender.org/D4386 |
Revision 9fdbffb by Sebastian Parborg March 9, 2019, 10:35 (GMT) |
Fix T62162: Bones set to unselectable can be fully selected through the viewport in edit mode. Bone selectability in edit mode now matches the behavior of pose mode (can no longer be selected). Reviewed By: Brecht Differential Revision: https://developer.blender.org/D4469 |
Revision a0f2923 by Dalai Felinto March 8, 2019, 21:52 (GMT) |
Fix active workspace changes when deleting workspace Tested for multi-window as well, which failed with the previous code even before we introduced ordered workspaces. |
Revision aa49444 by Dalai Felinto March 8, 2019, 21:52 (GMT) |
Fix crash when deleting workspaces too fast Delete workspaces via the menu was not refreshing the workspace tabs drawing. This way if you deleted the non-active workspace with the "e" shortcut from the workspace tab context menu and clicked on the workspace tabs again, it would crash. A few notes: * Deleting a non-active workspace is changing which workspace is then active, which is really strange. * Even when deleting the active workspace which workspace then becomes active seems random. * Using notifiers (ND_WORKSPACE_DELETE) to delete the workspace seems rather abusing notifiers in my humble opinion. This is not an important bugfix anyways, people probably would rarely run into this. I just ran into it while investigating another bug. |
Revision 2ada9c5 by Dalai Felinto March 8, 2019, 19:48 (GMT) |
Final fix for greasepencil materials assign/select/deselect in edit mode |
Revision 4ccaf56 by Dalai Felinto March 8, 2019, 18:36 (GMT) |
Fix T62349: Grease Pencil top material list not working This is a fixup for my own: 92d185faebe. I'm also fixing the poll of the EEVEE_MATERIAL_PT_context_material which would fail when we had no context.material available. |
Revision cee7c36 by Sergey Sharybin March 8, 2019, 17:13 (GMT) |
Revision 457ecc6 by Bastien Montagne March 8, 2019, 16:53 (GMT) |
Partially revert "Collection duplication from Outliner: add a 'duplicate hierarchy' operation." This partially reverts commit a77feabb51470b9cfb71be7f0ea7e774d6591799, removing the shallow 'duplicate hierarchy' option from outliner. Core changes from that commit in BKE_collections are kept. |
Revision 13978f7 by Bastien Montagne March 8, 2019, 16:53 (GMT) |
Followup to T62318: Fix on-the-fly that kind of .blend file cddata corruption. Remove cddata layers which are not supposed to be written in .blend file, when reading it. This is a cheap and simple check, which also gives us forward compatibility in case we decide some day to make a currently un-written layer type to be written in .blend files. |
|
|
|


Master Commits
MiikaH:n Sivut a.k.a. MiikaHweb | 2003-2021