Netrender for stills about blender-network-render-additions HOT 6 OPEN

Just want to thank you for your work. Now I can use network render with GPU :)

from blender-network-render-additions.

Hi,
Sounds nice! However currently we do not have time to look if and how we can implement these features. Developing this stuff needs a lot of testing on different OSes, it is slow and painful process, the Macs and PCs have to be left alone in that process, so we can be shure that the results are not corrupted. As one might suspect - these additions came when there was an inhouse demand for that. Thus only thing I can promise is when a new project will pop up where we again need to gather all the computational power we have in studio, we'll look into this.

from blender-network-render-additions.

Ok, i see.

Imho the proposed changes would not be much OS dependand, but you will probably know better... 8->

from blender-network-render-additions.

Hi,

Can I use the current Blender Version 2.77a, or is it recommended to use the Version 2.75 wich you have mentioned in the text?

And once I have connected the slaves, do I have different buttons on the client to start the process, or do i press "send current frame job" like in the normal networl render thing?

from blender-network-render-additions.

@hcw70
these still rendering extra features are nice, related to #2

• region (border) rendering (so that one monsterimage can be pushed to multiple slaves)
• seed randomisation per slave (is this feature not solving it already OOB?, frames will be rendered at different timestamps across the slaves, and seed val imho directly depends on exec machine time)

could you elaborate on render layers? actually client receives exr from master, it may not be immediately obvious though.
once you click "get image" - in opens in image editor. see RenderLayers (btw the file physically is put into Path as specified at very top if Client tab). imho something is wrong there, but groundwork is there to extend it.

@Wissperwind i just checked OOB netrender for 2.78c. it has still the same code as in 2.75a which was the original base, thus this will work. just push "send current frame job" and/or "get image" for stills. the button names are dubious, but I have not made any changes in them from the original netrender. and personally i dislike the different output behaviour between animation (automatically saved in directory and format as specified in Output subpanel in Client tab) and stills (manual saving from Render Result)

from blender-network-render-additions.

@kroko Seed randomisation according to the new blender feature should work for this issue.

Regarding render layer my intention was to send the same image to all render slave, have a different seed for each (with reduced iterations) and then combine the result images with an average filter (which is as i understood is the same as having the original iterations setting.

from blender-network-render-additions.