This one was written so that anyone could easily render out all the render passes on all render layers into separate files, to composite in any program they would like to use (e.g. GIMP / Photoshop / Nuke / AE).
It creates a file output node for each render pass on each render layer, so when you render it will save the respective image files in the specified render output folder.
For more information about the script, its development, usage and installation instructions, here’s the post about it in my blog.
Traceback (most recent call last):
File “E:\Blender_YAFARAY\2.66\scripts\addons\save_all_renderlayers_and_passes.
py”, line 251, in execute
basename = self.find_base_name()
File “E:\Blender_YAFARAY\2.66\scripts\addons\save_all_renderlayers_and_passes.
py”, line 77, in find_base_name
if len( re_match.groups() ) > 0:
AttributeError: ‘NoneType’ object has no attribute ‘groups’
Dito,
To help fixing this issue,can you please specify the name of your blend file?
(please provide the full filename, including the suffix. Best to copy and paste it from the file editor, so that I would also see the exact case of each letter).
Dito,
Did you check the “use nodes” option in the compositor’s composition nodes?
Please download and try the latest version of the script (where the button will be disabled unless “use nodes” is checked),
and let me know if the problem persists.
If it does, please upload your blend file to some file hosting service and send me the link so that I could test it.
This is a very good idea, we should have something like this in the official builds all the time. I spend most of the time setting up output nodes when you’re working in a big production.
I thought it might be because you’re using Cycles and I only tested it on BI,
But that worked just as well (as it should, since with regard to render layers and compositing nodes it’s the same).
I’ll try to get my hands on a winXP computer to test it there (tested it on Ubuntu and Win7 but not on XP),
and see if that has something to do with it.
About a month ago API changed and we add nodes differently. As an Addon writer you follow blender coders mailing list right? Errors like above will appear in latest builds. You probably used official 2.66 release. This shouldn’t be done. Always make your scripts compatible with latest releases. Especially that 2.67 will be out really soon.