Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
luxrender [2015/06/21 00:32]
slackermedia
luxrender [2021/06/03 19:48] (current)
Line 1: Line 1:
-[[{arrowp.png|border:​0;​background:​none;​width:​0;​display:​inline-block;​position:​absolute;​top:​0;​left:​0;​}lmms|]] 
  
-[[{arrown.png|border:​0;​background:​none;​width:​0;​display:​inline-block;​position:​absolute;​top:​0;​margin-left:​2.5em;​}mitsuba|]] 
  
 ====== LuxRender ====== ====== LuxRender ======
Line 62: Line 60:
 OpenCL increases the render speed substantially,​ but it does require sufficiently powered hardware, and for LuxRender to utilise OpenCL, you must [[opencl|enable OpenCL]] on your system. OpenCL increases the render speed substantially,​ but it does require sufficiently powered hardware, and for LuxRender to utilise OpenCL, you must [[opencl|enable OpenCL]] on your system.
  
-To compile without ​OpenCL support:+The default behaviour of the SlackBuild is to install LuxRender with OpenCL support. To disable it, start the SlackBuild with a leading ''​OPENCL=no''​ variable setting:
  
 <​code>​ <​code>​
Line 68: Line 66:
 </​code>​ </​code>​
  
-or +or, if you use ''​sport'':​
  
 <​code>​ <​code>​
Line 78: Line 76:
 ==== Blender ==== ==== Blender ====
  
 +The default behaviour of the LuxRender SlackBuild is to auto-detect whether you have Blender installed, and where its ''​script''​ directory is located, and to install the LuxRender Blender plug-in. You can forego this automatic detection process by just providing the path manually:
 +
 +<​code>​
 +$ BLENDER=/​path/​to/​blender/​scripts ./​luxrender.SlackBuild
 +</​code>​
 +
 +Or, if you would rather the Blender plug-in not be installed, set it to ''​no'':​
 +
 +<​code>​
 +$ BLENDER=no ./​luxrender.SlackBuild
 +</​code>​
 +
 +If you set ''​BLENDER=no''​ then the plugins are stored, uninstalled,​ in ''/​usr/​share/​luxrender-X.X''​.
  
  
 ===== Usage ===== ===== Usage =====
  
-LuxRender has several ​entry pointsIt can be launched ​as a shell application:​+LuxRender has several ​ways for you to interact with itTo try it out, use the ''​LuxTime''​ example stored in ''/​usr/​share/​luxrender-X.X''​. Copy the ''​LuxTime''​ directory to your home directory and then load the ''​.lxs''​ file to produce a render. 
 + 
 +LuxRender ​can be invoked ​as a shell application:​
  
 <​code>​ <​code>​
Line 88: Line 101:
 </​code>​ </​code>​
  
-It has a stand-alone GUI frontend, which you can launch from the **K Menu** or from a shell:+LuxRender ​has a stand-alone GUI frontend, which you can launch from the **K Menu** or from a shell:
  
 <​code>​ <​code>​
Line 102: Line 115:
  
 [{{ luxblend.jpg |Selecting the LuxRender engine in Blender.}}] [{{ luxblend.jpg |Selecting the LuxRender engine in Blender.}}]
- 
- 
- 
  
 <WRAP tip> <WRAP tip>
 **See Also** \\ **See Also** \\
-blender \\ +[[blender|Blender]] ​\\ 
-mitsuba \\ +[[mitsuba|Mitsuba]] ​\\ 
-povray+[[http://povray.org|Povray]] \\ 
 +[[yafaray|Yafaray]]
 </​WRAP>​ </​WRAP>​
  
- +<WRAP centeralign>​ 
-[[{arrown.png|border:​0;​background:​none;​width:​0;​display:​inline-block;​float:​right;​}mitsuba|]][[{arrowp.png|border:​0;​background:​none;​width:​0;​float:​right;​}lmms|]]+<wrap fa>[[luppp|R]]</​wrap>​ <wrap fa>​[[start|S]]</​wrap>​ <wrap fa>[[lv2rack|Q]]</​wrap>​ 
 +</​WRAP>​