<?xml version="1.0" ?>
<rss version="2.0">
  <channel>
    <title>KrayBugTracker::</title>
    <lastBuildDate>Sat, 09 Feb 2019 11:09:17 +0000</lastBuildDate>
    <description>KrayBugTracker::Kray3 Feature Requests: Recently edited tasks</description>
    <link>http://www.kraytracing.com/bugtracker/</link>
        <item>
      <title>FS#243: K3 Installer</title>
      <author>Janusz Biela</author>
      <pubDate>Sat, 09 Feb 2019 11:09:17 +0000</pubDate>
      <description><![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>
]]></description>
      <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=243</link>
      <guid>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=243</guid>
    </item>
        <item>
      <title>FS#242: Arbitrary not working</title>
      <author>Janusz Biela</author>
      <pubDate>Fri, 08 Feb 2019 10:15:23 +0000</pubDate>
      <description><![CDATA[
<p>
Arbitrary render not working in K3.<br />
</p>
]]></description>
      <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=242</link>
      <guid>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=242</guid>
    </item>
        <item>
      <title>FS#224: file buffer name extension </title>
      <author>Janusz Biela</author>
      <pubDate>Mon, 29 Oct 2018 18:04:10 +0000</pubDate>
      <description><![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>
]]></description>
      <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=224</link>
      <guid>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=224</guid>
    </item>
        <item>
      <title>FS#221: AO blending in Kray3Surface Option</title>
      <author>Janusz Biela</author>
      <pubDate>Fri, 19 Oct 2018 08:48:19 +0000</pubDate>
      <description><![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>
]]></description>
      <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=221</link>
      <guid>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=221</guid>
    </item>
        <item>
      <title>FS#195: Load/Save Kray config</title>
      <author>Janusz Biela</author>
      <pubDate>Wed, 11 Jul 2018 16:28:10 +0000</pubDate>
      <description><![CDATA[
<p>
Probably you did not work on this yet (no <acronym title="Graphical User Interface">GUI</acronym> connections)<br />
</p>
]]></description>
      <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=195</link>
      <guid>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=195</guid>
    </item>
        <item>
      <title>FS#211: Instances general switcher</title>
      <author>Janusz Biela</author>
      <pubDate>Sun, 12 Aug 2018 12:59:04 +0000</pubDate>
      <description><![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>
]]></description>
      <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=211</link>
      <guid>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=211</guid>
    </item>
        <item>
      <title>FS#184: PhyskySun control and desaturate... and postprocessing</title>
      <author>Janusz Biela</author>
      <pubDate>Wed, 20 Jun 2018 06:32:49 +0000</pubDate>
      <description><![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>
]]></description>
      <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=184</link>
      <guid>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=184</guid>
    </item>
        <item>
      <title>FS#155: motion blur buffer</title>
      <author>Janusz Biela</author>
      <pubDate>Fri, 24 Nov 2017 10:18:17 +0000</pubDate>
      <description><![CDATA[
<p>
motion blur vector buffer
</p>
]]></description>
      <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=155</link>
      <guid>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=155</guid>
    </item>
        <item>
      <title>FS#154: volumetric buffer</title>
      <author>Janusz Biela</author>
      <pubDate>Fri, 24 Nov 2017 10:03:28 +0000</pubDate>
      <description><![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>
]]></description>
      <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=154</link>
      <guid>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=154</guid>
    </item>
        <item>
      <title>FS#153: Clip camera</title>
      <author>Janusz Biela</author>
      <pubDate>Fri, 24 Nov 2017 09:46:40 +0000</pubDate>
      <description><![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>
]]></description>
      <link>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=153</link>
      <guid>http://www.kraytracing.com/bugtracker/index.php?do=details&amp;task_id=153</guid>
    </item>
      </channel>
</rss>
