| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
Caused by ca8f787349dcdf5. This issue is in master actually. Fixing it there
would cause conflicts so won't do that unless needed ;)
Steps to recreate were:
* Split properties editor into two (default startup.blend)
* Move both properties editors to the bottom, so only their headers are visible
* Move the upper edge of the upper properties editor up and down
Although it doesn't happen everytime, you may see the edge between the timeline
and the 3D view move, while the region drawing doesn't update.
What happened is area edge snapping allowed to snap the edge outside of window
bounds (we snap to a 4px grid by default), which screen_vertices_scale
interpreted as window scaling and thus run area size updates.
|
|
|
|
This feature is better handled by specialized tools.
|
|
Referring to ca8f787349dcdf5. Thought in this case the simple `+ 1` would be
correct, but we need to make the same pixel adjustment as we do in other places.
|
|
Simply moving the properties editor of the default startup.blend all the way to
the bottom could trigger this. Calculating limits for area edge moving would use
screen bounds instead of entire window bounds (screen + global bars).
Added assert that should help debugging further issues like this.
|
|
There are more related glitches for which I have fixes. Will test them some more
and push in a followup commit.
|
|
This is consistent with the 3D view.
|
|
introduced by rBd2757d149bf2d9ac604da6fb7f4742ee77e68d2d
|
|
This puts the wireframe on top of the weight in weight paint mode,
sculpt mode ...
Wireframe should be colored differently if the object is in paint mode
but it's not there yet.
|
|
|
|
None of those calls actually passed a DerivedMesh.
|
|
Differential Revision: https://developer.blender.org/D3510
|
|
Unbuffered stdout makes stdout and stderr better synchronised, and helps
when stepping through code in a debugger (prints are immediately
visible). We don't output much to stdout anyway, so this isn't likely to
cause any performance issues.
|
|
|
|
- TAA is also enabled for Forward rendering
- Uses less GPU memory (removed one history buffer)
- TAA is done after the color management
- consolidated the aa code between forward and deferred rendering
(workbench_effects_aa.c)
|
|
|
|
Collection IDs.
Was kind of a PITA to get working, but simple tests seem to pass well...
|
|
I.e. we can now use REPLACE operation directly on items of an RNA
collection, when those items are ID pointers.
Again, mandatory to support new Collection's objects/children override.
|
|
This is unused currently, but is mandatory for incomming support to
Collections objects and children items override support.
|
|
|
|
|
|
To prevent the pointcache from being copied-on-write too (and requiring
copying back), the cache is now shared between the original and
evaluated scenes. Reading from the cache is always allowed; running the
sim and writing to the cache is only allowed when the depsgraph is
active.
Some pointers have moved from RigidBodyWorld (RBO) to
RigidBodyWorldShared (RBOS). writefile.c copies some pointers back from
RBOS to RBO so that the file can still be opened on older Blenders
without crashing on a segfault.
The RigidBodyWorldShared struct is written to the blend file, because it
refers to the PointCache ID block.
The RigidObjectShared struct is runtime-only, and thus not saved to the
blend file.
An RNA getter-function is used to hide the new 'shared' pointer. As a
result the Python API hasn't changed.
Reviewed by: campbellbarton
Differential Revision: https://developer.blender.org/D3508
|
|
|
|
Key shortcuts and explanation about how to use the tool should go to the
status bar, but other info can in the header so it's near where the user
is working. This distinction has not been made yet for all operators.
|
|
This prevents it from disappearing when the blend file is saved.
|
|
|
|
Keymaps were used to check which tool was active.
|
|
This will be much useful in some cases, at least in override area it is
needed (avoids searching again for the overriden item in a collection).
|
|
|
|
|
|
Regression from undo system upgrade.
|
|
Following RNA pointer way - only return evaluated item if asked for.
|
|
When RNA path was for a collection item, we'd falsly get NULL final
property (and wrong final RNA pointer too).
Own stupid mistake in some previous commit, iirc.
|
|
Note that this commit also fixes serious memory leaks, temp Mesh
generated out of Main from the DM were never freed here!
|
|
|
|
|
|
The preview files had all the other collections excluded from the view layer.
Although this fix the problem, it probably means we ignored some existing
2.8 files in recent changes. Which is likely fine anyways given that 2.8 is
experimental.
|
|
|
|
|
|
Assert from BLI_assert by default in debug builds
(instead of just printing a warning).
Some developers ignored this, causing errors for others.
Better debug builds cause hard error so code isn't ignored.
Disabling is still useful when bisecting or testing outdated code.
|
|
Use less space for sign used when we don't have enough.
|
|
When meshes has no uv layer, but has a texture assigned there was a uv
layer allocated which was corrupt. When no uv layer is available now
there won't be a vbo created. This might impact performance as the draw
cache does not cache this result.
|
|
Current implementation works with at most of 3 layers, but was not
checked during hair drawing leading to reading from uninitialized
memory.
This commit limits it to the number of layers that is used during
compilation of blender.
|
|
only hash the texture if it exists. Really minor improvement
|
|
Based on animator feedback, accidentally not clicking on the manipulator
handle had unpredictable behavior.
This functionality will be moved into the manipulator and made optional
(add an invisible fallback manipulator).
|
|
textures were not always drawn as the material did not always include
the image in the hash. Not sure if this will solve all cases, but it
definitely works better with this change.
|
|
|
|
|
