Blender Git Loki

Blenderin Git "master"-kehityshaaran kommitit.

Page: 2995 / 5574

January 2, 2014, 20:34 (GMT)
Fix T38033: cycles volume emission changes with step size.
January 2, 2014, 19:44 (GMT)
Fix T37056: Making segment flips curves it's not needed

Made the system around splines order a bit smarter, so
crating a segment between two splines wouldn't switch
direction if splines are selected in a way that they're
"co-linear".

It is possible to make things even smarter using active
point and so, but that i'd consider a TODO.
January 2, 2014, 19:34 (GMT)
Bring back edit curve add menu

It was wrongly considered unused in rB5fdfa6d47542db32426ac080f071a1fd751e05a7
January 2, 2014, 16:59 (GMT)
Fix T37170: Missing curve outline when using constructive modifiers

Issue was caused by wrong bool flag assignment.
January 2, 2014, 11:57 (GMT)
Fix T38004: size of Waveform, Vectorscope and Histogram is incorrect in VSE

Made it so scopes image buffer is displayed without any additional scale
applied on them,

Further tweaks are possible here, but that i'd consider a TODO.
January 2, 2014, 11:44 (GMT)
Fix T38002: crash selecting a view mode for "Preview" in Sequence Editor
January 2, 2014, 11:04 (GMT)
Add back - and / shortcuts in modal numinput (as other 'special' keys, you have to use ctrl to activate them)...
January 2, 2014, 11:04 (GMT)
Fix "Flipped" drawn in edgeslide header text even when Even is disabled.
January 2, 2014, 11:04 (GMT)
Fix T38019: Edge/Vertex Slide recognises Even and Flipped as if they were numerical values

Further tweaked/simplified events handling in transform code, hope this time it works OK...
January 2, 2014, 09:24 (GMT)
Code cleanup: remove patch series from libmv

Since we're using own libmv branch from git.blender.org
we don't need to have local patches for libmv in blender
source tree.
January 2, 2014, 09:24 (GMT)
Code and style cleanup

Mainly fixed some style warnings reported by cpplint.

Also changed how camera (un)distortion happens internally
by replacing number of channels as a template argument
with number as channels passing as function argument.
Makes code easier to follow by eliminating loads checks
how much channels are used and which argument to pass to
the template.
Revision f754410 by Joshua Leung
January 1, 2014, 23:51 (GMT)
Fix T38025: Key-framing lattice points fails

Clarified the tooltip/description on the LatticePoint.co property to make it
clear that it shouldn't be edited, and that LatticePoint.co_deform should be
used instead.
January 1, 2014, 23:26 (GMT)
Add new BGE Stereo mode: 3DTV top-bottom.
This mode is designed for passive 3D TV: the viewport is split
horizontally - left eye above, right eye below - but the original camera
viewport is squashed in each half (with half the vertical resolution).
This is necessary to restore the aspect ratio in the 3D output because the TV expands each half to the full screen size.
January 1, 2014, 17:27 (GMT)
Code cleanup: use bool flag for direction in clip prefetch

That was nothing really wrong with the old short used for
direction, but that became kinda annoying because of compiler
idiocy which considered direction might have been zero.

Using explicit dual-state flag is more clear anyway.
January 1, 2014, 16:45 (GMT)
Code cleanup: line wraps and file names in doxy comments
January 1, 2014, 16:32 (GMT)
Fix crash happening in Cycles fcurve modifier

Summary:
Crash was happening because of fcurve modifier stack
used modifier's DNA to store temporary data.

Now made it so storage for such a thing is being
allocated locally per object update so multiple objects
which shares the same animation wouldn't run into
threading conflict anymore.

This storage might be a part of EvaluationContext,
but that'd mean passing this context all over in
object_where_is which will clutter API for now without
actual benefit for this.

Optimization notes: storage is only being allocated
if there're Cycles modifier in the stack, so there're
no extra allocations happening in all other cases.

To make code a bit less cluttered with this storage
passing all over the place added extra callbacks to
the FModifier storage which runs evaluation with the
given storage.

Reviewers: brecht, campbellbarton, aligorith

CC: plasmasolutions

Differential Revision: https://developer.blender.org/D147
January 1, 2014, 16:32 (GMT)
Re-bundle libmv from new upstream repository

No functional changes, just to make sure all the patches
are ported nicely and that update scripts works fine.
January 1, 2014, 16:32 (GMT)
Split tracking.c into several files

File tracking.c became rather huge and annoying to
maintain and it really contains several independent
areas of motrack pipeline.

Now we've got:

* tracking.c: general-purpose functions which are used
by blender, clip editor, RNA and so.

* tracking_detect.c: feature detection functions
(blender-side, logic is still in libmv).

* tracking_plane_tracker.c: blender-side 2D tracking logic.

* tracking_plane_tracker.c: plane track tracker.

* tracking_solver.c: functions for camera solving.

* tracking_stabilize.c: 2D stabilization functions.

* tracking_util.c: utility functions for all those files
and which shouldn't be public.
January 1, 2014, 16:32 (GMT)
Update Ceres to the latest upstream

Summary:
This brings up much easier termination type usage,
which for us means we might use:

ceres::Summary::IsSolutionUsable()

instead of doing manual funky enum values check.

Reviewers: keir

Differential Revision: https://developer.blender.org/D153
January 1, 2014, 16:32 (GMT)
Fix deadlock happening when using Save Buffers for render

Summary:
Issue was caused by the same tile being written twice to
the EXR file. This was happening because of partial update
of work-in-progress tiles was merging result to the final
render result in order to make color management pipeline
happy.

We need to avoid such a merges and keep memory usage as
low as possible when Save Buffers is enabled.

Now render pipeline will allocate special display buffer
in render layer which will contain combined pass in the
display space. This keeps memory usage as low as we can
do at this moment.

There's one weak thing which is changing color management
settings during rendering would lead to lossy conversion.
This is because render result's display buffer uses color
space from the time when rendering was invoked.

This is actually what was happening in previous release
already actually so not a big issue.

Reviewers: brecht

Reviewed By: brecht

Differential Revision: https://developer.blender.org/D162
Tehnyt: Miika HämäläinenViimeksi päivitetty: 07.11.2014 14:18MiikaH:n Sivut a.k.a. MiikaHweb | 2003-2021