Renaming a scene post-render breaks Backdrop and Render Result viewing #30222

Closed
opened 2012-02-16 23:42:03 +01:00 by Bill Knechtel · 3 comments

%%%If you're using compositor nodes and rename a scene after it's been rendered in cycles or blender internal, then make a change in any node, the backdrop stop drawing, and the render result in the UV/Image editor shows nothing. If you then rename your scene back to what it was previously, then make a node change, everything will work fine again.

To Recreate:

  1. In the attached blend, Render and go to the compositor.
  2. rename the scene.
  3. Break the connection between the render layer and the viewer and then reconnect it.

You'll notice there's now no backdrop, and if you flip over to the UV/Image Editor, there will be no render result either.

  1. Rename the scene back to "Scene".
  2. Break the connection between the render layer and the viewer and then reconnect it.

Now everything is fine again. If you re-render the scene with the new name, before performing step 4, it will work with either scene name.%%%

%%%If you're using compositor nodes and rename a scene after it's been rendered in cycles or blender internal, then make a change in any node, the backdrop stop drawing, and the render result in the UV/Image editor shows nothing. If you then rename your scene back to what it was previously, then make a node change, everything will work fine again. To Recreate: 1) In the attached blend, Render and go to the compositor. 2) rename the scene. 3) Break the connection between the render layer and the viewer and then reconnect it. You'll notice there's now no backdrop, and if you flip over to the UV/Image Editor, there will be no render result either. 4) Rename the scene back to "Scene". 5) Break the connection between the render layer and the viewer and then reconnect it. Now everything is fine again. If you re-render the scene with the new name, before performing step 4, it will work with either scene name.%%%
Author

Changed status to: 'Open'

Changed status to: 'Open'

%%%This might be annoying but not actually a bug. Just currently rendered image is stored in Renderer descriptor and access to this renderer happens using scene name. It's the most reliable way to link scene with renderer. If scene was renamed it'll use another renderer in which there's no rendered image.
It might be resolved by storing renderer in Scene datablock, but it'll be still stricky because of all that undo system and so.
I'd wouldn't consider this is a bug, just thing which might be improved. Added note to our TODO list http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Render#Render_.26_UI
Thanks for the report, but will close it now.%%%

%%%This might be annoying but not actually a bug. Just currently rendered image is stored in Renderer descriptor and access to this renderer happens using scene name. It's the most reliable way to link scene with renderer. If scene was renamed it'll use another renderer in which there's no rendered image. It might be resolved by storing renderer in Scene datablock, but it'll be still stricky because of all that undo system and so. I'd wouldn't consider this is a bug, just thing which might be improved. Added note to our TODO list http://wiki.blender.org/index.php/Dev:2.5/Source/Development/Todo/Render#Render_.26_UI Thanks for the report, but will close it now.%%%

Changed status from 'Open' to: 'Archived'

Changed status from 'Open' to: 'Archived'
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: blender/blender#30222
No description provided.