July 30, 2019, 20:55 (GMT) |
Cleanup: Rearrange Select Engine into multiple files |
July 30, 2019, 20:50 (GMT) |
cleanup: Fix typo in last commit Accidentally took the C flags as a base. |
July 30, 2019, 20:40 (GMT) |
CMake/Windows: Enable JMC on compilers that support it. JMC [1] enables more productive debugging of C++ code in visual studio this change enables it on debug builds for builds with visual studio 15.8 or higher. [1] https://devblogs.microsoft.com/cppblog/announcing-jmc-stepping-in-visual-studio/ |
July 30, 2019, 20:26 (GMT) |
Merge branch 'soc-2019-openxr' into temp-vr-draw-thread |
Revision 9ac33e5 by Julian Eisel (soc-2019-openxr, temp-vr-draw-thread, vamr-openxr-module, vr_scene_inspection) July 30, 2019, 20:19 (GMT) |
Merge branch 'master' into soc-2019-openxr |
July 30, 2019, 19:48 (GMT) |
Cloth: fix bug in invert_m2_m2() |
July 30, 2019, 19:38 (GMT) |
Keymap: Support F2 for rename in the outliner Rather than use the F2 rename active object popup when in the outliner, rename the active element. This allows renaming object data, collection, and other non-object elements within the outiner. |
July 30, 2019, 19:32 (GMT) |
DRW manager: select engine: remove redundant calls |
July 30, 2019, 18:48 (GMT) |
Bevel Custom Profile: 4-way pipe case vertex mesh working. |
July 30, 2019, 18:29 (GMT) |
Cloth: more face sizing debugging statements |
July 30, 2019, 17:46 (GMT) |
Cmake/windows: Fix vcpkg bypassing our libs folder. Occasionally we get reports of people that build blender and end up with either build errors or end up with builds that do not run on other systems. The root cause is when you install vpckg and integrate it into the build system it puts the search path for its includes and libraries before anything else. previously we told people to either uninstall vcpkg or remove the conflicting packages, which was not great. this change opts out of the use of vcpkg for blender only, so people can keep using it for other work without issues. |
July 30, 2019, 17:43 (GMT) |
Fix T67939: GPencil Noise modifier step is ignored in render The value of the step was calculated using a variable that was removed when the render frame change. Now, the step is calculated using the modulus of the current frame and recalculate noise only if the remainder that results from performing integer division is equal to 0. To calculate current frame, the first used frame is calculated to adjust real frame range. This approach is more stable in viewport and render. |
July 30, 2019, 17:37 (GMT) |
Merge branch 'master' into soc-2019-outliner |
July 30, 2019, 17:33 (GMT) |
Initial Commit: Use GPU to test the visibility of vertices. |
July 30, 2019, 16:16 (GMT) |
Change neighbour array default size |
July 30, 2019, 16:12 (GMT) |
Sculpt mesh API: replace gsets with static arrays |
July 30, 2019, 16:11 (GMT) |
Fix snap package to work with 2.80 version number Without this it rounds to 2.8. |
July 30, 2019, 15:11 (GMT) |
Fix T65691: GPencil Drawing long strokes turn invisible There was a fixed limit to the number of points available in a buffer stroke. Now, the array is expanded as needed using a predefined number of points for each expansion, instead to add one by one. This is done to reduce the number of times the memory allocation is required. As part of the fix, some variables have been renamed to reflect better their use. |
July 30, 2019, 15:06 (GMT) |
Alembic export: fix exporting of loop normals When the mesh is using custom normals, those should always be exported, regardless of the `ME_SMOOTH` flag on the invidivual polys. Also replaced the loop normal writing with the same logic as we use for reading (less pointer arithmetic, more normal counting). |
July 30, 2019, 15:06 (GMT) |
Alembic import: load face-varying normals Loop normals are called 'Face-varying normals' in Alembic. Before this commit, the existence of such normals was used to enable smooth shading. This is incorrect, as the normals could encode flat faces just as well. This commit adds the loading of these normals as custom loop normals. It then also enables Auto-Smoothing on the mesh (which is a bit of a misnomer and indicates to Blender that the custom normals should be used). Fixes the glitching described in T65959. Differential Revision: https://developer.blender.org/D5191 |
|
|
|


Master Commits
MiikaHweb | 2003-2021