This is not bug but very requirement feature: we need finally to have control over Physky Sun from Layout lights.
Solution is easy: control from direction light source from Layout (position does`t matter)
Second request is to have desaturate option (0-100%) for whole Physky which will allow users to render interiors like “studio interior” (I suggest to have 2x desaturation: for Physky background and Physky Sun)

So in this request, extra 3 options in GUI:
- control Sun position (selection light source)
- desaturate Sun
- desaturate background

…easy task but will help a lot.

Need to be same color everywhere (RGB 241.241.241)
Of course LEM`s are unteachable in this case.
I am not sure is this bug: selecting Pure Color and Pure Diffuse create total white render.

Need this for future tests.

Shader GUI should contain all features in on window.
I think is time to start create.

Perhaps GUI for that will be big and it will need scrolling. But if we add activation button - it will be less mess.
All effects for K3Shader can be activate in the same time but still in one window.
It will grow in future but everything will be in on place.

We will create at least three sub options: - K3Flags (all necessary flags: unseen flags, Invisible LEM)
- K3PowerShader (contain all K2 features)
- K3ShaderSurfaces (physical surfaces)

K3Shader can not override Nodes settings (especially texture pre-processing)

Override mode works now perfect: all flags works.
One thing is not working: LEM surfaces should keep his own color and not be overridden by color from Override GUI.

Scene has turn ON override mode where Sphere LEM + Window LEM should have RED color.

It will help with testing Kray, priority high.

Easy task.
We need to create an option for controlling Physky Sun by Lightwave Light.
The best solution is to make default Physky Sun connected with first light from Lightwave.
First (default) light from Lightwave in empty scene is LW direct light and this light should be automatically connected in GUI with Physky when user activate GUI Physky from K3. Later we can change it in Physky GUI (available LW Lights list names)
Ignore Light option in Physky GUI should be change to track light direction and have exclusion from scene. User will have easy live:
- Start Lightwave
- Open objects and create scene
- Open Kray and Physky
- Use direct light (default) in LW as control for Sun position
- Press render button

I put Critical because this option is necessary for testing.
Try not to use K3VPR - there are some refreshing bugs which I will upload soon.

We want special (fake solution) booster effect for reflection.

Background theory:
people from Maxwell and other Path Tracing render engines says that using HDRi they get better reflection on materials.
It`s happen that because HDRi has very dynamic pixels information and by this reflection effect is stronger.
Of course this is very bad solution for rendering generally and generate a lot bad photons and problems with LimitDR.

In theory solution is very easy: in GUI special global multiplayer for reflection: Range (1 —- infinite range)
1 is default.

We should have also clamps for that as second option:
reflection with low reflection level should not be boosted. Clamp should have percent level: 20% means reflection under this level are not boosted (in example scene we do not need boost floor in reflected ball)
How to make detection clamp - I leave you. Maybe 100% means maximum reflection on ball (in this case Ring over ball)
After that we will catch good level.

Scene for testing where:
- outside is sphere with LEM 500 for fake reflection (unseen by Radiosity and Unseen by Camera, so still we see Physky)You must activate/deactivate in scene editor.
- inside LEM Ring for interior reflection
We can not increase LEM Ring (it has maximum level luminosity acceptable for interior lighting)

Reflection booster will allow us to keep normal light outside interiors (exposure Physky) and gets good reflection levels which always are too weak.
Also in interiors we will get boost from LEM bulbs and other lights.

Of course this will be fake solution but I think this option will support very well future tone mapping.

Would be good to have this not as Engine Render option but like extra tone mapping feature.

This error appear sometimes and looks like light leaks.
It comes from Path Passes option.

I tried many options:
- increase/decrease GI resolution
- different Path Passes distance 10-100%
- more photons
- disable Path Passes - it helps but this is no solution for rendering (I tested normal scenes and without Path Passes looks very bad)

In Path Tracing render is correct.

Need research problem.