Age | Commit message (Collapse) | Author |
|
There are a few places where DerivedMesh is still used, most notably
when calling the (not yet ported) cloth simulation. There is also still
the use of Object.derivedDeform and Object.derivedFinal. Those places are
marked with a TODO.
Some functions in the editors module were copied to accept Mesh. Those
already had 'mesh' in the name; the copies are suffixed with '__real_mesh'
for easy renaming later when the DM-based functionality is removed.
|
|
|
|
occlusion
This patch adds support for clip_planes (ie ignore what is behind a face)...
The idea is to first execute a raycast to get the polygon to which the mouse cursor points.
Then a snap test is done on the vertices or edges of the polygon.
Then with the normal and location obtained in raycast a new clip_plane is created and the snap over the whole scene is processed ignoring the elements behind the clip_plane.
Here 2 gif of how the previous patch would work on blender2.79:
{F497176}
{F497177}
Reviewers: mont29, campbellbarton
Reviewed By: campbellbarton
Subscribers: bliblubli
Tags: #bf_blender_2.8
Differential Revision: https://developer.blender.org/D2527
|
|
|
|
looptri.
This was the default behavior and could break some addon since looptri is almost useless for the current python API.
|
|
This reverts commit 717dd4cecd2ea8eaa7b3bbfb5a5c7ec65f0337c0.
It was causing problems in the protactor ruler.
I'll think of a better solution.
|
|
the ED_transform_snap_object_project_view3d_mixed.
|
|
Clip_planes are an important parameter to be used in callbacks.
|
|
And remove unnecessary `defaulf:` labels.
|
|
We need to get data from evaluated object/posechannel too, then...
|
|
Own regression from multi-object transform.
|
|
Own regression from multi-object transform.
|
|
|
|
|
|
|
|
Error in multi-object merge.
|
|
|
|
|
|
Missed from recent pivot-point move to scene.
|
|
|
|
of type armature and curve first.
And remove unused variables.
|
|
precalc used to test the distance to the projected bound_box.
|
|
Pivot variables are now stored in scene toolsettings.
|
|
Also comment unused vars
|
|
BLI_match and remove confusing parameters.
|
|
|
|
from loose verts.
Bvhtrees take up a lot of memory space, reusing the common bvhtree of looptris to snap to vertices and edges is a good way to save memory.
Unfortunately we have a worsening performance in the snapping operation around 63% (addition to the original time).
But as we often do not need to build a bvhtree of loose verts and loose edges, we have an improvement in cache time :)
Since the CPU time of snapping operations (no matter how higth poly the object is) corresponds to less than 0.01% of all CPU time of a blender frame, that change is not really significant.
Snapping operations on a mesh in edit mode have not changed significantly.
Signed-off-by: Germano <germano.costa@ig.com.br>
|
|
|
|
|
|
Differential Revision: https://developer.blender.org/D2896
|
|
|
|
|
|
Currently set when setting the cursor location,
optionally used as an orientation type.
Intended for use by tools too.
See: D3208
|
|
Add extrude operator that's intended to work on the current selection
and be activated as a tool.
|
|
|
|
|
|
Use matching 2d/3d suffix.
|
|
|
|
Some snap functions already exposed this.
|
|
|
|
Needed to redo extrude+transform macro w/o resetting the translation.
|
|
Existing code checked pose/edit mode to check for transforming in an
objects local space.
This added many similar checks all over the code,
which leads to confusion.
Multi-edit caused a regression in UV transform since where UV's
had the object matrix applied by accident.
Now there is a boolean to use a local matrix,
this allows for any mode to have a 4x4 matrix
applied w/o adding mode specific checks everywhere.
|
|
|
|
|
|
This will allow greater control of the bvhtrees that are obtained, and helps identify problems.
It is also an additional step to unify the functions.
|
|
|
|
This was broken since 33bb8b785a9 (triple-buffer changes).
This also helps help lines as a whole.
|
|
This was added for scale-cage manipulator, but seems generally useful.
|
|
This is needed for other manipulator placement.
|
|
|