Fractal Terrains 3 Upgrade just dropped...

[guyanonymous]

I'd agree that the $10 isn't a big hardship, and I'm pleased for better looking rivers, for sure. The additional climate maps etc. are also welcome. I also like the new streamlined interface.

___

I've attached a psd file showing the multi-image allignment issues I've noticed. EDIT: I couldn't attach because of file size, so I've uploaded a zip file to mediafire. It contains the .ftw, the .psd multi-layer crop which uses two .bmp exports, and four full-sized .bmp export files (6000x6000) which fit together in a square and show what I call the 'dark line' (inverse tones?) issue, and 'river-gap' issue which. Here's the link: http://www.mediafire.com/file/dbot44...20right%29.zip

For the PSD: As each image is 6000x6000 pixels, I've just taken a slice of two of them on the sides they meet. The bottom layer is on the left and includes the dark line (that's part of the saved .bmp file). The top layer is on the right. There is no space between the images.

Re: Rivers: If you scroll down, you'll find several examples of rivers that cross the border, and notice there's a 1-2 pixel game on each side of the border (the land is there). I've circled several in red to make this easy The 'river-gap' problem occurs at the top/bottom of images as well.

Re: 'Dark Line' issue: You'll also notice on the right edge of the left image (bottom layer) and on both images at the bottom most edge, there is a one-pixel line that appears to have an inverse light-dark value; the colours are correct, but what's light is dark and vice versa.

In the past, I've just moved the right image over to the left one extra pixel, to overlap the 'dark line' artifact of the left image, it tends to look better (still with river gaps), but not perfect. There is enough of a pattern that becomes apparent as you scroll up and down, as there appears to be one missing pixel. I've not tried inversing the height map for that single pixel yet to see if that's what it actually represents. I believe the bottom right pixel on every image, though, is normal, because the right line and bottom line overlap there, producing a double inverse, or normal pixel.

I saved these, originally, in bmp to avoid compression artifacts.

I'll also upload the original .ftw file I'm using. I output at 6x3, with a resolution of 5000. This, in theory, will let me make a 30000x15000px image, though it's always a couple pixels off because of the 'dark line' artifact. I think it's appearing on the right and bottom of each saved image.

Thanks for taking a look at all this...if this was fixed, it would save me a LOT of time when I merge the multi-files back together, and actually let me automate the process.

p.s., with respect to your comment about 32/64 bit saves not working in the opposite version, it's likely that anyone using a 64 bit version would only use that, and vice versa (unless you end up with a plug-in situation like photoshop with some plugins only working in 32bit and others only in 64).

p.p.s., Is it possible to feather the tools in this release? Or use a different brush (other than a circle/oval of your dimensions)? If not (and I don't think it is), please consider those features for the future if they can be worked in.