This project is mirrored from https://projects.blender.org/blender/blender.
Pull mirroring updated .
- Jun 03, 2020
-
-
Nathan Letwory authored
-
Nathan Letwory authored
-
Nathan Letwory authored
-
Nathan Letwory authored
-
- Jun 02, 2020
-
-
Hans Goudey authored
This is a temporary solution for T77173 for the 2.83 release. D7203 provides a more long term solution for future releases. This adds theme colors for the three report backgrounds, setting them to the color used in 2.82. A separate commit in the addons repository will follow for changes to the bundled themes. Differential Revision: https://developer.blender.org/D7908
-
Brecht Van Lommel authored
This reverts commit 33ce0cb5. Fix T77273: crash enabling portal lights. The optimization for background updates can be added back later for 2.90 and 2.83.1.
-
Campbell Barton authored
This reverts commit f18ed7ad. Better leave the fix for 2.9 series.
-
Campbell Barton authored
-
Campbell Barton authored
Only use the active face when it's selected.
-
Bastien Montagne authored
-
Bastien Montagne authored
New depsgraph code handling drivers was not checking for possible NULL rna_path, as done everywhere else in code...
-
Campbell Barton authored
-
Campbell Barton authored
Comment on mode switching cases that are supported, including the issue from recent regression T77217 which is easy to miss since it's not used in the default key-map.
-
Brecht Van Lommel authored
Solution suggested by howetuft. Differential Revision: https://developer.blender.org/D7892
-
Garry R. Osgood authored
Differential Revision: https://developer.blender.org/D7890
-
- Jun 01, 2020
-
-
Bastien Montagne authored
-
Campbell Barton authored
Toggling object mode to the previous wasn't working, also resolves a case when toggling modes would cause an extra, unnecessary mode switch. Own regression in 5159b8e1.
-
Campbell Barton authored
Also allow NDOF with loop-cut.
-
Campbell Barton authored
-
Campbell Barton authored
-
- May 30, 2020
-
-
Antonio Vazquez authored
The Sculpt brushes were not properly initialized when use 2D template or other templates. Also, using the default template (not factory settings) could be situations where the brushes were not updated. This problem was introduced when some versioning code was removed in order to avoid duplicated brush creation.
-
- May 29, 2020
-
-
Clément Foucault authored
Differential Revision: https://developer.blender.org/D7876
-
Brecht Van Lommel authored
The file subversion is no longer used in the Python API or user interface, and is now internal to Blender. User interface, Python API and file I/O metadata now use more consistent formatting for version numbers. Official releases use "2.83.0", "2.83.1", and releases under development use "2.90.0 Alpha", "2.90.0 Beta". Some Python add-ons may need to lower the Blender version in bl_info to (2, 83, 0) or (2, 90, 0) if they used a subversion number higher than 0. https://wiki.blender.org/wiki/Reference/Release_Notes/2.83/Python_API#Compatibility This change is in preparation of LTS releases, and also brings us more in line with semantic versioning. Fixes T76058. Differential Revision: https://developer.blender.org/D7748
-
Clément Foucault authored
Create a new shader for the selection fix. Differential Revision: https://developer.blender.org/D7873
-
- May 28, 2020
-
-
Clément Foucault authored
-
- May 27, 2020
-
-
Brecht Van Lommel authored
-
Jacques Lucke authored
Reviewers: sergey Differential Revision: https://developer.blender.org/D7853
-
Patrick Mours authored
The input data to the OptiX denoiser was clamped to 0..10000 as required, but it could easily exceed that range with a high number of samples (since the data contains the overall sum). To fix that, divide by the number of samples first and multiply it back in after the denoiser ran.
-
Dalai Felinto authored
This was introduced on ecc395e4. Effectively this is reverting that commit for cases when scene->toolsettings->sculpt is NULL. But since the facesets are only working for sculpting this should be fine.
-
- May 26, 2020
-
-
Nathan Craddock authored
Add selection syncing for object add named (e.g. drag and drop from outliner to 3D view), outliner right click (a sync when the context menu is cancelled), and for object selection from Python.
-
Pablo Dobarro authored
The grab mode was not correctly implemented, so the way it was working was confusing for users. - Grab delta was calculated in increments from the last stroke position, so it did not match the behavior of a grab brush. I refactored the grab delta calculation to make this change more explicit. - Grab displacement was not calculated from the original coordinates - Grab was using an incorrect strength Grab is now setting the position of the affected vertices directly and the constraints solve the rest of the cloth. I also tried to implement an alternative version based on applying forces to move the vertices to the grab position, but I think this is more controllable and the grab falloff can be adjusted by tweaking the simulation falloff. Reviewed By: sergey Differential Revision: https://developer.blender.org/D7756
-
Pablo Dobarro authored
When the brush size is bigger than the entire mesh, fdata.tot_co can be 0, so the pose origin will default to (0,0,0), which does not make much sense. After this patch, the pose origin will be set to the farthest vertex from the pose origin, which at least should be in the surface of the mesh and in most cases in the direction the pose brush was already detecting the origin. Reviewed By: sergey Differential Revision: https://developer.blender.org/D7773
-
Pablo Dobarro authored
The only possible name for the iterator was ni, this should fix that. Reviewed By: sergey Differential Revision: https://developer.blender.org/D7774
-
Pablo Dobarro authored
The implementation of this function should match the one in SCULPT_vertex_co_get. This does not solve the issue when sculpting with modifiers active but I think this code is wrong Reviewed By: sergey, brecht Differential Revision: https://developer.blender.org/D7805
-
Sybren A. Stüvel authored
This was caused by a side-effect of our exporting code's memory management (Alembic considers data "written" and "final" when its C++ objects go out of scope) in combination with my change in rB65574463fa2d. I removed an "only export UVs on the first frame" clause because it was unclear why this restriction was there. As it turns out, it breaks the export of the 2nd and subsequent UV maps on an animated mesh. Effectively, on every frame the Alembic library thought we want to create a new UV map, instead of continuing to write a new frame of data to the existing one. This is resolved by keeping a reference to the C++ objects for the UV maps in memory while the exporter is running.
-
Philipp Oeser authored
Consider this a bandaid fix (similar to rBe2724abc22d5). Real issue seems to be that object is still in OB_MODE_PARTICLE_EDIT whereas it should be in OB_MODE_OBJECT after toggling 'Exclude From ViewLayer'. So while this patch prevents the crash, it leaves the object in a weird state (it cannot be selected for example), needs further investigation. Maniphest Tasks: T77074 Differential Revision: https://developer.blender.org/D7843
-
Julian Eisel authored
Didn't respect alignment rules for split layouts. Reported in T77075.
-
Philipp Oeser authored
Differential Revision: https://developer.blender.org/D7841
-
Philipp Oeser authored
unmuted in metastrip Maniphest Tasks: T77049 Differential Revision: https://developer.blender.org/D7834
-
Julian Eisel authored
-