Blender Git Commit Log

All Blender Git commits.

Page: 4564 / 8462

January 1, 2016, 16:41 (GMT)
Renamed map of basic blocks used for expressions.
January 1, 2016, 16:41 (GMT)
Renamed the FUNCTION input value type to EXPRESSION for clarity.

'Function' is a more general term, the input is specifically an
'expression' because it returns a single value.
January 1, 2016, 16:41 (GMT)
Renamed FunctionInfo to BasicBlock, because that's what it is generally called in compilers.
January 1, 2016, 16:27 (GMT)
Implement more texture types.

This adds support for marble, magic, stucci, distorted noise, musgrave
and wood textures.
January 1, 2016, 15:30 (GMT)
make.bat: add 'clean' command
January 1, 2016, 14:42 (GMT)
make.bat: detect MSVC location

Now this can run from any command line (without having to be launched from MSVC Command Prompt)
January 1, 2016, 12:42 (GMT)
New vector math mode for vector length, patch by Philipp Oeser (lichtwerk).
January 1, 2016, 10:26 (GMT)
make.bat: sanity checks w/ useful error messages
January 1, 2016, 07:47 (GMT)
make.bat correct name for cycles target
January 1, 2016, 05:05 (GMT)
Fix for make.bat

Build install target and config path was wrong.

Also use less verbose output and enable multiprocess builds.
December 31, 2015, 18:44 (GMT)
Add helper make.bat file for ms-windows builders

See --help for options (currently still quite basic)
December 31, 2015, 15:44 (GMT)
Cycles: Implement rolling shutter effect

This is an attempt to emulate real CMOS cameras which reads sensor by scanlines
and hence different scanlines are sampled at a different moment in time, which
causes so called rolling shutter effect. This effect will, for example, make
vertical straight lines being curved when doing horizontal camera pan.

This is controlled by the Shutter Type option in the Motion Blur panel.

Additionally, since scanline sampling is not instantaneous it's possible to have
motion blur on top of rolling shutter.

This is controlled by the Rolling Shutter Time slider which controls balance
between pure rolling shutter effect and pure motion blur effect.

Reviewers: brecht, juicyfruit, dingto, keir

Differential Revision: https://developer.blender.org/D1624
December 31, 2015, 15:40 (GMT)
Fix T46915: Non-intuitive behavior of Vector Curve Mapping node

Vector mapping node was doing some weird mapping of both original and mapped
coordinates. Mapping of original coordinates was caused by the clamping nature
of the LUT generated from the node. Mapping of the mapped value again was quite
totally obscure -- one needed to constantly keep in mind that actual value will
be scaled up and moved down.

This commit makes it so values in the vector curve mapping are always absolute.
In fact, it is now behaving quite the same as RGB curve mapping node and the
code could be de-duplicated. Keeping the code duplicated for a bit so it's more
clear what exact parts of the node changed.

Reviewers: brecht

Subscribers: bassamk

Differential Revision: https://developer.blender.org/D1672
December 31, 2015, 14:05 (GMT)
Output values in node graphs are unused, removed.

In fact there is no per-output data in node instances at all, so the
OutputInstance data was removed entirely. All the connectivity and
value information is in the inputs.
December 31, 2015, 13:57 (GMT)
Fix T47046: Exporting Max and Maya keymap throws RNA warnings in console.

Totally harmless, but let's silence this bpyrna warning in case enum_items
is a DummyRNA_NULL_items, which is by definition empty...
December 31, 2015, 13:56 (GMT)
Fix memleaks in refcounted data pointers on the bvm stack.
December 31, 2015, 13:02 (GMT)
Fix wrong format used in the recent python exit code commit
December 31, 2015, 12:56 (GMT)
Libmv: Yet again update to the latest version

Again brings some fixes for MSVC-2015 and keeps it easier to backport
the fixes into upstream.
December 31, 2015, 12:49 (GMT)
Cycles: Fix viewport rendering with multiple GPU devices
December 31, 2015, 12:11 (GMT)
Fix for memleaks caused by un-freed Value instances, kudos to Kevin Dietrich!

These values are heap-allocated virtual classes, because general node code is
largely agnostic to data types. After adding values to a node (either as
default input values or per instance), care must be taken to free them when
the node type or instance is destroyed.
By: Miika HämäläinenLast update: Nov-07-2014 14:18MiikaHweb | 2003-2021