2
$\begingroup$

I'm using blender 2.83 beta and I'm in the middle of a nightmare with a blender project that is randomly considering my scenes as 0 users datablocks.

It gives a red background on the scene name and a 0 on the left if I open the scenes list.

I didn't even know a scene can have 0 users, but I don't even see a fake user option so...

I'm using the 2.83 beta (updating to the today's version didn't help) on windows 10. I temporarily solved the problem by creating a full copy of every scene (all the scene were actually full copies of the master one) as backup.

Is this a feature? Is this a bug?

Improve this question
$\endgroup$
5
  • $\begingroup$ Hey :). I'm aware this is not a solution - but 2.83 is still beta. Wouldn't 2.82 work better? $\endgroup$ – Jachym Michal May 2 '20 at 16:07
  • $\begingroup$ @JachymMichal I tried to open the project on blender 2.82a but the problem persists. $\endgroup$ – Riccardo Fasoli May 2 '20 at 16:20
  • $\begingroup$ Oh, that's interesting :). Would you mind sharing the file? Just an empty .blend copy should do. $\endgroup$ – Jachym Michal May 2 '20 at 16:27
  • 1
    $\begingroup$ oh well it's a 2GB blender project and the problem seems to jump out quite randomly. try to make a couple of full copies of the default scene, should be enought... then play a bit with everyone and at some point you should notice that from the scenes list there's the issue $\endgroup$ – Riccardo Fasoli May 2 '20 at 19:02
  • $\begingroup$ @JachymMichal Can create a zero user scene via C.window.scene = C.scene.copy() in the python console. $\endgroup$ – batFINGER May 20 '20 at 17:34
4
$\begingroup$

Edit 2: the bug has been fixed on Blender side - so if you try the latest 2.83 beta build, you shouldn't have this issue anymore.

Having the same issue and from my tests it seems related to the new undo system introduced in 2.83 beta. Scenes can (randomly?) see their user count drop to 0 after an undo operation. Saving and re-opening the file temporarily fix that, but next undo may have the same effect.
It can become harmful if you use the "Purge All" action to clean orphan data, because those 0-user scenes will be considered as such and therefore deleted.

Edit: I've reported this issue here.

It does not happen (at least in my tests) when using "Undo Legacy".

  1. Preferences > Interface > Developer Extras
  2. Preferences > Experimental > Undo Legacy

Activate Undo Legacy

Improve this answer
$\endgroup$
1
  • $\begingroup$ On behalf of future 2.83 users, Thank you! :) $\endgroup$ – Jachym Michal May 20 '20 at 20:12
2
$\begingroup$

I ran into the same problem, and I would also be very interested in the reason to why this is happening (I assume it's a bug...)

I found a solution to add a fake user though!

In the Outliner, switch to "Orphan Data", and open the "Scenes" folder. There you'll see all your "orphan" scenes listed:

orphan scenes

Now simply click the X next to 0 and it will add a fake user:

scenes with fake user

It works properly, but it's a bit annoying because now all your scenes have this F right next to it in the Scenes dropdown:

enter image description here

Improve this answer
$\endgroup$
2
$\begingroup$

I had this problem while creating a Grease Pencil animation.

When you rename scenes that have been previously created (or previously added into the sequencer) you will get a red shaded scene name with zero users (this is what causes the error). Against all logic I took the scene out of the sequencer. Renamed the scene like it was before. Saved, closed and opened Blender again, and when the scene was in normal color again, I re-added it back to the sequencer.

I had another case where I would rename a sequence, it will go red shaded on the Scene list and I will not remove it from the sequencer. Saved, closed and opened Blender, then the scene will pick up the name on the sequencer.

I don't know which scenario is your case, but you may try both. Ultimately the red shaded zero user scene error will not destroy your scenes in the sequencer or delete zero user scenes. It is hardcoded not to.

Improve this answer
$\endgroup$
0
$\begingroup$

I have similar issue, to resolve this issue, you need to make sure in the Compositing, you have the Render Layer node that corespond to the scene, and you don't need to check Use Nodes anyway, only put that Render Layer node whenever you Copy the Scene, it will not create the 0 user on previous scene

enter image description here

Improve this answer
$\endgroup$

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.