Indigo Renderer Forum

Hi.
I start this thread.
_________________

The first is a quickrender (wip) that I loose (position of camera and sun; is recuperable. Same scene). The second is the first landscape of the post. Basic (very) , but enough to start. I stop at 2000 spp because the scene starts at 0.8 M s/p but loose power decreasing at 45 min to 0.45 M s/p.
The picture is croped because the poor very first plane.

Numbers:
30 x 30 kilometers patch landscape
5000 x 5000 poligons of definition
11 millions of instances

Nice ones yonosoy! I believe Ono fixed a problem that could cause that decrease in render speed in version 4 of Indigo.

Very cool!
One thing that might be helpful that I could add is a scatter mode that scatters more objects nearer the camera.

Very nice!

OnoSendai wrote:One thing that might be helpful that I could add is a scatter mode that scatters more objects nearer the camera.

Some Falloff sounds indeed interesting, but also interesting how to control it and keep it adaptable for all kind of scenes.

I would just tweak a bit with the lake.

Hi, thanks.
The more or less standard stuff for landscaping:
- A meaning of fractal response or slope.
- Minimum and maximum altitude of scattering (if possible with a relative meters of randomness to avoid straight lines in the landscape).
- Clip planes to near and far distance from camera.
- Backface culling.

And of course a falloff could be very interesting too. Also sometimes is better when you have several scatter systems in the same scene that each one could interpret the other to avoid the same space for multiple instances, but this last could be more difficult to acomplish.

Well, an attempt of earth simulation. The zenith is 92º, the camera is at -500 meters very far from the origin. Is void and poor poligonizated at this distance (a icosaedro several times subdivided at the noth pole determined by a decreasing system of circles). Sadly has a very poor effort of sample, 8 hours of render for 9000 spp. And a better attemp. 15 x 15 km., 3000 x 3000 poligons, 16 Millions of instances, again reached the maximum poligon count. Only three vegetation models (sorry for this, my fault). 4h of render 3600 spp.

Looking promising, I really like the first image.
You can actually control scattering with shaders, I'll give you some examples soon.

Can I ask how many triangles you have in total?

Thank you Ono.
Oscar, in this moments I´m doing another isolation with a more complex cover ground.
The scene has 17.174372.952637 (more than 17 billions?) of triangles in v4.0 eating 16 GB of RAM. I brake the poly count of v3.8.

I retake the first one with Metropolis Pathtracing and performs very well. The color is subtled altered from Pathtracing to Metropolis Pathtracing.

yonosoy wrote:Thank you Ono.
Oscar, in this moments I´m doing another isolation with a more complex cover ground.
The scene has 17.174372.952637 (more than 17 billions?) of triangles in v4.0 eating 16 GB of RAM. I brake the poly count of v3.8.

I retake the first one with Metropolis Pathtracing and performs very well. The color is subtled altered from Pathtracing to Metropolis Pathtracing.

landscape_Ab_2.jpg

That would be 17 trillion triangles in the silly english "short scale" number system. See https://en.wikipedia.org/wiki/Names_of_large_numbers

And holy crap that's beautiful! You should just add some displacement to the water.

Great stuff, really beautiful!

Astonishing...

Thank you very much. Sorry for the water in the last...

The scene slows down in v4.0 so I fallback at the moment with v3.8.33.
I realized that with Metropolis pathtracing the scene is faster than with pathtracing. This allow me to use the Post Process Aperture Difraction.
2h of render 2300 spp. Turbidity for the scene 1.6. At the moment I only can go with a FBM bump for the water. More over... (I expect to buy another slot of memory).
I try to process in the future two perspective with two isolations for each landscape. I use three patchs for the ground with several species but is almost for nothing in this perspective .

That's close to life-like, congrats ! I think that the instances all have the same orientation, it adds a lot to randomize rotation and scale for each (exporter thing).