Blender Git Commit Log

remove outdated code

Lineart: loading

Fix T88666: Cryptomatte: EXR sequence does not update when scrubbing the timeline.

Cause is that initializing the cryptomatte session would reset the
current frame of an image sequence. The solution is to always use the
scene current frame so it resets to the correct frame.

This was a todo that wasn't solved after it landed in master.
Needs to be backported to 2.93.

EEVEE: LightProbe: Finish loading and rendering of lightcache

Starting to port lightcache.c to c++.

recalc when viewer node changed

take viewer node into account when searching for output connection

compute viewed sockets even when it is not required for the output

Fix animation conversion in versioning

Animation in X and Y channels used `scene->r.xsch` as scene size, which
resulted in incorrect conversion for Y channel.

Merge branch 'master' into temp-vse-fix-T88263

remove toggles from node headers

handle viewer node in modifier

update spreadsheet context when activating viewer

initial viewer node

Fix (unreported): TextureOperation inputs have no resolution

When compositor node tree has a texture node, TextureOperation vector inputs has always {0, 0} resolution instead of having same resolution as TextureOperation which is the expected behaviour for resolutions propagation.

Current TextureOperation determineResolution implementation doesn't determine inputs resolution, breaking propagation of preferred resolution and that's the reason why they are always 0. Setting scene resolution always would mean it is its own resolution and could make sense, but setting it only when preferred resolution is 0, breaks preferred resolution logic affecting other operations as explained in D10972. In any case scene resolution is already the default preferred resolution on viewer and compositor nodes.

Reviewed By: jbakker

Differential Revision: https://developer.blender.org/D11381

Merge branch 'blender-v2.93-release'

add node to access iteration index

Fix T88623, T87044: Make encoded videos play correctly in VLC

The issue was two fold. We didn't properly:

1. Initialize the codec default values which would lead to VLC
complaining because of garbage/wrong codec settings.

2.Calculate the time base for the video. FFmpeg would happily accept
this but VLC seems to assume the time base value is at least somewhat
correct and couldn't properly display the frames as the internal time
base was huge. We are talking about 90k ticks (tbn) for one second of
video!

This patch initializes all codecs to use their default values and fixes
the time base calculation so it follows the guidelines from ffmpeg.

Reviewed By: Sergey, Richard Antalik

Differential Revision: https://developer.blender.org/D11426

Fix (studio-reported) crash in collection management code.

Code checking for potential collection loop dependencies can be called
in cases where we cannot guarantee that there is no NULL pointers, so we
need to check those. Was already done for objects.

NOTE: doubled-checked by @jbakker, thanks.

Revert "Added v2.93 pipeline config for new buildbot."

This reverts commit 632bfee0a5ea92d213b5c9d010483c16f0baa636.
This config is only intended for 2.93. Master will get its own config
file after testing that 2.93 is correct.

Merge branch 'blender-v2.93-release'