Kray3 Feature Requests

Some people has problem with putting correct files into LW plugin folder.
Installer should detect:
- x32/x64 system
- Lightwave version (if did not detect it should propose user to find correct path for installation)
- default folder in LW plugin folder: Kray (I think is better when Kray will have his own folder and for registration in general LW plugin folder)
- automatic assign K3 plugin into LW config - so user after opening LW has already installed K3 plugins.
- maybe GUI tab for K3 option

Arbitrary render not working in K3.

Instead of
K3_00000SFID.png

should be:
K3_00000_SFID.png

etc

I see You added AO option to Kray3surface GUI.
Now we should have option which allow us blend AO with normal GI render by percentage. I am not sure what would be better: multiply or screen or other blending system.

Blending (GUI option) should have normal blending when we just setup strength of blending with AO (0% - no visible effect).
AO intensity and distance of course remain in GUI

Option is really useful for rendering to vivid details shadow in renders especially in animation with Final Gathering when we do not need so detailed GI.

This is request (easy task) to create one button in Kray GUI which allow easy disable/enable all instances in scene.

Individual switcher OFF/ON works now
This will help a lot in rendering.
Default option in K3 GUI should be ON of course.

You mentioned before it should work in LW GUI - but there is some problems. So making this in K3 Core will be easy task.

This is request which is very much missing (like Sun Physky control from layout).
Simple Kray3Queue which allow user to select camera and render them all without user interaction.
Plugin should contain:
- list of camera from layout which we can select and render
- frame range (0-0, 5-5 means render only one frame)

Each camera shoots it`s own photons.

Actually never works (K2 also) I put it in feature as low priority.

Probably you did not work on this yet (no GUI connections)

motion blur vector buffer

New buffer: volumetric.

- In Physky extra activation option , effect from Physky Sun (it should render extra buffer without activated buffers from KrayBuffer plugin)...we must decide how to deal with this.
(should be detection also what range - up you you how you will deal with this not to get too strong or too weak effect in buffer)
- from physical lights Shader (should be detection what range - up you you how you will deal with this - maybe just formula connected with power of light so will be no GUI for that - better)
- from LEM sources: Shader
- if we have two Shaders activated (Physky Sun and Physical Light) we should get two file buffers.

Features has open ideas.

Clip camera plugin should cut everything in scene between camera and designed range clip.

- range in meters (ex: 1.0, 1.4, 5.33)
- clipped region must be excluded from camera visible but not from render (unseen by camera only)
- clipped object must be filled by user designed color if possible...no idea how to deal with open object - your task :D
- clipped color 100% luminosity unseen by radiosity
- extra option: texture instead color

GUI

- range
- clipped (cut) color (RGB - GUI)
- extra option: texture selection (cubic mapping,planar, or LW interface options)

We need glob option for recurse amount.
Since recurse 40 is optimum amount of bounce lights to get optimal photon map we need reduce amount of reflection recurse by global option.
This must be GUI option (0-infinite, default 4)which gives control over that.

Reflection recurse 4 seems optimum.

To avoid deep recurse problem in reflected surfaces we need use now Limiter in Node (bad idea and only one which solve problem right now)

GUI option should contain also fail recurse color (so instead getting black we should have option to choose color)
Also (I leave idea for you) instead color we could make fake reflection map instead color. So we can get even image there!

Scene for testing.
We should use sett recurse 40 (as global option for photons) but effect with new function should gives us sett recurse 5 (target).

One of the most important features: Camera queue interface.
GUI Interface should have selection:
- camera selection list (user can choose which camera will be render in queue, can be cam02, cam01, cam03)
- frame range (for example 05-20) for each camera separately
- Z-buffer range (for example 2-5 m) for each camera separately - this option can be ON/OFF

Buffer render independently - no need GUI for this option.

Scene for testing with 3 cams.

Image save system - if this option is selected:

(Camera name)_(file name)_(frame number)_(image format)

example:
Camerabathroom_shopcenter_0001.png and buffers:
Camerabathroom_shopcenter_0001_SFID.png

...it will protect users from making mistakes by mixing tone maps.
Sometimes users use project done in LW native render engine and when they switch to K3 they should disable tone mapping from LW.

Procedures for testing:
- run normal render (no VPR because we do not see LW affecting VPR render...I do not know why)
- use LW tone map settings to see effect

Ambient Intensity from Lightwave GUI should be overridden automatically in K3 with value zero. No need to have information about that when we start Kray.
Even if we leave Ambient Intensity on - still Kray should ignore this.
...you can leave small gate for users like small command for activate (there are some very rare situations when user need this option)

Procedures from scene:
- run K3VPR
- Ambient Intensity has value 30%

Target: render should be black (no other lights in scene)