Fix Split node in full-frame compositor when no inputs are connected #117282
Closed
Sergey Sharybin
wants to merge 1 commits from
When changing the target branch, be careful to rebase the branch in your fork to match. See documentation.
Sergey:compositor_fix_split_node into main
pull from: Sergey:compositor_fix_split_node
merge into: blender:main
blender:main
blender:blender-v3.6-release
blender:blender-v3.3-release
blender:universal-scene-description
blender:brush-assets-project
blender:partial-write-refactor
blender:blender-v4.1-release
blender:blender-v3.6-temp_wmoss_animrig_public
blender:temp-sculpt-dyntopo
blender:gpencil-next
blender:anim/animation-id-113594
blender:blender-v4.0-release
blender:blender-projects-basics
blender:bridge-curves
blender:sculpt-blender
blender:asset-browser-frontend-split
blender:asset-shelf
blender:tmp-usd-python-mtl
blender:tmp-usd-3.6
blender:blender-v3.5-release
blender:blender-v2.93-release
blender:realtime-clock
blender:sculpt-dev
blender:bevelv2
blender:xr-dev
When changing the target branch, be careful to rebase the branch in your fork to match. See documentation.
1 Commits
| Author | SHA1 | Message | Date |
|---|---|---|---|
 Sergey Sharybin
|
2af4c291fd |
Fix Split node in full-frame compositor when no inputs are connected
Not having inputs connected triggers the constant folding code paths in the operation builder, which attempts to convert the operation to a constant memory buffer. This happens before the canvas of the node is known, and the expected result in area of 1x1 pixels. The split node can not be constant-folded in such way without causing regression compared to the tiled compositor: for unconnected inputs the node is expected to use the output resolution as canvas. IN theory the node can be constant folded if the split percentage is 0 or 1, but there is no mechanism which allows such option-dependent constant folding check. This fixes node_split_unlinked.blend regression test which fails when full-frame compositor is used by default. |