Yes it can save your renders incrementally. If you set your output format to multilayer OpenEXR, it will save your render layers and passes.
If you want to save them to another format, the best is to set up a File Output node in your compositing.
Please watch the video in this post to see how the Render Queue works.
In the init.py, comment out lines 80 to 83.
In the render_queue.py, comment out lines 231,232,241,242.
I can probably gather everything in one place in the future, not sure if itâs worth adding an add-on preference for it⌠Does it bother you that much to have the panel in these layouts?
EDIT: Nevermind, I added the option in the preferences, will be in the next version.
Thank you very much, I have a large number of addons.
Therefore, panel management is very important for me.
For example, Photographer is under âViewâ.
I just donât need the panel in so many places.
But are you sure that in ârender_queue.pyâ the lines â231,232,241,242â are meant? For me it looks more like â221,222,223,224â and â231,232,233,234â. 241 and 242 do not exist at all. Normally the panels are registered with âbl_categoryâ, so I had not found them.
But in Preferencens it is of course easier.
So I have a focus plane that works really well, but I have to push back the next release, because I am using drivers, and adding drivers through the add-on makes Blender super unstable and constantly crashing for weird reasons (like changing the âShow in Viewportâ for the driven object in the object properties).
Tried to get help from devtalk but no luck, so if anyone has a clue, let me know.
Hi Chafouin,
I really like your addon, thank you very much!
Sorry, I cannot help with the focus plane problem, I have instead a small feature request:
If a switch betwen different cameras in the Outliner (just selecting one of them) and I look at the Properties panel I can see changing the properties for each camera, even if i donât make the selected as Active camera.
Doing the same from the Sidebar panel does not take effect, unless I make the camera Active.
Would it be possible to correct this? When I have a lot of cameras in the scene I like to check the different setting of each one, without changing the view.
Thank you!
Ciro
Unfortunately⌠this is by design, and I donât think this will change
The reason is that it would be very confusing to change your photographer camera settings and not see effects on the viewport directly.
The camera property panel is already doing that, so I prefer to keep both behaviors instead of getting rid of one entirely.
Added Preset systems to Exposure and Resolution panels
Added Lumens per square meter for Area lights. This can be useful to replicate LED strip lights brightness values provided by manufacturers and maintain brightness while scaling the area light. This should NOT be confused with Lux, which represents lighting brightness that hits a surface.
Added Preference option: Camera Default Passepartout and Composition Guides for new cameras
Youtube video is coming soon, but the feature is pretty self-explanatory. Only caveat is to turn off the Focus Plane before deleting a camera, or the focus plane wonât be deleted with it. Alternatively, you can âDelete Hierarchyâ of the camera in the Outliner, or simply use the Camera List delete button in the Photographer panel.
The DOF panel does not follow the the other panel preferences. I changed it myself in line 117 in âcamera_panel.pyâ to bl_category = âViewâ. Where View is the desired panel name.
Only if there is someone else who lives outside the preferences. P.S. First make a copy of the file!!!
Will fix it ASAP. There are so many settings now that I easily forget
EDIT: 3.6.1 is out with the UI fix of the issue reported by @MarioPeper.
Also just fixed a versioning mistake, please redownload if you encounter any issue. Sorry for the inconvenience.
Iâve finally bought your addon (sorry but using BlenderMarket where I was able to use my PayPal wallet without any CC involved) and Iâve tried your focus plane.
First of all itâs a nice feature.
Just noticed that the plane is not updated if I use an object as focus target.
The âXâ moves itself correctly but the red plane not.
Is it correct? or is it a bug?
Itâs âcorrectâ because the Blender Focus Object feature does not actually update the Focus Distance value.
For now I simply disable the focus plane when you pick your focus target, but I can fix it in the next version.
I actually started recording a video tutorial a year ago about the physically-based lighting theory, never got to finish it as I saw others (CG Cookie) releasing good videos about the subject. I might take the time to write down a documentation, but you can read the descriptions of properties leaving your mouse over them, I always try to put the most meaningful information there.
If you are talking about the Physical Starlight and Atmosphere add-on, Iâm not sure what they ended up with, they had some issues when using proper intensities. Photographer works fine with Blenderâs Nishita sky or LuxCore Sun and Sky.
Improved: Focus Plane now works with AF-Tracking. It also works if you use a regular Focus Object, you will just have to disable/enable the Focus Plane after updating the Focus Object.
Improved: White Balance Picker now works with 2.91. It now updates in real-time in the 3D view, and accuracy has been improved.
Changed: White Balance Picker in Image and Node Editor now uses the regular Color Swatch Eyedropper, for better compatibility across versions. It takes two clicks instead of one, but it promises to be more stable until BGL is fully replaced.
Improved: AF Tracking and Camera Target are now more stable and wonât create several trackers for the same camera in some situations.
Fixed: Camera Target orientation was incorrect in 2.83.
Blender development goes extremely fast, and itâs hard for me to support 3 different versions. I do my best to catch errors, but I will obviously miss some. So please bear with me, I really appreciate when users take the time to report errors, and do my best to fix them as fast as possible!