| Age | Commit message (Collapse) | Author |
|---|
|
|
|
This reverts commit b5bd39b5182590fd4d5ddb24d7b7bdbe714d57bf.
This is problematic because it means minor differences in system headers can cause errors
(glew in this case errored for me both with system and Blender's bundled version).
Developers can enable -Werror=* locally for warnings that aren't reliable across different systems.
|
|
This reverts commit 75cfc81ec39ac9953f25eb0ae5f9e70d3c24ee7e.
|
|
This is how the old code used to initialize it. Current value was
failing big time when baking all caches (always set to MAXFRAME), and it
was added right before commit to quiet a warning... (I know, I know...)
|
|
Reviewers: brecht
Differential Revision: https://developer.blender.org/D1732
|
|
Reviewers: brecht
Differential Revision: https://developer.blender.org/D1731
|
|
|
|
|
|
This is the second time at least that kind of stuff slips in during one of my refactor,
a mere warning here is really not enough (too easy to miss it)!
|
|
Issue was with very thin domains along one or two axes, these could lead to simulation
with only one cell width - and smoke code assumes we have at least 4 cells in each direction.
So now, we clamp resolution to a minimum of 4 in smoke_set_domain_from_derivedmesh().
Note: in extreme cases like this report, this will generate very un-cubic cells,
check it still works OK in 3DView is needed here.
Thanks to @genscher and @kevindietrich for help on this issue. :)
|
|
|
|
have it.
|
|
Curse gcc for not erroring by default on passing wrong func pointers... :/
|
|
|
|
We didn't switch to OSL-1.6.9 on all platforms yet,
so please keep codeabse compiled with 1.5 for the
time being.
|
|
|
|
Based on usages so far:
- Split callback worker func in two, 'basic' and 'extended' versions. The former goes back
to the simplest verion, while the later keeps the 'userdata_chunk', and gets the thread_id too.
- Add use_threading to simple BLI_task_parallel_range(), turns out we need this pretty much systematically,
and allows to get rid of most usages of BLI_task_parallel_range_ex().
- Now BLI_task_parallel_range() expects 'basic' version of callback, while BLI_task_parallel_range_ex()
expectes 'extended' version of the callback.
All in all, this should make common usage of BLI_task_parallel_range simpler (less verbose), and add
access to advanced callback to thread id, which is mandatory in some (future) cases.
|
|
|
|
settings".
Our RenderSettings struct may have a bit too much levels, makes it hard to track
all 'pointer' data during copy...
Fixed several issues here, but not sure I found all existing ones. :/
|
|
Displacement shader was not updating motion vertex positions.
Current solution is not totally correct because it applies same offset
for all time steps. Ideally we'll need to evaluate displacement shader
for every time offset separately, but currently we don't have subframe
image access.
For the time being will consider this a TODO.
|
|
|
|
- tighter scoping
- declare closer to use
- struct initializers
- bool vs int
|
|
- vectorscope grid
- color ramp handles
- box shadows (image file preview)
|
|
so that all points here are drawn between one Begin/End pair.
|
|
I put all usage of GL_POINTS under the microscope. Fixed problems &
optimized a couple of spots.
- reduce calls to glPointSize by about 50%
- draw selected & unselected vertices together for UV editor & EditMesh
- draw initial gpencil stroke point the proper size
- a few other smaller fixes
New policy: each GL_POINTS draw call needs to set its desired point
size. This eliminates half our calls to glPointSize (setting it back to
its 1.0 default after every draw).
|
|
|
|
|
|
Note this doesn't expose the option to the interface,
it just means scripts that set the subframe can render (as with Cycles).
|
|
|
|
Compiling OSL scripts with errors in them would cause Blender to crash since the OSL version
bump to 1.6.9 instead of printing the error to the console as it did before.
With version 1.6.2, OSL added a pointer to an OpenImageIO ErrorHandler as an argument to the
OSLCompiler constructor. However, since it defaults to the NULL pointer, Blender still compiled
fine after the OSL version bump.
It turns out, though, that this pointer is used without further checks inside the OSL code, which
makes it crash when it tries to report an error unless a valid ErrorHandler pointer is specified.
Therefore, this commit simply passes a pointer to the static default handler that OIIO offers,
which prints the error to the console just like OSL did before.
Using this feature for a more advanced error handling and displaying from the Blender side would
be possible and seems reasonable, but for now it's not really relevant for fixing this bug.
|
|
The combined pass is built with the contributions the user finds fit.
It is useful for lightmap baking, as well as non-view dependent effects
baking.
The manual will be updated once we get closer to the 2.77 release.
Meanwhile the new page can be found here:
http://dalaifelinto.com/blender-manual/render/cycles/baking.html
Reviewers: sergey, brecht
Differential Revision: https://developer.blender.org/D1674
|
|
|
|
- Only do this if PBVH is not used for display, this should correspond
to whats' happening in sculpt.c now.
- No need to do such synchronization for solid drawing, it supports
optimal display from PBVH.
In fact, such synchronization is only needed in the following case:
Drawing callback does not support PBVH draw and sculpt session is
configured to use PBVH for display and related operations.
|
|
Also made threshold aware of zoom, so now it's always 12px threshold
regardless of how much you're zoomed in.
|
|
The file started to be rather really huge and difficult to follow.
Should be no functional changes.
|
|
Should be no functional changes.
|
|
|
|
Previously it was simplier logic which only checked whether the mouse
is inside of some area around sliding zone, which was resulting in
wrong sliding zone used when zoomed out.
|
|
X11 property access was using wrong sized types that only worked for little endian systems.
|
|
Also refactor context backup/restore into functions.
|
|
924c626 broke loading on systems with different endian.
We could support reading values from SDNA, it isn't really worth the extra hassle.
Long support is still removed, just keep enum values the same.
|
|
|
|
|
|
|
|
|
|
|
|
Some py devs are way too smart for our own good... :P
|
|
|
|
|
|
|
