Revision a1747b0 by Sergey Sharybin November 5, 2019, 13:48 (GMT) |
Fix T71259: Array Modifier Performance is slow Was happening when object transform is animated. Caused by overly aggressive dependency construction introduced a while back in 9d4129eee649: we shouldn't add dependencies unless we really need them. This change removes unneeded transform dependency for cap objects (since only their geometry is used), and also removes own transform dependency if there is no offset object (which is the only case when own transform is needed). Differential Revision: https://developer.blender.org/D6184 |
Revision 16767c4 by Sergey Sharybin November 5, 2019, 13:34 (GMT) |
Merge branch 'blender-v2.81-release' |
Revision 8dfe280 by Sergey Sharybin November 5, 2019, 13:31 (GMT) |
Fix T71356: Motion Paths no longer update |
Revision 63b9f83 by Sergey Sharybin November 5, 2019, 13:23 (GMT) |
Revision 3d5d7cf by Patrick Mours November 5, 2019, 13:20 (GMT) |
Merge branch 'blender-v2.81-release' |
Revision 7a93abb by Patrick Mours November 5, 2019, 13:19 (GMT) |
Fix Cycles failing to compile when "WITH_CYCLES_LOGGING" is off |
Revision ea7e161 by Philipp Oeser November 5, 2019, 09:05 (GMT) |
Merge branch 'blender-v2.81-release' |
Revision bb69e62 by Philipp Oeser November 5, 2019, 08:57 (GMT) |
Fix T68396: Unable to change any Collision input value after it has been keyframed 'rna_CollisionSettings_update' has a history of tagging ob for update: rB79312c1912b4 ID_RECALC_TRANSFORM |ID_RECALC_GEOMETRY | ID_RECALC_ANIMATION rBf90a2123eedc OB_RECALC_OB | OB_RECALC_DATA | OB_RECALC_TIME rBfaf1c9a4bb27 OB_RECALC_ALL rB7df35db1b136 OB_RECALC Since the meaning of OB_RECALC_TIME/ID_RECALC_ANIMATION changed a bit historically (from "please update my animation if the animation datablock is tagged for update" to "update animation of this datablock") this was now always overwriting user edit with animated values, making it impossible to change those values once animated. Thx @sergey for guidance! Maniphest Tasks: T68396 Differential Revision: https://developer.blender.org/D6113 |
Revision cc601e0 by Campbell Barton November 5, 2019, 06:50 (GMT) |
Merge branch 'blender-v2.81-release' |
Revision bfa761d by Campbell Barton November 5, 2019, 06:47 (GMT) |
Cleanup: remove redundant pivot popover |
Revision 1ef2cbb by Campbell Barton November 5, 2019, 03:12 (GMT) |
Merge branch 'blender-v2.81-release' |
Revision 490d5bb by Campbell Barton November 5, 2019, 03:10 (GMT) |
Fix T68130: Over sensitive number button dragging When continuous grab, cursor motion was mapped to the min/max. This caused problems when int/float max values were used. Now the range is clamped by a value derived from the click-step so dragging numbers never increases it to an impractically large value. |
Revision f4e081e by Campbell Barton November 4, 2019, 22:17 (GMT) |
Merge branch 'blender-v2.81-release' |
Revision 95a60fe by Campbell Barton November 4, 2019, 22:14 (GMT) |
Fix errors in fix for T68018 |
Revision ef7fd50 by Julian Eisel November 4, 2019, 20:01 (GMT) |
UI: Rewrite stacked full-screen logic, fixing issues To recreate the main issue: * Set render and file browser to show in full-screen in the preferences * Default scene, press F12 in 3D View * Press Alt+S to save the image * Escape the file browser * Escape the image editor The former 3D View would now show the image editor. This is a common use-case that should work. Full-screen code is a hassle to get to work as expected. There are reports from 2.5, I did lots of work years ago to get these kind of use-cases to work fine. But apparently I broke this one with a fix for another common use-case in March (0a28bb14222c). This now stores hints in the space, rather than the area, which should make things much more controlable and hopefully help us fix issues like this. Here are a few references describing further common issues (all should work fine now): 0a28bb14222c, e61588c5a544, T19296 Checked over this with Bastien, we agreed that at some point we should do a big rewrite of all of this, for now this is acceptable. |
Revision 4b337a8 by Patrick Mours November 4, 2019, 17:10 (GMT) |
Merge branch 'blender-v2.81-release' |
Revision b45828e by Patrick Mours November 4, 2019, 17:09 (GMT) |
Fix T71123: OptiX error in Cycles viewport when adding HDRI Cycles did not update the "is_enabled" flag on lights when they were synchronized again, which caused all lights disabled by "LightManager::disable_ineffective_light" to be disabled indefinitely. As a result the OptiX kernels were not reloaded with correct features when a change to a light was made. This fixes that by updating the "is_enabled" flag during synchronization. Differential Revision: https://developer.blender.org/D6141 |
Revision ece4515 by Lukas Stockner November 4, 2019, 14:02 (GMT) |
Fix T71250: ID user decrement error with ID properties in ViewLayer Credit for the original patch goes to @scorpion81. |
November 4, 2019, 13:53 (GMT) |
Correct naming of cryptomatte output sockets on the render layers node The cryptomatte sockets were incorrectly numbered using a step size of two. While the increment by two is necessary to get the correct number of render passes, they should be numbered consecutively matching the socket names of the cryptomatte node. Reviewed By: lukasstockner97 Differential Revision: https://developer.blender.org/D6185 |
Revision 9fac676 by Sergey Sharybin November 4, 2019, 09:54 (GMT) |
Nasking: Toggle cyclic on Ctrl-Click on initial vertex This change replaces old behavior when spline was toggled as cyclic on double-click. Doing so was tricky on a tablet and is rather non-intuitive in general. Differential Revision: https://developer.blender.org/D6162 |
|