July 26, 2021, 06:39 (GMT) |
Fix T89851: Geometry nodes: wrongly detected "Node group has unidentified nodes or sockets" error rBfe22635bf664 introduced a utility to check for this (but it was always returning true). This wasnt a problem in master (since it is unused there), but in the 2.93 branch, this utility is actually used and the error results in all geometry nodetrees to appear with the "Node group has unidentified nodes or sockets" message (and being unusable). Now return false in has_undefined_nodes_or_sockets if all nodes and sockets have been successfully checked. This commit then needs to end up in the 2.93 branch. Maniphest Tasks: T89851 Differential Revision: https://developer.blender.org/D11911 |
July 26, 2021, 06:36 (GMT) |
LineArt: Fix crash due to empty duplicollection. |
July 26, 2021, 06:35 (GMT) |
Fix T89455: Cycles crash when rendering a Mesh with autosmooth The crash was caused by a mistake in 5f9677fe0c533b008b815d7fee0b56509a414ab7 where the pointers to the custom data layers would be overwritten with the one for the first layer, as CustomData_duplicate_referenced_layer is only about the first layer. customData_duplicate_referenced_layer_index should be used instead to duplicate the right layer. |
July 26, 2021, 06:32 (GMT) |
Fix T88756: crash when baking with autosmooth When baking some data, we create a new Mesh with edits and modifiers applied. However, in some cases (e.g. when there is no modifier), the returned Mesh is actually referencing the original one and its data layers. When autosmooth is enabled we also split the Mesh. However, since the new Mesh is referencing the original one, although `BKE_mesh_split_faces` is creating new vertices and edges, the reallocation of the custom data layers is preempted because of the reference, so adding the new vertices and edges overwrites valid data To fix this we duplicate referenced layers before splitting the faces. Reviewed By: brecht Differential Revision: https://developer.blender.org/D11703 |
July 26, 2021, 06:31 (GMT) |
Fix T88015: Round end caps on Freestyle lines not shaped as documented This might be an artistic choice, but round end caps are supposed to be a "half circle centered at the end point of the line" as documented here: https://docs.blender.org/manual/en/dev/render/freestyle/ parameter_editor/line_style/strokes.html#caps They are a shashed half circle instead. This patch makes this pure half circles [and also fixes the case where thickness of beginning was used for both beginning and end of the stroke] Maniphest Tasks: T88015 Differential Revision: https://developer.blender.org/D11340 |
July 26, 2021, 06:30 (GMT) |
Fix T89765: boolean modifier collection refcount issue The 'collection' property is flagged PROP_ID_REFCOUNT, so the modifiers foreachIDLink functions should walk with IDWALK_CB_USER (instead of IDWALK_CB_NOP). Otherwise the modifier wont be included as a user for the collection (e.g. on file read); removing the collection from the modifier will decrement usercount though (which in worst case scenario makes the collection orphan and will result in data loss) Maniphest Tasks: T89765 Differential Revision: https://developer.blender.org/D11877 |
July 26, 2021, 06:27 (GMT) |
Fix channel packed images display in the Image/Node editor Channel packed images should not have their RGB affected by alpha. rendering in Cycles and Eevee was fine already, but displaying these was not right in the Image and Node editors. Not 100% sure what to do for the "Color and Alpha" mode, but I guess this should stay like it was before (applying the alpha). "Color", "R", "G", and "B" modes were changed to not have color be affected by alpha though. ref. T89034 Maniphest Tasks: T89034 Differential Revision: https://developer.blender.org/D11871 |
July 26, 2021, 06:25 (GMT) |
Alembic export: evaluation mode option This option will determine visibility on either render or the viewport visibility. Same for modifer settings. So it will either evaluate the depsgrah with DAG_EVAL_RENDER or DAG_EVAL_VIEWPORT. This not only makes it more flexible, it is also a lot clearer which visibility / modfier setting is taken into account (up until now, this was always considered to be DAG_EVAL_RENDER) This option was always present in the USD exporter, this just brings Alembic in line with that. ref. T89594 Maniphest Tasks: T89594 Differential Revision: https://developer.blender.org/D11820 |
July 26, 2021, 06:23 (GMT) |
Alembic: remove non-functional "Renderable Objects" only option When introduced in {rB61050f75b13e} this was actually working (meaning it checked the Outliner OB_RESTRICT_RENDER flag and skipped the object if desired). Behavior has since then been commented in rBae6e9401abb7 and apparently refactored out in rB2917df21adc8. If checked, it seemed to be working (objects marked non-renderable in the Outliner were pruned from the export), however unchecking that option did not include them in the export. Now it changed - for the worse if you like - in rBa95f86359673 which made it so if "Renderable Objects" only is checked, it will still export objects invisible in renders. So since we now have the non-functional option with a broken/misleading default, it is better to just remove it entirely. In fact it has been superseeded by the "Visible Objects" option (this does the same thing: depsgraph is evaluated in render mode) and as a second step (and to make this even clearer) a choice whether Render or Viewport evaluation is used can be added (just like the USD exporter has). When that choice is explicit, it's also clear which visibility actually matters. This is breaking API usage, should be in release notes. ref. T89594 Maniphest Tasks: T89594 Differential Revision: https://developer.blender.org/D11808 |
July 26, 2021, 05:59 (GMT) |
Fix object "Set Origin" operating on linked library data Regression in d25747ee751096de2e417a7da1316bf5bf81c25a |
July 26, 2021, 05:56 (GMT) |
July 26, 2021, 05:55 (GMT) |
Fix T89861: Checking face selection breaks UV stitch operator |
July 26, 2021, 05:54 (GMT) |
July 7, 2021, 05:52 (GMT) |
July 7, 2021, 05:47 (GMT) |
Fix T89153: Follow Path for empty works only in negative values The old code only clamped cyclic curves |
July 7, 2021, 05:41 (GMT) |
June 30, 2021, 07:45 (GMT) |
Cleanup: remove compilation warning in previous commit. |
June 30, 2021, 07:43 (GMT) |
UI: Hide collection tab when scene master collection is active CollectionLineart does not care about the configurations in master collection. Other options are not applicaple for master collection as well. Hence hiding it. Reviewed by Dalai Felinto (dfelinto) Differential Revision: https://developer.blender.org/D11702 |
June 30, 2021, 07:41 (GMT) |
Fix: VSE seeking with proxy strips would fail on certain frames If the last decoded frame had the same timestamp as the GOP current packet, then we would skip over this frame when fast forwarding and we would seek until the end of the file. This would could only be triggered reliably in single threaded mode. Reviewed By: Richard Antalik Differential Revision: https://developer.blender.org/D11601 |
June 30, 2021, 07:41 (GMT) |
Fix: VSE search in mpegts files would fail ffmpeg_generic_seek_workaround did work properly and our start pts calculation was wrong. Reviewed By: Richard Antalik Differential Revision: https://developer.blender.org/D11562 |
|