The compositor in an another scene is tiggered when geometry modifications are done in the main scene. #114648

New Issue

kursad k · 2023-11-09T00:20:20+01:00

kursad k commented

2023-11-09 00:20:20 +01:00

System Information
Operating system: Win 11
Graphics card: RTX 207

Blender Version
Broken: 869372ffc3

Short description of error

Making modifications in one scene triggers updates in the compositor of another scene, if the view layer is added as a node. In theory the compositor should be calculated or triggered only after a real rendering or in the actual compositor, that does not seem to be case here. Please see the video where I stacked two scenes on top of each other by utilizing having both scenes open via opening the other scene in another main window.

The compositor should not be triggered given the realtime GPU is not enabled either in the viewports. This triggering seems to happen with the tiled and the fullframe compositors. This issue becomes a real performans killer in actual heavier production scenes. The only solution I found is to disable all the compositors everywhere in all scenes.

Exact steps for others to reproduce the error
load the attached scene

make sure you can see both of the scene (scene and comp) updates

play with the merge distance value in the geometry nodes graph

watch the updates in the other

**System Information** Operating system: Win 11 Graphics card: RTX 207 **Blender Version** Broken: 869372ffc335 **Short description of error** Making modifications in one scene triggers updates in the compositor of another scene, if the view layer is added as a node. In theory the compositor should be calculated or triggered only after a real rendering or in the actual compositor, that does not seem to be case here. Please see the video where I stacked two scenes on top of each other by utilizing having both scenes open via opening the other scene in another main window. The compositor should not be triggered given the realtime GPU is not enabled either in the viewports. This triggering seems to happen with the tiled and the fullframe compositors. This issue becomes a real performans killer in actual heavier production scenes. The only solution I found is to disable all the compositors everywhere in all scenes. <video src="/attachments/c96c8e0d-838b-4e1a-be18-36ba994abe73" title="blender_DEHCz5w2PK.mp4" controls></video> **Exact steps for others to reproduce the error** load the attached scene make sure you can see both of the scene (scene and comp) updates play with the merge distance value in the geometry nodes graph watch the updates in the other

bug_08112023_1714_29.zip

345 KiB

blender_DEHCz5w2PK.mp4

4.0 MiB

kursad k added the

labels 2023-11-09 00:20:21 +01:00

kursad k changed title from ~~The compositor in an another scene is tiggered when modificationsa are done in the main scene~~ to The compositor in an another scene is tiggered when geometry modifications are done in the main scene.

2023-11-09 00:23:55 +01:00

Iliya Katushenock added the

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

The compositor in an another scene is tiggered when geometry modifications are done in the main scene. #114648