|
141 | Render core | Feature Request | Very High | Critical | global recurse | New | |
Task Description
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).
|
|
153 | Render core | Feature Request | Very High | Critical | Clip camera | New | |
Task Description
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)
|
|
224 | Render core | Feature Request | Very High | Critical | file buffer name extension | New | |
Task Description
Instead of K3_00000SFID.png
should be: K3_00000_SFID.png
etc
|
|
243 | LW interface | Feature Request | Very High | Critical | K3 Installer | New | |
Task Description
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
|
|
247 | Rendering | Bug Report | Very High | Very Low | Twisted Displacement | New | |
Task Description
Error with vertex direction.
|
|
316 | Rendering | Bug Report | Very High | Very Low | OCC channel | New | |
Task Description
OCC needs to be in a separate channel, if possible in real-time ON/OFF. Should contain an option to mix ambient with render: - screen - multiply - normal mode - etc
|
|
333 | Rendering | Bug Report | Very High | Very Low | K3DoF from click image region | New | |
Task Description
Update for new K3DoF feature: - clicking by mouse pointer on the K3 window render creates a new Focal Distance for DoF. - Lens F-Stop must be added to K3DoF option. In this case, LW DoF can be disabled or ignored if not needed but still must be an option for animation, etc.
|
|
335 | Rendering | Bug Report | Very High | Critical | Differences in Photon maps between LEM and Physical | Researching | |
Task Description
You can switch ON/OFF left/Right site to see how the photon map looks for LEM or from Physical lights. Use Precompute to see differences. In normal render PM+FG everything looks normal (I think because GI is blended)
|
|
195 | LW interface | Feature Request | High | Critical | Load/Save Kray config | New | |
Task Description
Probably you did not work on this yet (no GUI connections)
|
|
334 | Rendering | Bug Report | High | Medium | KrayVPR | Researching | |
Task Description
First step: make the passes more usable like big pixels reduced with time or one pass with random pixel render or something which reduce lags when camera move or scene is complex.
|
|
137 | LW interface | Feature Request | Medium | Low | Camera queue | New | |
Task Description
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
|
|
155 | Render core | Feature Request | Medium | High | motion blur buffer | New | |
Task Description
motion blur vector buffer
|
|
211 | Render core | Feature Request | Medium | Critical | Instances general switcher | New | |
Task Description
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.
|
|
242 | Render core | Feature Request | Medium | Medium | Arbitrary not working | New | |
Task Description
Arbitrary render not working in K3.
|
|
154 | Render core | Feature Request | Low | Low | volumetric buffer | New | |
Task Description
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.
|
|
213 | Rendering | Bug Report | Low | Low | override diffuse and LEM color | New | |
Task Description
This is no bug but request to finalize it and get correct one override system (left only small tweaking)
1. In override mode (scene) lamps on the wall (also LEM in windows) should have original color. Now is override by default color from plugin.
2. Materials with lower diffuse than 100 should have in override always same level for all surfaces. In this example metal sphere should be like walls.
Other options works correct.
|
|
221 | Render core | Feature Request | Low | Low | AO blending in Kray3Surface Option | New | |
Task Description
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.
|
|
248 | Rendering | Bug Report | Low | Critical | Displacement for optimization | Researching | |
Task Description
Small scene for researching Displacement optimization. Looks like in new K3 is faster, especially with the Volume System. Reuploaded scene.
The render time looks okay but the quality of Displacement is not good….even if I decrease march steps or accuracy (1 mm both, long time render)
should there be a smooth option between pixels or a similar feature for reducing the step effect?
|
|
252 | Rendering | Bug Report | Low | Low | LW2020_____IES, Spherical Light not working | New | |
Task Description
3 bugs in one:
1. CPU (attachment…do not watch first row of CPU Utilization …I have turned OFF them) 2. IES not working 3. Spherical not working
Settings: Path Tracing for fast render.
Save image works.
|
|
259 | Rendering | Bug Report | Low | Low | LW2020_____Crash | New | |
Task Description
Missing trasmission color. In new version I get also crash on start render.
|
|
283 | Rendering | Bug Report | Low | Low | Panorama in sequences | New | |
Task Description
Two bugs in one: 1/When we press render sequences in Panorama mode, Kray starts from frame 01 (instead 00) 2/When we at frame 02 and we press sequences, Kray start render from beginning of animation instead from frame 02
Works correctly only Still Image Frame Render: you are at 05 frame and Kray start with 05 frame as should be.
|
|
291 | Rendering | Bug Report | Low | Low | Power Shader Physky Sun | New | |
Task Description
Simple, please add Power Multiplayer N for Sun in Physky GUI.
|
|
308 | Rendering | Bug Report | Low | Low | Dark LightPortal | New | |
Task Description
Dark LightPortal when camera is behind.
|
|
311 | Rendering | Bug Report | Low | Low | LW2020.0.2_____Instant Crash | New | |
Task Description
Instant crash…probably two bugs inside.
|
|
203 | Render core | Feature Request | Very Low | Very Low | not working Compositing background image | New | |
Task Description
Actually never works (K2 also) I put it in feature as low priority.
|
|
205 | Render core | Feature Request | Very Low | Low | camera queue plugin | New | |
|
|
134 | Render core | Feature Request | Defer | Very Low | Ambient Intensity override mode | New | |
|
|
135 | LW interface | Feature Request | Defer | Very Low | Override LW tone mapping | New | |
|