Each of the rendering engines 130 generates results. For example, different rendering engines 130 may provide results for different pixels. As another example, according to at least one embodiment, different rendering engines 130 may, at or around a particular time, provide results for a same pixel. In this regard, according to at least one embodiment, two or more of the rendering engines 130 may sample a same pixel, but at different locations. At a given time, results generated by the rendering engines 130 are merged (e.g., by a merger 140) to produce a merged result. For example, at a particular interval (e.g., an artist-selected interval), each rendering engine 130 provides its results to the merger 140. The merger 140 combines the results from the rendering engines 130 into a single image for display. The merged result is provided to the front-end client 110 (or saved in storage for later viewing). The front-end client 110 may control a display, e.g., an external monitor, to display snapshots of the merged result. As such, the artist may evaluate progressive results of the changes that he or she had initiated.

As described earlier, the dispatch 120 provides the inputs to each of the rendering engines 130. For example, duplicates of the inputs are sent to every rendering engine 130. Accordingly, each of the rendering engines 130 has (e.g., in its own or corresponding memory storage) an exact (or the same) copy of the scene to be rendered.