Revision 064167f by Manuel Castilla August 23, 2021, 14:36 (GMT) |
Compositor: Full frame transform nodes Adds full frame implementation to "Rotate", "Transform" and "Stabilize2D" nodes. To avoid sampling twice when concatenating scale and rotate operations, a `TransformOperation` is implemented with all the functionality. The nodes have no functional changes. Part of T88150. Reviewed By: jbakker Differential Revision: https://developer.blender.org/D12165 |
Revision 8f4730e by Manuel Castilla August 23, 2021, 14:36 (GMT) |
Compositor: Full frame convert nodes Adds full frame implementation to all nodes in "Converter" sub-menu except "ID Mask" which is implemented separately. No functional changes. Part of T88150. Reviewed By: jbakker Differential Revision: https://developer.blender.org/D12095 |
August 23, 2021, 14:27 (GMT) |
Fix T88107: rename Convertor to Converter nodes to correct spelling Differential Revision: https://developer.blender.org/D11198 |
August 23, 2021, 13:47 (GMT) |
Fix T90423: black pixels after shadow terminator geometry offset Solves an error in the principled diffuse BSDF, where it was not correctly rejecting directions outside the hemisphere. Differential Revision: https://developer.blender.org/D12283 |
Revision 2f0e350 by Germano Cavalcante August 23, 2021, 12:49 (GMT) |
Fix T90872: Dopesheet messes up keyframe handles Y coordinate was not being constrained. Caused by {rBb0d9e6797fb866e7a58876c7977c98a190070310} |
Revision 27f138f by Germano Cavalcante August 23, 2021, 12:49 (GMT) |
Cleanup: rename parameter in transform utility `inv_unit_scale` is not descriptive. |
August 23, 2021, 12:46 (GMT) |
GPencil: Fix memory leak in split & trim functions Authored by Henrik Dick (weasel) Reviewed By YimingWu (NicksBest), Antonio Vazquez (antoniov) Differential Revision: https://developer.blender.org/D12284 |
Revision 5aa3167 by Philipp Oeser August 23, 2021, 11:54 (GMT) |
Fix T90772: Image Editor not sampling color from the the currently selected pass Caused by {rBebaa3fcedd23}. Seems this above commit assumed an ImageUser's multi_index is only used for Multiview/Stereo? This is not the case, multi_index also stores the index for layer/pass combination. If we call both BKE_image_multilayer_index and BKE_image_multiview_index (even though this is not appropriate/needed for multilayer images?), we might end up overwriting multi_index again. note: looking at this I was also wondering why we update the ImageUser in image-buffer-aquiring funnctions [and not from the UI, e.g. template_image_layers, but that is a whole different story I guess, see comment in T90772 as well] note2: this could also use a utility function (this is not the only place where this is done), this is fo a cleanup commit. Maniphest Tasks: T90772 Differential Revision: https://developer.blender.org/D12267 |
Revision 8165333 by Jeroen Bakker August 23, 2021, 11:47 (GMT) |
Pipeline: Use more explicit cuda versions. |
Revision 9564b6c by Philipp Oeser August 23, 2021, 10:52 (GMT) |
Fix T90651: camera reconstruction crash without scene camera This was working differently in 2.79, tried tracking this down and it seems this was wrong since the 2.8 beginning in {rB7907dfc40018}. This would not only crash without an active scene camera, but would also result in different tracks from different camera's constraints could not be selected. So select id depends on corresponding camera, remove the dependency on scene camera completely. Maniphest Tasks: T90651 Differential Revision: https://developer.blender.org/D12230 |
Revision 0682af0 by Campbell Barton August 23, 2021, 05:08 (GMT) |
RNA: add length augmented to RNA_string_get_alloc This was noted as a TODO as it wraps RNA_property_string_get_alloc which takes a length return argument. |
Revision 62f2204 by Campbell Barton August 23, 2021, 05:08 (GMT) |
Cleanup: rename len to str_len for BLF functions Make it obvious which variable this is the length of. |
Revision aa067be by Campbell Barton August 23, 2021, 05:02 (GMT) |
Cleanup: use BLI_str_utf8 prefix Rename: - BLI_str_utf8_invalid_byte (was BLI_utf8_invalid_byte) - BLI_str_utf8_invalid_strip (was BLI_utf8_invalid_strip) |
Revision 0de3d4e by Germano Cavalcante August 23, 2021, 02:48 (GMT) |
Fix T90847: snap to face of Add Primitive tool not working in edit mode BVHTree was being created but not balanced. Error introduced in {rBfcc844f8fbd0}. |
Revision b477333 by Ankit Meel August 22, 2021, 16:45 (GMT) |
Cleanup: fix comment about compiler support. Differential Revision: https://developer.blender.org/D12288 |
Revision a1e91fb by Harley Acheson August 22, 2021, 16:26 (GMT) |
BLF: Remove space_userpref.py font_kerning_style Remove `font_kerning_style` from `space_userpref.py` since this is no longer valid. See more details in D12276 Differential Revision: https://developer.blender.org/D12276 Reviewed by Campbell Barton |
Revision 721fad3 by Lukas Stockner August 21, 2021, 21:31 (GMT) |
Fix Windows builds after Zstandard commits |
Revision 2ea66af by Lukas Stockner August 21, 2021, 19:39 (GMT) |
Add support for Zstandard compression for .blend files Compressing blendfiles can help save a lot of disk space, but the slowdown while loading and saving is a major annoyance. Currently Blender uses Zlib (aka gzip aka Deflate) for compression, but there are now several more modern algorithms that outperform it in every way. In this patch, I decided for Zstandard aka Zstd for several reasons: - It is widely supported, both in other programs and libraries as well as in general-purpose compression utilities on Unix - It is extremely flexible - spanning several orders of magnitude of compression speeds depending on the level setting. - It is pretty much on the Pareto frontier for all of its configurations (meaning that no other algorithm is both faster and more efficient). One downside of course is that older versions of Blender will not be able to read these files, but one can always just re-save them without compression or decompress the file manually with an external tool. The implementation here saves additional metadata into the compressed file in order to allow for efficient seeking when loading. This is standard-compliant and will be ignored by other tools that support Zstd. If the metadata is not present (e.g. because you manually compressed a .blend file with another tool), Blender will fall back to sequential reading. Saving is multithreaded to improve performance. Loading is currently not multithreaded since it's not easy to predict the access patterns of the loading code when seeking is supported. In the future, we might want to look into making this more predictable or disabling seeking for the main .blend file, which would then allow for multiple background threads that decompress data ahead of time. The compression level was chosen to get sizes comparable to previous versions at much higher speeds. In the future, this could be exposed as an option. Reviewed By: campbellbarton, brecht, mont29 Differential Revision: https://developer.blender.org/D5799 |
Revision 67c29bc by Lukas Stockner August 21, 2021, 19:39 (GMT) |
Use Zstandard compression for the sequencer cache Reviewed By: campbellbarton, brecht, mont29 Differential Revision: https://developer.blender.org/D5799 |
Revision 2b170f1 by Lukas Stockner August 21, 2021, 19:38 (GMT) |
Refactor low-level blendfile reading into separate files Instead of handling mmap, compression etc. all directly in readfile.c, refactor the code to use a generic FileReader. This makes it easier to add new compression methods or similar, and allows to reuse the logic in other places (e.g. thumbnail reading). Reviewed By: campbellbarton, brecht, mont29 Differential Revision: https://developer.blender.org/D5799 |
|