<?xml version="1.0" ?>
<rdf:RDF xmlns:dc="http://purl.org/dc/elements/1.1/" 
  xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
  xmlns="http://purl.org/rss/1.0/"
  xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel rdf:about="http://www.kraytracing.com/bugtracker/">
    <title>KrayBugTracker::</title>
    <link>http://www.kraytracing.com/bugtracker/</link>
    <description>KrayBugTracker::Kray3 Feature Requests: Recently edited tasks</description>
    <dc:date>2019-02-09T11:09:17Z</dc:date>
    <items>
      <rdf:Seq>
                <rdf:li rdf:resource="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=243" />
                <rdf:li rdf:resource="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=242" />
                <rdf:li rdf:resource="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=224" />
                <rdf:li rdf:resource="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=221" />
                <rdf:li rdf:resource="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=195" />
                <rdf:li rdf:resource="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=211" />
                <rdf:li rdf:resource="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=184" />
                <rdf:li rdf:resource="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=155" />
                <rdf:li rdf:resource="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=154" />
                <rdf:li rdf:resource="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=153" />
              </rdf:Seq>
    </items>
    		
  </channel>
    <item rdf:about="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=243">
    <title>FS#243: K3 Installer</title>
    <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=243</link>
    <dc:date>2019-02-09T11:09:17Z</dc:date>
    <dc:creator>Janusz Biela</dc:creator>
     <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

</description>
    <content:encoded><![CDATA[
<p>
Some people has problem with putting correct files into LW plugin folder.<br />Installer should detect:<br />- x32/x64 system<br />- Lightwave version (if did not detect it should propose user to find correct path for installation) <br />- default folder in LW plugin folder: <strong>Kray</strong> (I think is better when Kray will have his own folder and for registration in general LW plugin folder)<br />- automatic assign K3 plugin into LW config - so user after opening LW has already installed K3 plugins.<br />- maybe <acronym title="Graphical User Interface">GUI</acronym> tab for K3 option<br />
</p>
]]></content:encoded>
  </item>
    <item rdf:about="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=242">
    <title>FS#242: Arbitrary not working</title>
    <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=242</link>
    <dc:date>2019-02-08T10:15:23Z</dc:date>
    <dc:creator>Janusz Biela</dc:creator>
     <description>

Arbitrary render not working in K3.

</description>
    <content:encoded><![CDATA[
<p>
Arbitrary render not working in K3.<br />
</p>
]]></content:encoded>
  </item>
    <item rdf:about="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=224">
    <title>FS#224: file buffer name extension </title>
    <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=224</link>
    <dc:date>2019-01-10T09:05:29Z</dc:date>
    <dc:creator>Janusz Biela</dc:creator>
     <description>

Instead ofK3_00000SFID.png



should be:K3_00000_SFID.png



etc

</description>
    <content:encoded><![CDATA[
<p>
Instead of<br /><strong>K3_00000SFID.png</strong>
</p>

<p>
should be:<br /><strong>K3_00000_SFID.png</strong>
</p>

<p>
etc
</p>
]]></content:encoded>
  </item>
    <item rdf:about="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=221">
    <title>FS#221: AO blending in Kray3Surface Option</title>
    <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=221</link>
    <dc:date>2019-01-10T09:04:42Z</dc:date>
    <dc:creator>Janusz Biela</dc:creator>
     <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.

</description>
    <content:encoded><![CDATA[
<p>
I see You added AO option to Kray3surface <acronym title="Graphical User Interface">GUI</acronym>.<br />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.
</p>

<p>
Blending (<acronym title="Graphical User Interface">GUI</acronym> option) should have normal blending when we just setup strength of blending with AO (0% - no visible effect).<br />AO intensity and distance of course remain in <acronym title="Graphical User Interface">GUI</acronym>
</p>

<p>
 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.<br />
</p>
]]></content:encoded>
  </item>
    <item rdf:about="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=195">
    <title>FS#195: Load/Save Kray config</title>
    <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=195</link>
    <dc:date>2019-01-10T09:00:45Z</dc:date>
    <dc:creator>Janusz Biela</dc:creator>
     <description>

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

