Appending object/material that references scene property imports whole scene #108047

New Issue

slowburn · 2023-05-18T14:49:42+02:00

slowburn commented

2023-05-18 14:49:42 +02:00

System Information
Operating system: Windows-10-10.0.19045-SP0 64 Bits
Graphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79

Blender Version
Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: e1ccd9d4a1d3

Short description of error
Appending or copying object or material from another .blend file, that is somehow referencing custom scene property, also imports that scene with all objects in it.
I've attached an example file with a material that is using custom scene property as a driver for a value input.

Exact steps for others to reproduce the error

Create a new Blender project.
Append a single object or material from the provided file.
Or use Copy Object command to copy/paste it into another project.
A new scene will be created with multiple objects in it.

**System Information** Operating system: Windows-10-10.0.19045-SP0 64 Bits Graphics card: NVIDIA GeForce RTX 3060 Ti/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 531.79 **Blender Version** Broken: version: 3.5.1, branch: blender-v3.5-release, commit date: 2023-04-24 18:11, hash: `e1ccd9d4a1d3` **Short description of error** Appending or copying object or material from another .blend file, that is somehow referencing custom scene property, also imports that scene with all objects in it. I've attached an example file with a material that is using custom scene property as a driver for a value input. **Exact steps for others to reproduce the error** 1. Create a new Blender project. 2. Append a single object or material from the provided file. 3. Or use Copy Object command to copy/paste it into another project. 4. A new scene will be created with multiple objects in it.

append bug.blend

1.1 MiB

👀 1

slowburn added the

labels 2023-05-18 14:49:43 +02:00

Pratik Borhade commented

2023-05-18 17:57:19 +02:00

Hi, thanks for the report. Can confirm when appending/copying object that has scene reference in driver.

Pratik Borhade added

and removed

labels 2023-05-18 17:57:39 +02:00

Philipp Oeser commented

2023-05-19 14:35:49 +02:00

Dont think this will be considered a bug.
If there is a reference to the scene, it has to be pulled in as well.
What would be the alternative? Have the driver "break"?
(dont think the current state is fine-grained enough to analyze a driver "in depth" to see what exactly it needs to pull in, but havent checked details)

CC @dr.sybren
CC @mont29

Dont think this will be considered a bug. If there is a reference to the scene, it has to be pulled in as well. What would be the alternative? Have the driver "break"? (dont think the current state is fine-grained enough to analyze a driver "in depth" to see what exactly it needs to pull in, but havent checked details) CC @dr.sybren CC @mont29

Bastien Montagne commented

2023-05-19 15:06:59 +02:00

This is indeed expected behavior, no bug here.

Bastien Montagne closed this issue

2023-05-19 15:07:01 +02:00

Blender Bot added

and removed

labels 2023-05-19 15:07:03 +02:00

slowburn commented

2023-05-19 17:01:48 +02:00

I don't understand the reasoning here. If a material is referencing a scene property, what's the point of importing entire scene with ALL of its objects (which are unrelated)? This is a terrible workflow and also very confusing for the user. It took me quite a while to figure out why I can't append this one object, until I noticed that there are 10 extra scenes and 50000 objects hidden away in a seemingly empty blend file.
Logical solution would be to copy the property into the new scene. If that's not possible for some reason then breaking the driver would be 100x better than current behaviour.

I don't understand the reasoning here. If a material is referencing a scene property, what's the point of importing entire scene with ALL of its objects (which are unrelated)? This is a terrible workflow and also very confusing for the user. It took me quite a while to figure out why I can't append this one object, until I noticed that there are 10 extra scenes and 50000 objects hidden away in a seemingly empty blend file. Logical solution would be to copy the property into the new scene. If that's not possible for some reason then breaking the driver would be 100x better than current behaviour.

Bastien Montagne commented

2023-05-22 10:59:49 +02:00

If you do not want to bring in a scene, do not create dependencies to this scene.

The whole point of the linking process is that you get what you link and all its dependencies. This behavior is a fundamental trait of Blender data design since it's very beginning, and Scene are among the 'highest level' type of data-blocks (they 'contain' almost all other type of data).

