This is looking very good. I just wonder why do you need to go back and reselect pass every time. In things like this get it doen to as few moves as possible per pass is the way to go. When you have 10-15 scenes to set up passes, doing as less you can for each pass is more than appreciated.
Iād like to see it published, youāll have more than 1 licence from me 
Cheers
If I understand the questionā¦you donāt need to go and reselect the pass every time in the listbox. Itās just the habit of showing people how it works that Iāve started doing that. When you render, it renders from the pass selected in the top āCurrent Passā¦ā pulldown. No matter what pass is selected in the pass listbox. The pass listbox is only for assigning objects and lights to that pass.
No pass specific light-exclusions just yet. Maybe soon, or in a future iteration. But some render globals per pass (resolution multiplier, render mode, ray recursions, render lines).
Oh, my bad. I got it wrong Light exclusions and resolution/AA setting per pass are also very welcome. They can come very handy. Memorizing settings from previous pass (not coming back to defaults for each new pass) is also a big plus. Simmilar way the Deadline submit jobs plugin worksā¦
Yes, at the moment the āSave Pass as Sceneā¦ā option allows you to output the current pass as a scene that contains no pass editor dependent information. (so itās just a clean, normal LW scene.) So you can then take that pass and submit it to a farm setup.
This is not how the plug-in is intended to mainly work, though. This is not like surpasses where the end result is a master scene and a bunch of child scenes. This is all meant to be contained in one scene and rendered from one scene. Thatās why you render directly from the pass editor interface.
Cool!
I suggested this type of approach for NewTek way back (working with saved surfaces instead of object copys). Good to see that someone actually have thought the same thing!
Jeremy: this is excellent! I need a render pass manager like yesterday! I hope to see it released soon, Iāll get it right away.
And also, I agree with some of the earlier posts, light exclusion would be very useful as well.
jeremy - request
This is for a fool proofing it.
Can you have a options panel that would allow one to set a setting that
saves a backup .lwo (and multiple .srf files for multiple surfaces with object name prefix) as it originally loaded in a specified directory, just in case one nuts up and kills hours or days of work on custom texture and shading.
Iām not sure I understand what youāre asking. The overrides only affect the render as rendered from the pass editor. In other words, if you do an F9 or F10, the results are still your normal object and scene. Itās not changing settings for your loaded scene. Itās āadditiveā or āreplaciveā if I can say that. So it leaves the scene totally in tact, but allows you to have all your passes set up in that one scene as well. And if your overrides arenāt loaded onto an object or light or pass scene, then that object or light or pass scene defaults back to the normal scene and object information for that pass.
But a surface override wonāt show in an F9. That would be doing destructive changes. It only shows in the test frame as rendered from the pass editor (or pass sequence). Same with all the overrides. You wonāt see the motions in the layout viewport when you use a motion override. Only for the rendered pass.
Unless youāre saying that youād like this to just be a backup tool as well? One that backs up your .lwo for you at certain times? Am I misunderstanding you?
yes this is just for backup purpose. And it can be a checkbox or something: totally optional.
What would it be backing up, sorry? Just your normal scene? Like an autosave? Your normal objects? Iām just not seeing what this has to do with the pass editor, since the pass editor doesnāt really change your normal scene and objects.
Hi,
Iāve had the pleasure to betatest this Great tool and I can say that is very easy to use and I really like the workflow. I made a test yesterday with a real production scene (a previous job in which I had to split the render in objects passes by hand), this scene was 12 mill. polys optimized (with normal maps) at about 3 mill. 32 strawberries fall over a cereal bar, they are real clones with displacement textures applied, motions controlled by motionmixer, sss, G2, spinning lights, etc. and it works perfectly!
Other great plus that Iāve found is that it plays nice with Pixel and Images Filters Node Editors from Denis Pontonnier; so if we add a NE first in our master scene, renderPass Editor can be used for multipass rendering together with any NEs for multilayering rendering, each render pass with their respective buffers! :bounce: Theoretically speaking, it should work also with the new ExrTrader, I guess, since what renderPass Editor also makes, is to save an independent scene for each pass, in such a way we can have a different buffersaver setup for every different pass.
Thank you for so useful tool, Jezza. Looking forward to the final release!
Gerardo
A new video. Selective passes.
http://www.lwidof.net/passEditor/passEditor-selectivePasses.mov (9.1mb sorenson 3)
Just showing that this is also very useful for pass splitting and organisation, not just creating custom passes.
Heyā¦ sweet stuff there! Iām totally interrested in this! Ohhā¦ and hahaā¦ the computervoice is quite fun, but hard to understand at times. Why donāt you record your own voice?
Had some downtime at work between this and that, but couldnāt talk into my computer without looking weird. 
One more before I sign off for the night. This one covers the overrides.
http://www.lwidof.net/passEditor/passEditor-overrideTypes.mov (13mb sorenson 3)
Dudeā¦ This is getting awesome! Iāve needed decent pass management in LW for ages. Canāt wait to get my hands on it. :drool:
serious, serious stuff jezza. thx:thumbsup:
donāt be shy, this deserves itās own thread and all the attention it brings. congrats.
