Hi guys, here's my newest Terragen 2 pic. Comments welcome.
Note: This took 16 hours to render so I doubt I'm rendering it again.
Ce que je trouve bizarre c'est l'arrête au milieu de l'image.
Mais c'est jolie.
Quote from: bla bla 2 on October 28, 2010, 03:50:25 PM
What I find bizarre is the stop in the middle of the image.
But it's pretty.
I can't explain it either ...
Probably a fractal line. Did you use a noise flavour other than 'Perlin' in the general mountain shapes?
Perlin ridges and billows noises will create these lines between features, whereas straight Perlin will not. Also, perlin mix 1/2 will create them as well, as they are variant blends of the Perlin billows/ridges noises.
16 hours seems a ridiculously long time for this image, maybe you'd like to post the .tgd and we can try and get that time down by an awful lot... :)
TGD right here.
At first glance, a cloud quality of '12' on a 1500m thick layer is your problem, especially since your camera is inside this hazy layer. Drop that to '1'(making it 16 samples, instead of 200) and you'd have this rendered MUCH quicker. ;)
* Edit, I'm rendering it now on 2 cores, I'll say it'll take no longer than 20 minutes on my crappy computer. I'll update with the actual time when it's done...
Quote from: dandelO on October 28, 2010, 06:39:15 PM
At first glance, a cloud quality of '12' on a 1500m thick layer is your problem, especially since your camera is inside this hazy layer. Drop that to '1'(making it 16 samples, instead of 200) and you'd have this rendered MUCH quicker. ;)
* Edit, I'm rendering it now on 2 cores, I'll say it'll take no longer than 20 minutes on my crappy computer. I'll update with the actual time when it's done...
I rendered it on a dual core too ... the atmosphere didn't seem to take the longest to render. Anyway, I really don't know why it would take so long, if someone can find out that would be good ..
From 16 hours, to 16 minutes, in that one single step. :o
This is just the default final render node settings of the .tgd you uploaded, I'd say no longer than 30-45 minutes at the size 800x550px, that you have posted above. Maybe an idea to quickly run through all the quality settings before commiting to a final render that will tie up your computer for hours and hours unnecessarily. ;) A cloud 'quality' of '1'(full quality) is usually adequate.
[attachimg=#]
* The line in your terrain comes from the Perlin billows noise in the fractal terrain. Also, the orange colour doesn't need checked in that fractal as it won't appear in the render. The terrain shaders before the 'compute terrain' node only supply displacement information to the scene, colour is applied after the compute terrain node. Unless you plan to use the colour output of that shader to feed another shader function further down the chain then it doesn't need checked at all. And, if you do need to do that at any point, black and white would be your best bet for choice of colours as it will give you the correct control(contrast/roughness/etc) of the range between black and white.
QuoteAnyway, I really don't know why it would take so long, if someone can find out that would be good ..
I just did. You had cloud quality at '12', when '1' is sufficient. :)
* You'll find that it actually was atmospherics that was taking such a long time to render, your camera is only about 14m from the centre of this cloud layer, its altitude(Y) is about 6m above the planet surface(this setting doesn't take displacements into account, it's a fixed height, according to your planet radius) and your camera's 'Y' is about 20m so, everything that is being rendered is viewed through this hugely sampled haze-cloud.
:o Thanks Martin, man I had no idea! I need to check my render quality settings before I render things. I guess clouds like I had didn't have to be such high quality.
So, now you can report back later with a new render time. ;)
Maybe, since you don't have to wait 16 hours, you could also try fixing that line. I'd isolate it by drawing over it with a soft painted shader and use it as the blend shader to a smaller fractal. Then the new shader will only appear over your painted line mask. Maybe you could even find a better way than that. Generally, laying a smaller scaled displacement over the original terrain should cover up any fractal lines but be careful, too much amplitude will destroy your original mountain shape, not enough and it won't be enough to break up the line.
* I was going to upload an edited .tgd where I'd fixed the line but I figure, this could be a good bit of a practice for you to try out yourself. :)