| Age | Commit message (Collapse) | Author |
|---|
|
Quite straightforward implementation -- all the conversion magic is
happening in IMB_exr_write_channels() and remained changes are only
needed to pass information whether channels is to be converted to
half float or not.
Regular file output will use full-float for Z pass, which matches
behavior of the single layer EXR files. But when saving happens
with File Output node then all the passes are respecting half float
settings because it's not possible to distinguish whether we're
saving Z pass or not.
Reviewers: juicyfruit, campbellbarton
Reviewed By: campbellbarton
Subscribers: maxon, effstops, fsiddi
Differential Revision: https://developer.blender.org/D1353
|
|
Useful for scaling all UV islands
|
|
Avoids counting the whole queue when we only want to check whether it is empty or not!
|
|
Noisy and annoying with new gcc5...
|
|
Useful to fill an array in the order its added.
|
|
|
|
|
|
|
|
into alpha in 2.75 RC1
|
|
This is mainly useful for the render farms output when logging might stop at
the "Path Tracing Tile N/N" string, which makes it a bit difficult to follow
what exactly is happening (node going crazy, hardware issues or just last tile
is too much heavy).
This is more like an experiment, might be changed in the future.
|
|
reading file has failed
This way automated scripts can actually see if some issue happened.
|
|
They'll be checked for the version later and that check will fail anyway,
so better to not allow user to see unsupported device in the list.
Also corrected one more issue with the device enumeration.
|
|
This is typically an error (& hangs a few seconds on win32), best catch early.
|
|
- was doing 2x spin-locks, multi-view check and hash-lookup per face-corner.
- avoid doing customdata layer lookup per face.
|
|
|
|
|
|
|
|
The assertion code was not taking quad faces into account.
Problem report by Folkert de Vries (flokkievids) through personal
communications, thanks!
|
|
- minor corrections
- link to new manual
- wrap lines at 120
|
|
This patch suppresses the outdated KX_PolygonMaterial.rst documentation file and moves the example contained in it into KX_BlenderMaterial.rst.
The file KX_BlenderMaterial.rst receives some extra formatting changes (lists are not supported in methods arguments types).
Reviewers: kupoman, campbellbarton, lordloki, panzergame, moguri
Reviewed By: panzergame, moguri
Projects: #game_engine
Differential Revision: https://developer.blender.org/D1355
|
|
|
|
Creating triangles at endpoints is often not so good, disable by default.
|
|
Save Buffers option is enabled"
This reverts commit ab417f31f403d74a76fb51fbd6e2aa3f706e15f1.
This workaround caused serious memory corruption issues which is not really acceptable
for the release. We'll be likely sticking to a more limited release when using freestyle
with saved buffers for until proper solution is implemented.
Conflicts:
source/blender/render/intern/source/pipeline.c
|
|
The issue was caused by render pipeline freeing render parts prior to finishing
exr file writing which resulted in unfinished parts not being written into the
file by save_empty_result_tiles().
As a temporary solution we do explicitly write unfinished parts as empty tiles
to the exr file prior to freeing parts.
Not ideal solution, but should work for the release.
|
|
|
|
This reverts commit 810f8928d65abbce6dddc1e11f6092c22d9a5fcc.
Worked by accident with MSVC, real fix next...
|
|
|
|
|
|
|
|
|
|
|
|
Without this extra flush order of stat prints is undefined in the
output. which makes it rather tricky to write custom output in a
reliable way.
|
|
This includes total render time spent on rendering since render() was
invoked and also prints time of actual rendering (without synchronization
step).
|
|
Copy modifiers operator would copy modifier to all strips, even
unselected ones.
|
|
working
(it would behave like 'bone envelope resize' instead).
Issue comes from the fact this transform op shares some common points with both BoneResize
and BoneEnvelope operations. However, trying to re-use `TFM_BONE_ENVELOPE` itself in this case
is bad idea, since this mode gets stored in transform op and is directly re-used for redo,
by-passing the whole init phase that shall be done in `TFM_BONESIZE` mode... So now,
we add a real new mode, `TFM_BONE_ENVELOPE_DIST`, while keeping most of existing code
and all existing behavior.
This is slightly hackish - but was already anyway, and avoids creating a full new set of
function for pretty much the same thing. As a side note, also makes it possible to
resize envelope distance outside of envelope viewing mode (from py or by adding a custom
shortcut).
|
|
|
|
with final values.
This means redo panel of matching operators would not get correct values set in case
those were entered with numinput, or some snapping was used...
|
|
Skipped devices did not reflect in the device number, which might result in bad
array indices.
This might also resolve T45037, and need to be ported to a release branch.
|
|
- would hang on win32 (checking network share?)
- made the path absolute on all systems
|
|
|
|
We _never_ want this, so better not fail silently.
|
|
|
|
|
|
Reduces issues with vars leaking into the parent scope.
|
|
|
|
avoid sqrt
|
|
|
|
|
|
We really don't need to iterate all edges of the mesh every frame to
search for loose edges, this calculation can be cached when filling the
edge index buffer.
|
|
after the current frame
This behaviour was confusing, since "selected keyframes" suggests that it covers
all selected keyframes (instead of trying to do this based on frame ranges).
|
