Blender Git Loki

Kaikki Blender Git kommitit.

Page: 5245 / 8462

November 8, 2014, 12:34 (GMT)
Fix: Stroke filling was incorrectly propagated to the following layers

This was noticeable when the enabling onion skinning on a layer without
fills which follows one which does.
November 8, 2014, 11:58 (GMT)
Merge remote-tracking branch 'refs/remotes/origin/master' into fracture_modifier

Conflicts:
source/blender/blenkernel/intern/pointcache.c
source/blender/blenkernel/intern/rigidbody.c
November 8, 2014, 11:58 (GMT)
Merge branch 'master' into mesh-transfer-data
November 8, 2014, 11:56 (GMT)
On second though, allow modifier to create vgroups too.

This is rather hard to handle in fact, should a modifier be allowed to create vgroups,
when it cannot delete them really (because vgroups are defined at object level, not CD / DM level)?
Open question for review! :P

Also, fixed some (stupid) bugs, fixed some potential bugs, and did some cleanup.
November 8, 2014, 11:14 (GMT)
triggered objects dont need to be fractured any more and restore kinematic after load
November 8, 2014, 10:32 (GMT)
cmake buildfiles Cleanup / Refactor, no functional changes.
Move away from using hardcoded ${target} when calling install() in cmake
November 8, 2014, 04:51 (GMT)
Merge branch 'master' into GPencil_EditStrokes
November 7, 2014, 17:12 (GMT)
Allow separate widget data per editor.

To make this work, we need separate type/instance for the widgets. This
is a bit ugly but it is necessary if we want widgets on each editor to
depend of per editor-options or visibility state.
November 7, 2014, 13:56 (GMT)
Depsgraph: Add depsgraph update function to the hook modifier

This is mainly to test how this is expected to work and it seems
to be rather straightforward. Now new depsgraph can use hook :)
November 7, 2014, 13:38 (GMT)
Depsgraph: Forgot this in previous commit
November 7, 2014, 13:13 (GMT)
Depsgraph: Hook up constraints evaluation callback

Quite straightforward. There's one extra flag to the old object where_is
which helps preventing duplicated code needed for old dependency graph
system In the future we'll get rid of this argument and decouple all the
functions in a nice way.

One retarded issue is setting negative scale flag on the object, which
currently happens in both local transform and constraints update.

Bigger issue here is the original object matrix which should be used
as an input for the constraints stack. Currently constraints will operate
on the previous final object matrix when changing the dependencies of the
constraint list.

This is possible to solve by storing intermediate data in the graph
(or somewhere else(, but for until that's nicely implemented we'll probably
couple constraints back. Will investigate this further.
November 7, 2014, 12:40 (GMT)
Revert "All editable GPencil stroke points are now shown when editing is enabled"

This reverts commit 9686e48bab7340a172b0c9b8aea1f685b531d29c.

In response to feedback, I've decided to revert this since it didn't really work
that great at all when you have dense drawings. At times, this would make it
almost impossible to see what you were doing.
November 7, 2014, 12:15 (GMT)
Revert "Squashed commit of the mesh-transfer-data branch."

This reverts commit 5d21c925690ad0848f4ba0fa40556213f48849e1.
November 7, 2014, 12:14 (GMT)
Squashed commit of the mesh-transfer-data branch.
November 7, 2014, 12:14 (GMT)
Merge branch 'master' into experimental-build
November 7, 2014, 12:12 (GMT)
Add 'specific' from-layer selection to transfer operator too.

Note we do not offer specific to-layer selection, since we may transfer
to several selected objects at once.
November 7, 2014, 12:02 (GMT)
Merge branch 'master' into mesh-transfer-data
November 7, 2014, 11:52 (GMT)
Support undo. Scale stays same for non-3D widgets
November 7, 2014, 11:47 (GMT)
Depsgraph: Experiment with time source dependnecy update

Goal is to be able to play animation back for investigating how flush
happens, how object dependencies are being evaluated and all the rest
of the stuff which isn't so visible with the static scene.

Main idea here is to have a relations in the depsgraph between the time
source node and all the nodes which depends on time. We go with the
relations approach in order to make it fast to figure out which nodes
are to be tagged for updated when the time changes. It is faster to
iterate over the time dependencies rather than iterating over the whole
depsgraph,

Now, currently dependency graph's relations links only possible between
operation nodes. For this reason we don't use actual dependency structure
to define relations between time and nodes, but we've got a list of nodes
which depends on time stored in the time source node. This is the most
simple way to deal for now.

Currently we use relation between time and ID nodes, which corresponds
to how current depsgraph works, in the future we'll likely need to make
it relation betteen time source and individual components.

Or maybe even revisit the time flushes..
November 7, 2014, 11:36 (GMT)
Removed unused frame value code.
Tehnyt: Miika HämäläinenViimeksi päivitetty: 07.11.2014 14:18MiikaH:n Sivut a.k.a. MiikaHweb | 2003-2021