Blender Git Statistics -> Developers -> lichtwerk
Philipp Oeser (lichtwerk)
Total Commits : 885
Master Commits : 799
Branch Commits : 86
First Commit : March 11, 2015
Latest Commit : April 13, 2021 (Yesterday)
Commits by Month
Date | Number of Commits | |
---|---|---|
April, 2021 | 10 | |
March, 2021 | 38 | |
February, 2021 | 23 | |
January, 2021 | 33 | |
December, 2020 | 16 | |
November, 2020 | 23 | |
October, 2020 | 40 | |
September, 2020 | 28 | |
August, 2020 | 35 | |
July, 2020 | 17 | |
June, 2020 | 11 | |
May, 2020 | 53 | |
April, 2020 | 58 | |
March, 2020 | 35 | |
February, 2020 | 29 | |
January, 2020 | 36 | |
December, 2019 | 9 | |
November, 2019 | 26 | |
October, 2019 | 44 | |
September, 2019 | 49 | |
August, 2019 | 23 | |
July, 2019 | 26 | |
June, 2019 | 5 | |
May, 2019 | 23 | |
April, 2019 | 20 | |
March, 2019 | 10 | |
February, 2019 | 13 | |
January, 2019 | 16 | |
December, 2018 | 35 | |
November, 2018 | 21 | |
October, 2018 | 12 | |
September, 2018 | 0 | |
August, 2018 | 0 | |
July, 2018 | 10 | |
June, 2018 | 14 | |
May, 2018 | 21 | |
April, 2018 | 2 | |
March, 2018 | 0 | |
February, 2018 | 0 | |
January, 2018 | 5 | |
December, 2017 | 1 | |
November, 2017 | 0 | |
October, 2017 | 0 | |
September, 2017 | 0 | |
August, 2017 | 0 | |
July, 2017 | 0 | |
June, 2017 | 0 | |
May, 2017 | 0 | |
April, 2017 | 0 | |
March, 2017 | 0 | |
February, 2017 | 0 | |
January, 2017 | 1 | |
December, 2016 | 0 | |
November, 2016 | 0 | |
October, 2016 | 0 | |
September, 2016 | 4 | |
August, 2016 | 0 | |
July, 2016 | 1 | |
June, 2016 | 1 | |
May, 2016 | 1 | |
April, 2016 | 1 | |
March, 2016 | 2 | |
February, 2016 | 0 | |
January, 2016 | 0 | |
December, 2015 | 0 | |
November, 2015 | 0 | |
October, 2015 | 0 | |
September, 2015 | 0 | |
August, 2015 | 3 | |
July, 2015 | 0 | |
June, 2015 | 0 | |
May, 2015 | 0 | |
April, 2015 | 0 | |
March, 2015 | 1 |
Commit Distribution
Favourite Files
Filename | Total Edits |
---|---|
blender_default.py | 18 |
particle_edit.c | 18 |
space_view3d.py | 14 |
object_relations.c | 13 |
interface_templates.c | 12 |
object_constraint.c | 11 |
rna_nodetree.c | 10 |
rna_object_force.c | 10 |
object_add.c | 9 |
interface_handlers.c | 9 |
File Changes
Action | Total | Per Commit |
---|---|---|
Modified | 1 106 | 1.2 |
Code Changes
Action | Total | Per Commit |
---|---|---|
Lines Added | 7 973 | 11.0 |
Lines Removed | 4 523 | 6.2 |
Latest commits 
1 day and 15 hours ago |
Motion Tracking: setting Keyframe A & B was not updating UI indicators Entering the numbers in the keyframe field was not triggering a viewport update, so the little green lines down in the cache area were only change when the user e.g. changed the frame. Now send appropriate notifiers. Issue spotted in T86456 by sebastian_k. Maniphest Tasks: T86456 Differential Revision: https://developer.blender.org/D10963 |
April 9, 2021, 07:14 (GMT) |
Fix T87150: bad points appearance in orthographic view Points are drawn as half octahedron (aligned to the camera). Getting the appropriate matrix for facing the camera would fail in in orthographic view, points were not facing the camera (revealing their missing other half octahedron) Maniphest Tasks: T87150 Differential Revision: https://developer.blender.org/D10923 |
April 8, 2021, 06:36 (GMT) |
Fix T87267: Texture Paint stencil texture not drawing Typo in {rBafcfc6eb0842}. Maniphest Tasks: T87267 Differential Revision: https://developer.blender.org/D10915 |
April 7, 2021, 16:44 (GMT) |
Fix T87263: Animation decorator not working on Grease Pencil Build modifier Factor value When having a checkbox and a value both in one row together with an animation decorator it is questionable whether the decorator should act on animating the checkbox or the corresponding value. At the moment, usage in modifiers does not seem to be very consistent: Here the animation decorator works for animating the checkbox: - `Build` (greasepencil) > `Factor` (this was reported and is changed in this patch to act on the value instead of the checkbox) - `DataTransfer` > `Topology Mapping` > `Max Distance` (this I guess should also act on the value instead of the checkbox) - `Edge Split` > `Edge Angle` (questionable) - `Mirror` > `Merge` (questionable) - `Screw` > `Merge` (questionable) - `Wireframe` > `Crease Edges` (questionable) Here the animation decorator works for animating the value: - `VertexWeightEdit` > `Group Add/Remove Threshold` - `Decimate` > `Symmetry` So in this patch only the behavior in the greasepencil Build modifier UI is changed, since I think it is quite obvious that one would more often use the decorator for animating the factor value than for animating the checkbox. Maniphest Tasks: T87263 Differential Revision: https://developer.blender.org/D10910 |
April 6, 2021, 15:01 (GMT) |
Fix T87236: crash reading file with grease pencil palettes Caused by typo in {rB76689e851700}. Since Palettes and bGPDpalette are not the same size, this would not only cause a crash in versioning code, but could only go downhill from here on. Maniphest Tasks: T87236 Differential Revision: https://developer.blender.org/D10903 |
April 6, 2021, 09:14 (GMT) |
Fix T86932: Curve: pick shortest path missing update of active point drawing For curves, we need to tag the curve ID_RECALC_COPY_ON_WRITE for batch cache update (same as in {rB24b2fe50f3ec}). Maniphest Tasks: T86932 Differential Revision: https://developer.blender.org/D10826 |
April 6, 2021, 09:06 (GMT) |
Fix T84623: Curve/Surface force not working in normal direction Tweaking e.g. a field strength would then not use the curve/surface normal anymore [but the object center instead]. If a curve has a forcefield with effector shape Curve (in code its shape is PFIELD_SHAPE_SURFACE then), it wil get a SurfaceModifier. Changing properties will free the SurfaceModifierData's bvhtree and mesh And these dont get copied along when doing the CoW copy, these are explicitly set to NULL. So this was also failing for meshes, not just curves. Without the mesh & bvhtree though, get_effector_data() will not set the EffectorData's normal correctly (it is closest_point_on_surface() which does this). And without the right EffectorData's normal, the effector will of course work unexpected. Going in and out of editmode made this work because that goes down this route: - BKE_object_handle_data_update - BKE_displist_make_curveTypes - do_makeDispListCurveTypes - curve_calc_modifiers_post -- BKE_mesh_new_nomain_from_curve_displist -- we then have our desired updated mesh from the curve -- this will also call the SurfaceModifiers deformVerts [which - given we have a valid mesh - will update the bvhtree properly] Also note that _animating_ the effector actually works, (have not done the deep dive why this works, assume the curve geometry is updated in this case) So, now just carefully tag the curve ID_RECALC_GEOMETRY in rna_FieldSettings_update for this specific case. Maniphest Tasks: T84623 Differential Revision: https://developer.blender.org/D10092 |
April 6, 2021, 04:59 (GMT) |
Fix T48167: Mesh select random factor is not accurate Selecting random percentage would not reliably guarantee the precise percentage of selected elements now randomize an index array instead and use the precise number of elements from this array. Note that this change has only been made to edit-mesh and should be applied to all random selection operators. |
April 2, 2021, 19:23 (GMT) |
GPencil: Prevent RNA assignment of invalid materials in modifiers Materials used in grease pencil modifiers have the requirement that they are already used on the object. In the UI dropdown, this restriction is ensured by calling uiItemPointerR with appropriate searchptr and searchpropname, so only giving the user the choice of materials already used on the object. From python though, it was still possible to assign materials outside of this this restriction. This led to reports like T86981 [which have been partially solved by clamping the material index in the modifier code to be in the valid range]. Now make sure we dont assign "invalid" materials through RNA by appropriate RNA pointer functions. This also adds a proper warning (red, alert) in case of the LineArt modifier if such a invalid material is still in the file [same as other modifiers already do]. Differential Revision: https://developer.blender.org/D10873 |
April 2, 2021, 19:18 (GMT) |
Fix T86654: wrong Vertex Interpolation option default when importing alembic caches This resulted in bad motion blur from alembic animation when imported after rB83980506957c (because it was now OFF by default). When imported in a version prior to rB83980506957c and saved, this was still working fine. Vertex interpolation option introduced in rBbab2260b59c7 was defaulting to ON (correct) in that commit, but was lost in rB83980506957c. Now switch this to ON by default again. Note: if you have a file that was (incorrectly) imported with a version after rB83980506957c you'll have to enable Vertex Interpolation option on every MeshSequenceCache modifier by hand. Maniphest Tasks: T86654 Differential Revision: https://developer.blender.org/D10876 |
MiikaHweb - Blender Git Statistics v1.06