</description>
    <content:encoded><![CDATA[
<p>
Probably you did not work on this yet (no <acronym title="Graphical User Interface">GUI</acronym> connections)<br />
</p>
]]></content:encoded>
  </item>
    <item rdf:about="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=211">
    <title>FS#211: Instances general switcher</title>
    <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=211</link>
    <dc:date>2019-01-10T08:59:58Z</dc:date>
    <dc:creator>Janusz Biela</dc:creator>
     <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.

</description>
    <content:encoded><![CDATA[
<p>
This is request (easy task) to create one button in Kray <acronym title="Graphical User Interface">GUI</acronym> which allow easy disable/enable all instances in scene.
</p>

<p>
Individual switcher OFF/ON works now <br />This will help a lot in rendering.<br /><strong>Default option in K3 <acronym title="Graphical User Interface">GUI</acronym> should be ON of course.</strong>
</p>

<p>
You mentioned before it should work in LW <acronym title="Graphical User Interface">GUI</acronym> - but there is some problems. So making this in K3 Core will be easy task.<br />
</p>
]]></content:encoded>
  </item>
    <item rdf:about="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=184">
    <title>FS#184: PhyskySun control and desaturate... and postprocessing</title>
    <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=184</link>
    <dc:date>2019-01-10T08:58:12Z</dc:date>
    <dc:creator>Janusz Biela</dc:creator>
     <description>

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 &amp;#8220;studio interior&amp;#8221; (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.

</description>
    <content:encoded><![CDATA[
<p>
This is not bug but very requirement feature: we need finally to have control over Physky Sun from Layout lights.<br />Solution is easy: control from direction light source from Layout (position does`t matter)<br />Second request is to have desaturate option (0-100%) for whole Physky which will allow users to render interiors like &#8220;studio interior&#8221; (I suggest to have 2x desaturation: for Physky background and Physky Sun)
</p>

<p>
So in this request, extra 3 options in <acronym title="Graphical User Interface">GUI</acronym>:<br />- control Sun position (selection light source)<br />- desaturate Sun<br />- desaturate background
</p>

<p>
 …easy task but will help a lot.<br />
</p>
]]></content:encoded>
  </item>
    <item rdf:about="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=155">
    <title>FS#155: motion blur buffer</title>
    <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=155</link>
    <dc:date>2019-01-10T08:50:12Z</dc:date>
    <dc:creator>Janusz Biela</dc:creator>
     <description>

motion blur vector buffer

</description>
    <content:encoded><![CDATA[
<p>
motion blur vector buffer
</p>
]]></content:encoded>
  </item>
    <item rdf:about="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=154">
    <title>FS#154: volumetric buffer</title>
    <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=154</link>
    <dc:date>2019-01-10T08:49:18Z</dc:date>
    <dc:creator>Janusz Biela</dc:creator>
     <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.

</description>
    <content:encoded><![CDATA[
<p>
New buffer: volumetric.
</p>

<p>
- 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. <br />(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) <br />- 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 <acronym title="Graphical User Interface">GUI</acronym> for that - better)<br />- from LEM sources: Shader <br />- if we have two Shaders activated (Physky Sun and Physical Light) we should get two file buffers.
</p>

<p>
Features has open ideas.<br />
</p>
]]></content:encoded>
  </item>
    <item rdf:about="http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=153">
    <title>FS#153: Clip camera</title>
    <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=153</link>
    <dc:date>2019-01-10T08:47:20Z</dc:date>
    <dc:creator>Janusz Biela</dc:creator>
     <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)

</description>
    <content:encoded><![CDATA[
<p>
Clip camera plugin should cut everything in scene between camera and designed range clip.
</p>

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

<p>
 <acronym title="Graphical User Interface">GUI</acronym>
</p>

<p>
- range<br />- clipped (cut) color (RGB - <acronym title="Graphical User Interface">GUI</acronym>)<br />- extra option: texture selection (cubic mapping,planar, or LW interface options)<br />
</p>
]]></content:encoded>
  </item>
  </rdf:RDF>