If you do not want to bring in a scene, do not create dependencies to this scene. The whole point of the linking process is that you get what you link and **all** its dependencies. This behavior is a fundamental trait of Blender data design since it's very beginning, and Scene are among the 'highest level' type of data-blocks (they 'contain' almost all other type of data).

Philipp Oeser commented

2023-05-22 11:33:45 +02:00

So I think (in the case of this report), instead of having custom properties on the scene (to control "scene-wide" stuff on other obects/materials etc. in drivers), it would be better to have a more isolated "controller object" that holds these properties? That way only those get pulled in when appending (and not a whole scene..)

So I _think_ (in the case of this report), instead of having custom properties on the **scene** (to control "scene-wide" stuff on other obects/materials etc. in drivers), it would be better to have a more isolated "controller object" that holds these properties? That way only those get pulled in when appending (and not a whole scene..)

Pratik Borhade referenced this issue

2023-07-18 06:00:57 +02:00

Importing node with context variable driver imports entire scene. #110207

Iliya Katushenock referenced this issue

2023-12-17 00:21:13 +01:00

Node Assets that have driver with active scene context property are importing entire scene from asset source file #116259

Nika Kutsniashvili commented

2023-12-17 00:24:35 +01:00

I think, to reopen the discussion hopefully, that if driver is referencing to scene property by Scene ID it should import the scene, but if its referencing it by "Active Scene" context property, it should work on active scene of file in which it was added, and not import the scene.

That makes sense to me. I understand why it needs to import scene when you're referencing Scene ID, but when I set it to "Active Scene", I'm expecting it to work on active scene on any blend file, not of source file.

I think, to reopen the discussion hopefully, that if driver is referencing to scene property by Scene ID it should import the scene, but if its referencing it by "Active Scene" context property, it should work on active scene of file in which it was added, and not import the scene. That makes sense to me. I understand why it needs to import scene when you're referencing Scene ID, but when I set it to "Active Scene", I'm expecting it to work on active scene on any blend file, not of source file.

Bastien Montagne commented

2023-12-17 23:06:02 +01:00

@nickberckley Not fully sure, but is the 'Active Scene' actually bringing in any scene? I would not expect it to do so (unless you already linked a scene in the 'Single Property' mode, before switching to the 'Context Property' one).

Nika Kutsniashvili commented

2023-12-18 10:55:17 +01:00

@mont29 You're right I first set it to Single Property and then switched it to Context Property. When I set it up with Context Property first it works as expected and Active Scene isn't importing anything.

Would you consider it a bug that changing Single Property to Context Property doesn't clear ID?

@mont29 You're right I first set it to Single Property and then switched it to Context Property. When I set it up with Context Property first it works as expected and Active Scene isn't importing anything. Would you consider it a bug that changing Single Property to Context Property doesn't clear ID?

Bastien Montagne commented

2023-12-18 11:03:02 +01:00

No... Although it can be confusing in some cases, most of the time you do not want to reset settings when switching to another 'mode', even if they become unused then.

And linking code has no way to know whether a property is actually used or not. So am afraid it's up to the user to keep things clean here. :)

No... Although it can be confusing in some cases, most of the time you do not want to reset settings when switching to another 'mode', even if they become unused then. And linking code has no way to know whether a property is actually used or not. So am afraid it's up to the user to keep things clean here. :)

👍 1

slowburn commented

2023-12-18 23:43:14 +01:00

@nickberckley

When I set it up with Context Property first it works as expected and Active Scene isn't importing anything.

How can I setup a driver to reference Active Scene? I don't see such option in the drivers editor.

@nickberckley > When I set it up with Context Property first it works as expected and Active Scene isn't importing anything. How can I setup a driver to reference Active Scene? I don't see such option in the drivers editor.

Nika Kutsniashvili commented

2023-12-18 23:56:15 +01:00

@slowburn

![image](/attachments/fa59e079-9041-4754-843f-5482f8cf722b) @slowburn

image.png

36 KiB

👍 1

Sign in to join this conversation.