Blender Git Loki

Kaikki Blender Git kommitit.

Page: 4474 / 8462

March 24, 2016, 10:31 (GMT)
Fix some typos and incorrect tooltips/descriptions
March 24, 2016, 07:27 (GMT)
Fix T47910: Knife project fails

Regression in fix for T43896, using screen-space precision here is very problematic,
using lower precision here works for both reports.
March 24, 2016, 07:05 (GMT)
Cleanup: use prefix for return args
March 24, 2016, 06:56 (GMT)
Fix incorrect arg type
March 24, 2016, 06:52 (GMT)
Fix T47838: Walk gravity fails w/ intersecting objects

Regression in 3ad0344, fix from @mano-wii.

More comprehensive fix can be done after 2.77a.
March 24, 2016, 06:34 (GMT)
Driver Keyframing: Some tweaks to make inserting keyframes on Driver F-Curves easier

Now, when trying to insert a keyframe on a driven property (using IKEY, or with
autokeying enabled), the keyframes will get created on the Driver's F-Curve
(instead of creating a new FCurve that goes into the active action, but will never
do anything). Furthermore, the x-value of the new keyframe will be the current
result of the driver expression.

Why/Motivations:
This way, it becomes easier to create corrective drivers, as you can position all
the targets the driver depends on, then adjust the driver value until it does what
you need, and then you keyframe that value to bake it into the Driver F-Curve
(in effect, "training" the computer how to behave in that case).

Usage Notes:
* In practice, that particular workflow is still quite clunky to achieve, due to some
quirks of how the driver system and the UI widgets interact. Specifically, you'll
need to disable/mute the driver before trying to edit the setting (to prevent the
driver from immediately resetting the value - before even autokey fires!). However,
if you're using the Graph Editor to preview/monitor/manage the keying process, you'll
then want to re-enable the driver before changing the targets, so that you can see
how much of a change you'll want to be applying!

* The warning about editing driver values may need to be disabled or selectively
knocked out. I had it disabled while testing this functionality, but it's actually
harmless in its current state (if just a bit annoying).
March 24, 2016, 06:13 (GMT)
Fix T47900: VSE adjustment crashes on blank frame

Regression, should have been included in previous fix.
March 24, 2016, 02:20 (GMT)
Fix dodgy indentation
March 24, 2016, 02:15 (GMT)
Drivers UI: Added name validation/linting for Driver Variables

When attempting to change a driver variable name to an "invalid" name,
an indicator will now be shown beside the offending variable name.
Clicking on this icon will show a popup which provides more information
about why the variable name cannot be used.

Reasons that it knows about are:
1) Starts with number
2) Has a dot
3) Has a space
4) Starts with or contains a special character
5) Starts with an underscore (Python does allow this, but it's bad practice,
and makes checking security of drivers harder)
6) Is a reserved Python keyword
March 24, 2016, 00:35 (GMT)
added guards in fluid solver destructor
March 24, 2016, 00:02 (GMT)
Fix T47896: Scripted Expression string length limit is too short for some autogenerated expressions

While most scripted expressions are quite short (e.g. "var" or "frame + 1"),
those that are autogenerated by scripts (to take into account a wide range of factors)
may require a bit more headroom to operate in.

By doubling the maximum length here, we now make it possible to combine up to 38
3-letter variables in some linear combination (with all factors expressed to 4 dp).
That should be more than enough for anyone or anything for quite a while!

Unfortunately, this does increase memory consumption for drivers across the board.
March 23, 2016, 20:53 (GMT)
Revert "Cycles: Experimental proof-of-concept LWR denoising"

This reverts commit d93cc73ffdf1ecea47b80292f771d11944bbb42c.
March 23, 2016, 20:53 (GMT)
Cycles: Experimental proof-of-concept LWR denoising

This commit adds a proof-of-concept implementation of the LWR image denoising algorithm to Cycles.
To use it, just activate the new checkbox in the Sampling settings.
Some features (such as viewport rendering) might be broken, so this is definitely not suitable
for doing actual work with it yet.
March 23, 2016, 20:50 (GMT)
Merge remote-tracking branch 'origin/master' into experimental-build
March 23, 2016, 19:05 (GMT)
fixed pyobject reference count and changed mantaflow deallocation callback -> solver objects now deleted as well
March 23, 2016, 18:28 (GMT)
Revert "Fix T47869: OpenColorIO Error with unicode path to config file under Windows"

White the config itself could be loaded this way, lookup tables can not. Additionally,
that's not really clear how to solve the issue with search path which is multi-byte
only in the API.

Reverting for further investigation.

This reverts commit ab4307aa0868f2d8389cc0dd500eff38909b08f1.
March 23, 2016, 18:23 (GMT)
Fix T47900: VSE adjustment crashes on blank frame
March 23, 2016, 16:16 (GMT)
Merge branch 'libquery-recursive' into asset-engine
March 23, 2016, 16:16 (GMT)
Merge branch 'master' into asset-engine
March 23, 2016, 16:08 (GMT)
Merge branch 'libquery-recursive' into id-remap
Tehnyt: Miika HämäläinenViimeksi päivitetty: 07.11.2014 14:18MiikaH:n Sivut a.k.a. MiikaHweb | 2003-2021