| Message |
 |
- Date: 2010-03-10 01:17
- Sender: Matt Ebb
- May not be a problem with netrender per se, but Martin's probably best equipped to see what the issue is. Assigning to him.
|
- Date: 2010-03-12 03:39
- Sender: Martin Poirier
- Rendering goes fine, but compositing has to be turned off on the client, otherwise it reapplies composition that has been done on the slaves. I'm going to have to figure something out to turn if off automatically.
|
- Date: 2010-03-12 04:07
- Sender: Martin Poirier
- There's also this warning when loading back the result (a multilayer exr) in Blender through the render engine api, loading the exr manually works fine.
warning, channel with no rect set Composite.Combined.A
warning, channel with no rect set Composite.Combined.B
warning, channel with no rect set Composite.Combined.G
warning, channel with no rect set Composite.Combined.R
Assigning to brecht for testing (I think he's responsible for the render engine).
|
- Date: 2010-03-14 17:08
- Sender: Martin Poirier
- Adding a demo file.
Unzip, open blender from this directory (it will load results.exr from cwd), load result.blend, execute opened script (it should change the render engine to Test Render, do so if it didn't), render. It should display exr warnings in console, the layers mentioned in the warnings will be missing from the result buffer (but would be visible if loading the exr in the image editor manually).
|
- Date: 2010-12-05 12:06
- Sender: Brecht Van Lommel
- Looked into this bug again, and the problem is that network render expects all layers in the .exr file to be loaded, while only the ones that the renderer expects are loaded. This is working as designed actually, but in this case it would be useful to support loading other layers too. Not sure yet how to solve without making major changes.
|
- Date: 2010-12-06 03:41
- Sender: Martin Poirier
- IMHO, when loading a multilayer exr as render result, it should recreate the result as it was originally (so that saving and reloading as result is a lossless operation).
|
- Date: 2010-12-07 19:08
- Sender: Ton Roosendaal
- Ehm... so the conclusion is, no bug but just 'how it was coded' ?
|
- Date: 2010-12-08 03:50
- Sender: Martin Poirier
- Depends what we want to support for render engines. Personally, I'd consider it a bug, at the very least a missing feature.
|
- Date: 2010-12-08 08:27
- Sender: Brecht Van Lommel
- I guess it's not a bug in the render api but still one in network render, which is also a feature. Anyway, I'll try to fix this.
|
- Date: 2011-06-19 13:05
- Sender: Ton Roosendaal
- Reminder to this report, it's getting dusty! :)
|
- Date: 2011-11-10 22:12
- Sender: Ian Foot
- I see that "[#28049] Blender "Network Render" does not render effects (nodes) from the Compositor." has been marked as a duplicate of this.
It would seem to me that this is an extremely serious bug as it is impossible to use netrender to farm out any scenes that use compositing nodes.
The slave nodes render the scene correctly with both the renderlayer and the composite output in the exr file. The master monitor web page correctly shows a thumbnail of the composited scene. However, the client seems to only expect, and will only display the renderlayer before compositing. It completely ignores the composite layer, as if it doesn't exist. The client does not appear to be expecting the composite layer at all, even though Compositing is checked in the Post Processing settings in the blend file.
This bug can be very easily verified, using the default cube. Simply open the nodes editor, enable nodes and set up a simple compositing pipeline (e.g. connect alpha from the renderlayer to the compositing node). Rendering locally will display the expected output, whilst a network render will only display the renderlayer before compositing.
This bug effectively renders (sorry!) the netrender absolutely useless apart from for very simple work. I am extremely puzzled as to why there appears to be no progress on this bug, since it is a year and a half old.
|
- Date: 2011-11-11 01:43
- Sender: Martin Poirier
- Please note that the work around written in the other report still applies.
That is: the result exr files on the master can be fed into Blender's compositor as multilayer and that will work correctly (as if you'd render them locally).
But it sure would be nice to get it fixed.
|
- Date: 2012-04-03 14:54
- Sender: Sergey Sharybin
- Support of multilayer EXR files should've been improved in svn rev45358. probably it'll fix the tissue?
Brecht, othewise mayeb better to move this into a todo?
|
- Date: 2012-06-19 00:24
- Sender: Thomas Dinges
- What is the current status? Can we close or mark as ToDo?
|
- Date: 2012-09-24 20:45
- Sender: Thomas Dinges
- Closing this one due to no updates.
|
|
