Having Problems?
If your problems are not answered here, please post a comment on the forums.
Common Complaints
Here are some of the common problems that may arise when using Distriblend. If you have further examples or unresolved issues, please feel free to post on the forums.
Rendering Failed
The Node will usually give a reason for a failed render in its log. However, sometimes it cannot ascertain the exact cause of the error or the description may not be clear. The following list describes some of these cases and how to fix them.
- Long path names
- The Node may report a missing frame file if you install distriblend too deeply or the projects you submit have long path names.
In previous releases, if the node.conf file listed an incorrect path to Blender, rendering would fail without providing any reason. However, since 1.2 the system will not start if it cannot find Blender.
Limitations
Some common features are still missing from Distriblend. This list hopes to identify where the system falls short:
- Failed renderings are treated as successful but without returning any frames. The Node's log window should be inspected for the reason.
- If a Node disconnects whilst rendering and does not return, that frame is not repeated unless the Distributor is restarted (since it waits for it to return not knowing how long the render might normally take).
- Frames cannot be retrieved from an incomplete project by the Client. To access the frames, look in the storage directory for the distributor.
- Projects cannot be paused or stopped once they have been submitted for rendering.