Blender Git Commit Log

Depsgraph: Use explicit parameters eval operation code

This replaces usage of generic PLACEHOLDEWR with string lookup with more
explicit opcode. This should make it faster to build dependency graph by
avoiding string comparisons when it's not needed.

There should be no user measurable different.

Depsgraph: Cleanup, use proper style for macro loop

Depsgraph: Remove unsued node flag

Depsgraph: Make operation codes more obvious

This synchronizes al lrelated changes from blender2.8 branch.

Depsgraph: Remove bunch of debug code

Was never actually used and implementation seems to be slow: we shouldn't be
doing per-node evaluation hash lookups, adds too much overhead. We can instead
store statistics in the node itself, and maybe even group them somehow.

Ideally such a statistics should be user-friendly so riggers and animators
can see exactly what's happening.

Fix T53004: XWayland ignores cursor-warp calls

There is currently a limitation in XWayland,
the cursor needs to be hidden during warp calls.

Eevee: Fix T53095: Black cube on start and no material updates

This was caused by a not bound unused texture. Removing the texture usage fixes the problem.

Merge branch 'master' into blender2.8

Merge branch 'blender2.8' into greasepencil-object

Fix one more assert being triggered due to recent changes.

Code refactor: remove MEM_WRITE_ONLY, always use MEM_READ_WRITE.

It's unlikely the driver can do useful optimizations with this, and if
we sum multiple samples we are reading from the memory anyway.

Merge branch 'blender2.8' into topbar

openvdb changes for manta support

customization for obstacle grid to match mantaflow flags grid

Silence warning in outliner_id_remap_exec

changes for quick smoke cycles node setup and minor bug fixes

with quick smoke, the cycles setup for fire was unreachable (why?) -> removed the if-clause. also fixed minor bugs (UI Quick Liquid, copy settings for effector object)

Merge branch 'blender2.8' into greasepencil-object

Fix memory leak in GPU

The problem was the flag was not checked and in some situations this avoided the batch clear.

Fix crash changing settings of operator executed in different scene

Steps to reproduce were:
* Open Blender, create a new scene
* Go back to initial scene, transform object
* Switch back to newly created scene, change operator settings there
* Should cause a crash (at least with asan)

Should behave like 2.7 now, that is, switch scene back to where
operator was executed.

Solve context issues when tweaking operator settings from top-bar

E.g. editing settings after transforming in 3D View would print
warnings, or in Movie Clip Editor wouldn't work at all.

We now store the area & region an operator was executed in and restore
it temporarily when redoing.
Ideally operators wouldn't depend on screen context for event-less
execution (exec callback), but we're far from that.

Remove operator redo panel from clip editor