| Age | Commit message (Collapse) | Author |
|---|
|
Fix asan error.
|
|
Was using function for edge rotation which was doing unnecessary checks
Use the face normal and BLI_polyfill_beautify_quad_rotate_calc directly.
|
|
Needed for 3D iterative edge-rotation to avoid flipping when projected
from different angles,
but could keep zero area faces in 2D polygons.
|
|
|
|
|
|
|
|
Was intersecting same triangle twice.
|
|
Portable builds LOCAL files need to be
treated as system instead of using as a fallback to USER templates.
|
|
Would return the test path for developer builds:
{blender-dirname/release}
Now return an empty string when no path is found.
|
|
Use more watertight and robust intersection test.
It uses now ray to triangle intersection, but it's all fine because segment was
covering the whole bounding box anyway.
|
|
Use same 5 digits precision as we already use for e.g. Object's
location, for Object's dimensions too.
To be backported to 2.79a, should we do it.
|
|
Mainly when object origin is not at the geometry bounding box center.
Seems to be straightforward to fix, hopefully it doesn't break some obscure case
where this was a desired behavior.
|
|
|
|
|
|
The issue here was that removing datablock from main database will poke editors
update, which includes buttons context to free users of texture. Since Cycles
will free datablocks from job thread, it might crash Blender since main thread
might be in the middle of drawing.
Solved by exposing extra arguments to bpy.data.foo.remove() which indicates
whether we want to perform ID user count and interface updates. While scripts
shouldn't be using those normally, this is the only way to allow Cycles to skip
interface update when removing datablock.
Reviewers: mont29
Reviewed By: mont29
Differential Revision: https://developer.blender.org/D2840
|
|
the same name
The issue was caused by render result identifier only consist of scene name,
which could indeed cause conflicts.
On the one hand, there are quite some areas in Blender where we need identifier
to be unique to properly address things. Usually this is required for sub-data
of IDs, like bones. On another hand, it's not that hard to support this
particular case and avoid possible frustration.
The idea is, we add library name to render identifier for linked scenes. We use
library name and not pointer so we preserve render results through undo stack.
Reviewers: campbellbarton, mont29, brecht
Reviewed By: mont29
Differential Revision: https://developer.blender.org/D2836
|
|
|
|
|
|
|
|
This way we can easily re-use bits of code for new dependency graph.
Currently should be no functional changes.
|
|
Affects both "normal" open as a video file and thumbnail generation.
|
|
callbacks, leading to crash.
Related to (exposed by) T52735, fixes the reported crash but not the
underlying issue.
To be backported to 2.79a should we do one.
|
|
|
|
|
|
|
|
This means boolean tessellation wont match viewport tessellation
however it's needed to avoid zero area triangles causing problems.
|
|
|
|
This way we dont rely on the static array of chars that was causing T52385.
That fixes T52385.
|
|
|
|
With new style drawing hotspot should be in the middle of the border,
not inside it.
|
|
|
|
Doesn't rely on hovering, more consistent with 2D drawing tools.
|
|
A version of circle drawing for non 1:1 aspects
|
|
|
|
I forgot the reset the toggle after rendering the probes...
|
|
|
|
Add sanitizer. I wanted to stay away from this because I think we should fix what causes NaNs in the first place. But there can be too much different factor causing NaNs and it can be because of user inputs.
|
|
Avoid ambiguity between 2d/3d (which were already named).
|
|
|
|
This should get rid of the leak once for all.
|
|
|
|
|
|
Was caused by numeric overflow when calculating preview dimensions.
Now we try to avoid really insance preview resolutions by fitting
aspect into square.
|
|
The branching introduced by the uniform caused problems on mesa + AMD in the resolve stage.
This patch create one shader per sample count without branching.
This improves performance of a single ray per pixel case (3.0ms against 3.6ms in my testing)
|
|
|
|
|
|
|
|
Benchmarks peformance on GTX 1080 and RX 480 on Linux is the same for
bmw27, classroom, pabellon, and about 2% faster on fishy_cat and koro.
|
|
|
|
The issue was caused by operator redo which frees all object's evaluated data,
including bounding box. This bounding box can not be reconstructed properly
without full curve evaluation (need to at least convert font to nurbs, which is
not cheap already).
|
