www.kraytracing.com

Hi

First I must admit that i am getting a little fed up with waiting for any news regarding K3.0.
Anyway I am posting some renders just to break the silence on forum and to encourage all kray fans to post their own - lets entertain each other waiting for K3.0 :):)

These are my favourite renders that i made for two competitions - that's why there are some geometry errors.

This looks good! Really! Congratulation!
Some details about render? recurse, light, etc.
About K3.0 I know Your frustration but please be patient. We connect now K3.0 to Layout but also in this category will be a lot changes (probably we will have KrayHub which will control whole Kray system (render part, plugins part, shaders part, network render, etc). Grzegorz took decision to reorganize this department because code of Kray is huge and is very hard keep eye at everything (thousands of code lines in many departments). Is no choice If we want faster response for bugs and new additions.

nice work .


@ jansuz thnx for thos great information about kray 3. so sure we will be patient or kray b strong and strong more and more .. we have time

Thx!

The setup was nothig special, kray sun (with lower exposure of 2) sun intensity around 0.5 with HDRI in LW's backdrop.

I did not use recurse because render times were even longer than photon mapping (probably because there is quite a lot geometry and photons don't just 'fly' in the air after first bounce).

Janusz can you give us any estimate on when K3.0 will be near completion? A month, two, half a year... Any little previews? I know that I am bothering you but it is not easy just sitting and waiting

medzo wrote:Thx!

The setup was nothig special, kray sun (with lower exposure of 2) sun intensity around 0.5 with HDRI in LW's backdrop.

I did not use recurse because render times were even longer than photon mapping (probably because there is quite a lot geometry and photons don't just 'fly' in the air after first bounce).

Janusz can you give us any estimate on when K3.0 will be near completion? A month, two, half a year... Any little previews? I know that I am bothering you but it is not easy just sitting and waiting

Limiting bounce lights amount by recurse command will not bring visible speed render at all. Photon Mapping mode is not that "sensitive" (For Kray is almost doesn`t matter 5, 10, 20 bounce lights and more) because interpolation method calculations are much faster then Path Tracing calculations.

Big different will be in Path Tracing. Calculations speed dramatically drop down with small recurse value. For example in Exteriors you can try put in cmds line: recurse 4. Of course be careful with glass (this material needs minimum 10 recurse to look good)
This will be solve in K3.0 by special code which will make exception for transparent materials even when we limit amount of recurse under this level.

For Photon Mapping personally I use recurse 8-10
For Path Tracing recurse 5 (remember glass problem) - if in scene are just basic windows glasses with two layers - then will be not problem. Problem can start when will be more layers of glass (black surface render)

Kray is connected to Layout now. Will be new structure of files: KrayHub which will control all Kray parts. This is now rewrite to new system and is necessary because amount of data in code is huge.

sorry i made a mistake. when i was talking about recurse i meant path tracing with (recursed) limited bounce around 8 (of course because of the glass).

In my tests i also found that path tracing with low recurse value produces quite fast renders and also the light does not bounce so much producing visualy pleasing transitions between light and shadow.

medzo wrote:sorry i made a mistake. when i was talking about recurse i meant path tracing with (recursed) limited bounce around 8 (of course because of the glass).

In my tests i also found that path tracing with low recurse value produces quite fast renders and also the light does not bounce so much producing visualy pleasing transitions between light and shadow.

I think good balanced value for Path Tracing is 5. Under this amount transport of photons starting be poor. Over is too much for calculation and no big different in light.
Too dark shadows you can reduce by tonemaping.

That problem You can notice in Octane render for example. Use real Path Tracing mode with recurse 5 or more dramatically increase time of render. Of course this problem is huge in interiors where almost all photons must be calculated from one to five recurse..only a few percent escape by windows after one or two bounce.
So to avoid long render in Octane you can switch render mode to DIRECT MODE + Occlusion system. Then is very fast but is one problem: render is artificial because most of GI is simulated by DIRECT MODE and OCC.
The time to receive clean render in Octane is infinite. We can only wait up to moment when noise will be acceptable for us....
Situation is the same in Kray. We can raise up min/max FG for Path Tracing forever and still will be small noise. For my render with Bugatti I used FG 1000/0 and this was acceptable for me . Scene is almost empty and contain a lot reflection surfaces. I could reduce it even to 200/0 so render would be 2 times faster.
In interiors even FG 10.000 is not enough

very good renders and nice design