Thanks guys for all the feedback - this is the sort of information I need, particularly if the render parameters are going to be have to changed so much that splitting the image up to render is not much quicker than rendering it as a single picture.
Quote from: Tangled-Universe on August 10, 2009, 03:20:02 PM
The first image is nicely stitched, can't find any artefacts that quickly.
The second one has an obvious large seam through the water.
The atmosphere is a bit more hazy in that one and that's probably the reason why the tiles differ more.
Martin
This is the worst stitch I can currently come up with - it's the image I've been tweaking the code with as I know it looks pretty bad in the lake area. It appears the more "busy" the scene in the area of the stitching, the less obvious the stitch is.
Quote from: Hetzen on August 10, 2009, 08:37:12 PM
Openning these up in seperate tabs and flicking back and fourth between them, there's some pretty horrible differences. Which would concern me if this was used in an animation. I'm sure that's not the stitching purpose. Just pointing it out.
I've been using the excellent Beyond Compare utility to compare my image outputs, and in the tree scene it appears the trees render a bit lighter in the stitched scene, but it is mostly a consistent change across the scene. If you were using the software for broadcast quality animation, I would suggest rendering each frame as a whole rather than tiling it (my software will support this eventually).
Quote from: neuspadrin on August 10, 2009, 08:59:25 PM
You also might want to have a few clouds, as artifacts can come in theres stitching wise too.
I have tried a couple of scenes with clouds and so far there are no problems.
I'm going to tweak my code a bit futher and I hope to produce one or two larger, higher quality renders over the next week or two.