Age | Commit message (Collapse) | Author |
|
Stroke update use now the location from Strokecache instead of the mouse
position.
Differential Revision: https://developer.blender.org/D5861
|
|
in Dopesheet
Differential Revision: https://developer.blender.org/D5868
|
|
Modifier stack evaluation would copy mesh settings other than mesh topology
automatically, outside of the individual modifier evaluation. This leads to hard
to understand code, and makes it unclear which settings are available in following
modifiers, and which only after the entire stack is evaluated.
Now every modifier is responsible to ensure the mesh it outputs preserves materials,
texture space and other settings, or alters them as needed.
Fixes T64739: incorrect texture space for various modifiers
Differential Revision: https://developer.blender.org/D5808
|
|
|
|
These were only strictly valid for texture space calculation, don't store them
since they should not be used after that. Only store a flag to indicate if the
auto texture space has been evaluated.
In the future it might make sense to store bounding boxes at the mesh level to
speed up bounding box computation for multiple objects using the same mesh, but
then it will need to be implemented differently.
|
|
This fixes the regression from T70103 introduced by the fix for T70103.
|
|
|
|
This commit accidentally undid a bunch of previous commits. Only the intended
changes are left now.
|
|
This makes a lot of shader node wiring code less complex.
This only add the flatten mechanism (which fixes T69672).
~~Cleanup to remove the complexity in ntree_shader_relink_displacement,
ntree_shader_bump_branches and ntree_shader_tag_nodes will be commited
separately.~~(already included)
The code is only added for shader nodes for now but could be exported to
other internal nodetree types in the future.
Cleanup: Node Shader Tree: Remove GPUmaterial special nodegroup handling
Reviewers: brecht
Reviewed By: brecht
Maniphest Tasks: T69672
Differential Revision: https://developer.blender.org/D5829
|
|
|
|
D5857 by @cmbasnett
|
|
|
|
Reviewed By: JacquesLucke
Differential Revision: https://developer.blender.org/D5803
|
|
Add check if fcurve is empty to skip fcurve evaluation.
Reviewed By: JacquesLucke
Differential Revision: https://developer.blender.org/D5805
|
|
Tag depsgraph update as a part of cache invalidation.
Author: mdewanchand
Reviewed By: ISS
Differential Revision: https://developer.blender.org/D5718
|
|
This happens to be a non-behavioral change, but previous code here was
*very* confusing, and only ended up generating expected results by mere
chance (since `facepa[i]` == `totpart` in case the face has no (valid)
particle, i.e. `pa == NULL`)...
|
|
Systematically reset particle pointer to NULL and use it to detect
invalid particle case, instead of checking value of the face's
particle index everywhere in a confusing and prone-to-bug way
(see T70150 and previous commit).
No behavioral change expected here.
|
|
There’s be a lot to say about that explode modifier code, for now just
follow other places in code... But the handling of 'invalid'/'unkown'
particle case is... quiet confusing to say the least.
|
|
Follows general logic, and are placed next to similar tools.
|
|
|
|
This was a mistake when fixed the problem with multiframe sculpt. I missed change the index and use active point in the check.
|
|
This decomposition is useful in rigging, and involves a math trick.
|
|
Before when Onion or Multiframe was enabled the VBO length was the total of points on the object for all frames and this results in a big size when the scene had a lot of frames.
Now, the size of VBO length is calculated more precisely and reduce the time to alloc the VBO.This also reduce memory footprint.
|
|
|
|
If there aren't modifiers or they are not transform type, the rotation is not needed.
|
|
Instead to use the 3D cursor as reference point (legacy code), it would be better use the object location.
Tested by: @pepeland
|
|
As multiframe does not use modifiers, this is not required and only gets weird results.
Related to T70116
|
|
Related to T70116
|
|
The flag was working in the oposite mode.
Related to T70116
|
|
As the evaluated data is not calculated in multiframe, needs to have the original colors.
Related to T70116
|
|
|
|
Related to T70116
|
|
The evaluated frame is only available when the frame is the active one.
Related to T70116
|
|
The selection was not working because the evaluated frame was only working for active frame, so when the evaluation was changed to use eval data instead of original data, the data was not available and the loop did not use it.
Related to T70116
|
|
|
|
|
|
space issues"
This reverts commit e7a514369fe700dcc5a1fe433c8f709ed9595ded, it introduces
a bug in selection in edit mode.
Fixes T70103: can't select extruded Vertex
Ref T64739
|
|
NDEBUG is the standard define, not DEBUG.
|
|
E.g. entering the file path field and then pressing enter without any
change would call an unneccesary directory change, causing flickering.
So the main point of this is to avoid flickering.
Without this the text field could also be used to refresh the file list,
but for that we have a proper button.
|
|
The big options button in the lower left is now gone, it's replaced by a
smaller icon toggle button in the upper right.
That means I could also remove code for the region we had just for this
button.
I also added versioning code for the removal, to make sure the region is
removed cleanly when reading old files.
|
|
The BVHTree was erroneously marked as not cached.
|
|
Pablo and William agreed that the main purpose of the layout should be
to list files in a way that it's easy see which files were
created/modified when. Previously it was set to "Long List" to show the
modification time, now the vertical list is much better suited. The time
is shown anyway.
|
|
|
|
For the default keymap we were only using the regular toolshelf
operator, doing this for the industry compatible keymap too now (we
could even remove it there, we don't use it in other editors).
Since we "now" have proper operators for toggling regions, this specific
one is totally redundant.
|
|
So far the file browser code had some lazy creation for the tool region,
even though it should always be there. The only reason I can see for
this is compatiblity. So I simply added versioning code to add the
region in case it's not there. Now we should be able to savely assume
the tool region to be there, whithout any unusual lazy-creation.
|
|
This makes it so that regions only needed when the file browser is
invoked as an operation (e.g. Ctrl+O rather than a regular editor) are
lazy created then, and removed if the file browser is changed into a
regular editor then (e.g. Ctrl+O over regular file browser editor ->
Cancel).
That should remove some troublesome assumptions and makes versioning
redundant.
It also fixes the issue of an empty execute region at the bottom after
cancelling a file operation invoked from a regular file browser editor.
|
|
Differential Revision: https://developer.blender.org/D5716
|
|
Adjust empty menu check to skip the menu title.
|
|
|
|
Differential Revision: https://developer.blender.org/D5847
|