| Age | Commit message (Collapse) | Author |
|---|
|
Conflicts:
source/blender/editors/object/object_shapekey.c
|
|
(as Vertex Group).
Was more a feature request actually, but anyway...
Note this is a bit more complex than it's vgroups counterpart, since we have to handle
relations between keys (relative keys, and position for absolute ones).
|
|
Added a small menu with a few helper oerators next to each group panel:
* Remove group from all objects
* Select objects in group
More could be added possibly in the future.
Thanks to Campbell for the advice here.
|
|
|
|
|
|
Conflicts:
source/blender/blenloader/intern/versioning_270.c
|
|
|
|
The issue was caused by the render engine loading edit mesh, which re-allocates
mesh array which might be referenced by other object's derived meshed.
Worst thing about this is that updating render engine happens from the end of
scene update function, after all the objects are updated and so. This is needed
so render engine gets the update objects which is correct.
The only proper way to solve the issue is to make it so viewport engine does not
leave objects in inconsistent state, meaning nobody will reference to freed data.
In order to reach this we do edit mesh loading before running objects update so
all the objects which uses that mesh will have proper references in the derived
mesh.
This also solves old creepyness which happened before when having single object
in edit mode. tweaking it will calculate derived mesh as a part of scene update,
then this derived mesh will be freed by edit mesh loading and viewport will be
creating derived mesh again.
Now render engine is expected to do nothing with meshes which are in edit mode,
but they still need to load edit data for non0meshes. It's not really easy to
do from the BKE level because needed functions are implemented in the editor.
Thanks Campbell for the review!
Differential Revision: https://developer.blender.org/D697
|
|
(original patch by Sergey Sharybin)
Note: RNA API can't use size_t at the moment. Once it does this patch
can be tweaked a bit to fully benefit from size_t larger dimensions.
(right now num_pixels is passed as int)
Reviewed By: sergey, campbellbarton
Differential Revision: https://developer.blender.org/D688
|
|
|
|
|
|
We could make the exec to also show the progress bar, but I think it is not needed.
|
|
If the active image node contributes to the final material shader
(meaning it's either directly or indirectly connected to an Output Node)
the user will receive an alert about circular dependency.
Similar to what we do for Blender internal the baking will still happen,
but the user will receive the alert which should prevent the image
saving to happen if the result was not intentional.
Core function to check for node output written by Lukas Toenne.
Reviewers: lukastoenne, campbellbarton
Differential Revision: https://developer.blender.org/D673
|
|
Importantly, reversed mul_serie_m3 argument order (so it matches the m4 function)
|
|
NULL's)
|
|
|
|
|
|
Note: This makes no change to the user, the render engine (Cycles) still
need to update the progress during baking. But this is the Blender side
of this.
|
|
|
|
Sort vertex groups by Armature Hierarchy
Reviewers: mont29
Differential Revision: https://developer.blender.org/D649
|
|
|
|
|
|
|
|
Revert "Object Select Similar tool now has a Pass Index option."
This reverts commit 7a6919a74eb08caaf21030c17fe7c2723394a3d6.
|
|
|
|
...as per qurq's request finally!
|
|
Keying Set is inappropriate
|
|
Changed the polling method used for both the add and remove LoD operators
to a more appropriate one.
|
|
|
|
emitting a ND_NLA_ACTCHANGE signal now to make that work.
Found while documenting the NLA for my upcoming book
|
|
This is a misnomer: the operator copies data (mostly pointers) of
various types from the active to selected objects. "Make Link" implies
creating a permanent connection between these objects ...
|
|
|
|
|
|
Keying Sets
Most of the default builtin Keying Sets (e.g. Loc, Rot, Available, etc.) depend
on the currently selected objects, making them unsuitable for use with this feature.
As a result, this feature would silently fail. This commit adds some error messages
which at least let users know what's going on so that they can make other plans
|
|
psys.
This is inconsistent with other comparable cases like materials, where
the active slot is used to define matching objects.
|
|
|
|
|
|
Mostly missing 'static' declarations and some potential bugs.
|
|
Fix to be included in 2.71
|
|
Reported by Andy Davies (metalliandy) outside the tracker
Fix to include in 2.71
|
|
Error
Users can now bake from Mesh, Font, Curve, Surface and Metaballs.
Fix to include in 2.71
|
|
|
|
|
|
Note: the custom UV option is only available when calling the operator
via a script. It's currently not exposed in the UI since it's intended
to be used by scripters
To test it:
bpy.ops.object.bake(type='UV', use_clear=True, uv_layer='MyNewUV')
Reviewers: campbellbarton
Differential Revision: https://developer.blender.org/D546
|
|
Now I have a facny 2.71 splash too!
Conflicts:
source/blender/blenloader/intern/versioning_270.c
|
|
Fix to include in 2.71 (asked via BlenderArtist)
|
|
Also it has a better error handling for the BVHTree creation
Fix for 2.71
|
|
- BLI_BITMAP_SET -> BLI_BITMAP_ENABLE
- BLI_BITMAP_CLEAR -> BLI_BITMAP_DISABLE
- BLI_BITMAP_GET -> BLI_BITMAP_TEST
- BLI_BITMAP_MODIFY -> BLI_BITMAP_SET
|
|
|
|
Suggestion by Andy Davies (metalliandy) to conform with industry standard (custom cage is something else apparently)
Note: this is the last bake related commit I plan for 2.71/rc (unless
everyone agrees that we could squeeze in D546 - custom UVs, which would
be really nice to add for 2.71 scripters)
Note 2: I'll update the wiki docs shortly
|
