January 31, 2021, 13:07 (GMT) |
XR: Remove remaining use of GHOST types in RNA It might be good to have a WM equivalent for GHOST_XrPose (e.g. wmXrPose) since converting from location/rotation or float[7] to GHOST_XrPose can be pretty awkward. |
January 30, 2021, 18:15 (GMT) |
GPencil: New option to disable automatic zoom (WIP) The UI is still in progress |
January 30, 2021, 17:15 (GMT) |
Merge branch 'master' into sculpt-dev |
January 30, 2021, 15:19 (GMT) |
Merge branch 'master' into temp-gpencil-io |
January 30, 2021, 15:19 (GMT) |
Merge branch 'master' into temp-gpencil-interpolate |
January 30, 2021, 15:18 (GMT) |
Merge branch 'master' into temp-gpencil-bezier-v2 |
January 30, 2021, 15:18 (GMT) |
Merge branch 'master' into greasepencil-object |
January 30, 2021, 15:17 (GMT) |
Merge branch 'master' into temp-gpencil-fill |
January 30, 2021, 12:45 (GMT) |
Alembic procedural: use an enumeration to discriminate object types Using ObjectHeader::matches involves allocating strings which showed in profiles. |
January 30, 2021, 03:17 (GMT) |
XR: Start refactoring internal API Remove unnecessary data from GHOST types and mostly eliminate use of GHOST types at RNA level. At the WM level, action creation functions deal with single actions (instead of multiple actions at once) to simplify the API. |
January 29, 2021, 23:14 (GMT) |
EEVEE: Depth of field: Fix incorrect prediction for holefill tiles Holefill is only needed if having foreground elements in the tile. |
January 29, 2021, 22:46 (GMT) |
EEVEE: Depth of field: Improve slight defocus opacity estimation This correct the opacity estimate (for some reason the number of samples returned by dof_gather_total_sample_count is wrong and ring_count needs to be incremented). Also adds a bias towards the focused area to improve the transition to fully opaque. |
January 29, 2021, 22:34 (GMT) |
EEVEE: Depth of field: Bleed more background over in-focus area Improves water-tightness. |
January 29, 2021, 21:44 (GMT) |
Merge branch 'master' into sculpt-dev |
January 29, 2021, 18:53 (GMT) |
GPencil: Cutter in Multiframe Changes to support multiframe cutter |
January 29, 2021, 17:34 (GMT) |
Merge branch 'master' into cycles_procedural_api |
January 29, 2021, 16:54 (GMT) |
GPencil: Show fill progress |
Revision c897885 by Alexander Gavrilov January 29, 2021, 16:04 (GMT) |
Armature: add B-Bone lengthwise scaling and custom handle scaling options. In addition to the base bone transformation itself, B-Bones have controls that affect transformation of its segments. For rotation the features are quite complete, allowing to both reorient the Bezier handles via properties, and to control them using custom handle bones. However for scaling there are two deficiencies. First, there are only X and Y scale factors (actually X and Z, but this is the legacy naming), while lengthwise all segments have the same scaling. The ease option merely affects the shape of the curve, and does not cause actual scaling. Second, scaling can only be controlled via properties, thus requiring up to 6 drivers per joint between B-Bones to transfer scaling factors from the handle bone. This is very inefficient. This patch addresses these deficiencies by adding Length scale inputs, and providing toggles to apply custom handle local scale channels to the now four scale-related properties. The 'Length' name is used to avoid confusion due to the X/Y vs X/Z naming. The two Length scale inputs control the ratio between the lengths of the start and end segments of the bone: although for convenience two inputs are provided, the whole chain is still uniformly scaled to fit the curve. A Scale Easing option is provided to multiply the easing value by the Length scale factors to synchronize them - this produces a natural scaling effect where both the shape of the curve and the scale is affected. The second issue is addressed by providing toggles for each handle that multiply each of the X, Z, Length and Ease values by the matching Local Scale channel of the handle bone, thus replacing trivial drivers. The Scale Easing option has no effect on this process since it's easy to just enable both Length and Ease buttons. Finally, this fixes a strange behavior where the segments were not actually scaled in the Y direction to match their actual length, thus producing gaps or overlap depending on the shape of the curve. For transformation the change should be very small if enough segments are used, but this will affect the results of the Copy Transforms and Armature constraints, so a backwards compatibility option is provided. Newly created bones default to the new behavior. Differential Revision: https://developer.blender.org/D9870 |
Revision 0e42662 by Alexander Gavrilov January 29, 2021, 16:04 (GMT) |
Bone Overlay: support bone wireframe opacity settings. When weight painting the bone overlay is extremely intrusive, effectively requiring either extensive use of hiding individual bones, or disabling the whole bone overlay between selections. This addresses the issue by adding two bone opacity sliders that are used for the 'wireframe' armature drawing mode. One directly controls the opacity in a uniform way. The other one allows fade based on the depth between the near and far clip planes in order to provide an automatic visual cue about which bones are closest. |
Revision a898a70 by Alexander Gavrilov January 29, 2021, 16:04 (GMT) |
Depsgraph: connect up drivers on various physics properties. It seems drivers for physics properties weren't being linked to evaluation nodes. This connects settings used by modifiers to Geometry; particle settings and rigid body data to Transform which seems to contain rigid body evaluation; and force fields to object Transform, since fields can exist on empties. Differential Revision: https://developer.blender.org/D10088 |
|