January 13, 2021, 13:56 (GMT) |
Fix T83050: Crash dragging shared collection to master collection The flag syncing code expects to find collection flags in same view layer before and after the move, it even has an assert for it. However, there is one case where this doesn't happen, when dragging a collection that exists in two scenes to the master collection. This commit removes this assert, frees the temporary flag structs separately, and updates some comments with this information. There is more detail in the adjusted comment. Differential Revision: https://developer.blender.org/D9785 |
January 13, 2021, 13:56 (GMT) |
Fix T83280: Crash when deleting hair collision collection. Root of the issue was missing management of ID pointers in the cloth modifier data stored in ParticleSystem for hair physics, in the 'foreach_id' particle system code. Using modifier's 'foreach_id' code in psys one unfortunately requires some ugly conversion gymnastics, but this is still better than having dedicated code for that case. Note that this is actually a fairly critical issue, fix should be backported to 2.91.1 should we do it, and to 2.83 LTS as well I think. |
January 13, 2021, 13:55 (GMT) |
Fix T83460: Regression in snap for measure tool Now the gizmo is drawn only when the eventstate located in `wm->winactive->eventstate` has not changed. So it doesn't matter if it's "selected" or not. This commit also removes the use of the private header "wm.h" Reviewed By: campbellbarton Differential Revision: https://developer.blender.org/D9539 |
January 13, 2021, 13:52 (GMT) |
Fix T83352: Move with constraint showing an incorrect value in the header The displayed value was always that of the x axis. |
January 13, 2021, 13:52 (GMT) |
Fix T83161: Crash when moving ruler endpoints and opening or closing the toolshelf `invert_snap` could be called before `snap_gizmo->keymap` was found. Use the lazy initialization in `invert_snap` then. |
January 13, 2021, 13:52 (GMT) |
Fix transform snap mixed with incremental The incremental was taking priority but the other elements are mandatory. |
January 13, 2021, 13:51 (GMT) |
Fix T83092: Direction of rotation with View orientation changed in 2.91 The change was intentional so that the orientation matrices match (`rv3d->viewinv` becomes equal to the orientation matrix). But, although in a projection matrix the Z axis is negative, this should not be so from the user's point of view. So the solution here is to negate the Z axis when the View orientation is chosen. This affects all modes, but is only evident for rotation. --- Another change here is to use the final rotation value (`values_final`) for the gizmo drawing since this value can be changed by the mode. |
January 13, 2021, 13:51 (GMT) |
Fix T83020: Transform: AutoConstraint being confirmed without releasing the MMB The transform modifiers are confirmed by releasing any button. Thus, the operation can be falsely confirmed if the button that launched the operation is released after the modifier has been activated. Previously the events that confirmed the modifiers were hardcoded. An option to fix this would be to add custom confirmation keyitens for specific modifiers. But this can be a bit confusing and would make the modal keymap even bigger. So the solution here is to skip the button that launched the operation when confirming the modifier. |
January 13, 2021, 13:50 (GMT) |
Fix transform redo panel showing only the first custom orientation The error was introduced in rBf470a02afaea, but the problem is in `ED_transform_calc_orientation_from_type_ex` |
January 13, 2021, 13:50 (GMT) |
Fix T82777: Some transform modes using incorrect default orientation Some modes were always using `"Global"` orientation as the default. |
January 13, 2021, 13:49 (GMT) |
Fix T79356: Improved icons for MSIX builds Fixed an issue that was causing the app icon to render with a 'plated' background color in the taskbar and other areas of Windows. Updated all app icons in Microsoft Store package to match Microsoft's design recommendations. Added multiple scales for app icons for high resolution displays. Added high contrast app icons. Reviewed By: pablovazquez, jmonteath Maniphest Tasks: T79356 Differential Revision: https://developer.blender.org/D9681 |
January 13, 2021, 13:29 (GMT) |
Fix T83625: Shading attribute names cause compilation error. Some GPU platforms don't support having more than one underscore in sequence in an attribute name. This change will remove the underscore as a possible character when encoding to save names. |
January 13, 2021, 13:29 (GMT) |
Fix T84397: Creating and removing many objects very quickly causes a crash The root of the issue was caused by the dependency graph using ID pointer to map evaluated state from old depsgraph to new one upon relations update. This was failing when IDs were re-allocated rapidly: was possible that Object ID's evaluated state assigned to Mesh and vice versa. Now depsgraph uses Session UUID to identify which IDs to restore evaluated state to. The session UUID is stored in the IDNode, so that id_orig is not dereferenced on depsgraph update since the ID might be freed. The root of the issue is identified by Campbell, original patch was done by Bastien, thanks! Also thanks to Oliver and Ray and everyone else for testing! |
January 13, 2021, 13:29 (GMT) |
Fix T83084: Smart UV Project inverts the resulting UVs Caused by 850234c1b10a828678f1b91001f2731db807f7e2, Flip the normal to avoid flipped projection. |
January 13, 2021, 13:27 (GMT) |
Fix: Update normals when switching scene quality Recent commits also updated normals for metaballs, curves and volumetric objects. This change tags will tag to generate geometry for these new types. |
January 13, 2021, 13:27 (GMT) |
Fix T84459: Face normals not displaying (AMD GPU) This is part two of the fix for T84459. Issue appears to be caused by AMD graphics driver later than 20.11.1 and affects older GPUs (Polaris/FIJI cards). Drawing normals in edit mode uses the same OpenGL data type for storing normals that is known to be faulty. This change fixes the face dot normals by using GPU_COMP_I16. |
January 13, 2021, 13:25 (GMT) |
Fix T84459: Wireframe not displaying with AMD GPU Issue appears to be caused by AMD graphics driver later than 20.11.1 and affects older GPUs (Polaris/FIJI cards). Wireframe drawing uses the same OpenGL data type for storing normals what is known to be faulty. This patch enabled storing the normals using GPU_COMP_I16. It also solves the normals drawing in edit mode for vertex and loop normals. |
January 13, 2021, 13:24 (GMT) |
GPU: Enable HQ normal work around for AMD Polaris THe high quality normals work around is enabled for Polaris cards using the official drivers. Since driver version 2.11.2 they fail to render using low quality normals. The detection of polaris cards is done by matching the opengl renderer. The renderer strings have been extracted from various reports linked to {T82856} but isn't complete as some reports are missing the exact renderer as users don't always report via the help menu. |
January 13, 2021, 13:21 (GMT) |
GPU: Add HQ normals workaround. This change makes it possible for platforms to only support high quality normal rendering. This is part of {T82856} where current AMD drivers running on the polaris architecture does not support the low quality setting due to a driver bug. In a next commit the work around will be enabled. |
January 13, 2021, 13:20 (GMT) |
DrawManager: High quality normals for non meshes This adds high quality normals for non meshes. These include * Volumetric Object Wireframe * Metaballs * Extracted Curves * Curves in edit mode This is in preparation to fix a regression in recent AMD drivers where the `GL_INT_2_10_10_10_REV` data type isn't working in Polaris cards. |
|