Planetside Software Forums

General => Terragen Discussion => Topic started by: ultrasonic on April 28, 2017, 11:25:36 AM

Title: massive difference between RTP and disk rendering
Post by: ultrasonic on April 28, 2017, 11:25:36 AM
Hey guys,

we are currently evaluating the free trial and we noticed a massive difference between RTP and disk rendering.
[attachimg=1]

Any idea where this might come from? I cannot post the file here, but I could send it via mail...what is your support address?

Cheers
Oliver
Title: Re: massive difference between RTP and disk rendering
Post by: cyphyr on April 28, 2017, 03:42:24 PM
one thing to mention is that you should always set the preview level to HD, let if finish "previewing" without any atmo, lighting or textures enabled (small row of buttons along the top) and only then switch to RTP.
Title: Re: massive difference between RTP and disk rendering
Post by: ultrasonic on April 28, 2017, 04:05:56 PM
thx for your answer!can you elaborate a bit on why I should do that? Is this documented somewhere or is just something you got used to?
Seems more like a hack to me after reading it for the first time.
Title: Re: massive difference between RTP and disk rendering
Post by: cyphyr on April 28, 2017, 07:37:52 PM
It's not a hack :)
much more detailed explanation here ...
http://www.planetside.co.uk/forums/index.php/topic,21730.0.html
Title: Re: massive difference between RTP and disk rendering
Post by: Oshyan on April 29, 2017, 12:02:14 AM
There is no terrain in this case, so HD will not matter. HD only affects terrain geometry detail generation.

It looks like there are some areas of your cloud that are very hard for the RTP to sample and get to a low noise level. I would guess that what you're seeing is undersampling; a lot of noise that is giving an inaccurate result. The first thing I would try is enabling the crop region and setting it to focus on one of the problem areas. The idea here is to let it resolve a lot more to see if it gets more accurate, and doing it in a crop will happen a lot faster. If it eventually resolves to something that looks more accurate then it's basically a sampling problem. One that we might be able to improve on, but at the same time there will always be situations with hard-to-sample shaders which will just need to resolve more to be accurate.

So, assuming that letting it resolve further gives you a more accurate result, then I would say the bottom line is where you see a lot of noise like this, use a crop region and let it resolve further to get a more accurate view.

- Oshyan