Blender Git Commit Log

Eevee: Expose Shadow filter size.

Eevee: Add Variance Shadow Mapping

This is an alternative to ESM. It does not suffer the same bleeding artifacts.

Eevee: Shadows: Add UI buttons for size and method

Only one method is available right now. VSM and PCF are comming.

Eevee: Refactor Shadow System

- Use only one 2d texture array to store all shadowmaps.
- Allow to change shadow maps resolution.
- Do not output radial distance when rendering shadowmaps. This will allow fast rendering of shadowmaps when we will drop the use of geometry shaders.

Apply lattice modifer in each frame

The lattice must be evaluated in each frame, not in the location of the first frame only.

Resolve T52687: Add node label shows as 'Unknown'

Add type access method, need to extend to other types
for now just get node UI working properly again.

PyAPI: Fix mathutils freeze allowing owned data

Docs: mathutils docstrings

Cleanup: mathutils vector comments

Use doxy markup & correct outdated info.

Correct last commit

Cleanup: Simplify SWIZZLE macro

- Use indices instead of character args.
- Use numbered macros instead of variadic args.

Parsing using rtags used over 11gb of memory. While this should be
resolved upstream (report as #1053), the extra complexity didn't give
any real advantage.

Expose scene > engine in the UI (render panel)

Use workspace -> engine in the opengl render

Use workspace -> engine in the viewport

Not yet for OpenGL render.

Collection Panel: Get mode from workspace

Those overrides will change, and this panel may not exist in the future.
But meanwhile let's make things work as tey were supposed to.

Context: Expose "engine" for Python and add BKE_render_engine_get()

Properties Editor: Add Workspace and organize context path

We now have the properties of:

Scene, Scene > Layer, Scene > World, Workspace

[Scene | Workspace] > Render Layer > Object
[Scene | Workspace] > Render Layer > Object > Data
(...)

We use Scene or Workspace depending on workspace.use_scene_settings.

Also, we no longer expose the object in the collection context.
Since this should go away (and at the very least we should get the mode
from the workspace).

[msvc/make.bat] mention the msvc-2017 option in the make.bat help text.

Workspace: Add (render) engines

We still need to change the viewport so it uses this instead of scene.rd.engine.

Workspace: SETLOOPER should get render layer from workspace

Right now we are still passing NULL instead of the workspace in most of
those cases. That shouldn't matter much since this will simply bring
back the previous behaviour.

Also, most of those calls (gpu_material.c, view3d_draw_legacy.c,
render_internal.c) are from deprecated areas of Blender anyways.

The areas that will need to be addressed are:
* physics (collision.c)
* particles (pointcache.c)
* sound (sound.c)

And of course:
* game engine (BL_BlenderDataCoversion.cpp)

It's not clear to me, however, why some of those areas are using the
SET_LOOPER in the first place. SET_LOOPER acts on top of bases so we
want to iterate over the SceneLayer objects, not all of scene ones.

However in some cases it seems that the original design was expecting to
loop over all the objects (+ the set objects).