Differences

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

--- luxrender [2015/06/21 00:06]
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 ======
@@ Line 54: / Line 52: @@
 To get the basic Luxrender package installed, first install its dependencies; all of them are available from [[http://slackbuilds.org]] but some (like OpenCL) are optional.
-Once the dependencies are installed, install Luxrender from [[http://slackbuilds.org]]. This also installs the Blender package.
+Once the dependencies are installed, install Luxrender from [[http://slackbuilds.org]].
-To compile without OpenCL support:
+==== OpenCL ====
+OpenCL is an open specification that enables a system to access and recruit any computing device for the computational workload. In practise, that usually means the graphics card (GPU) but in theory it could include more.
+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.
+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>
@@ Line 62: / Line 66: @@
 </code>
-or
+or, if you use ''sport'':
 <code>
@@ Line 68: / Line 72: @@
 </code>
-If you do not know what OpenCL is, you probably do not need it. If you do know what it is and want to use it, then you must follow the instructions in the OpenCL SlackBuild to ensure that OpenCL is enabled on your system.
+If you do not know what OpenCL is, you probably do not //need// it.
+==== 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 =====
-LuxRender has several entry points. It can be launched as a shell application:
+LuxRender has several ways for you to interact with it. To 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>
@@ Line 78: / Line 101: @@
 </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>
@@ Line 84: / Line 107: @@
 </code>
-{{ luxrender.jpg?666 }}
+[{{ luxrender.jpg?666 |The LuxRender GUI rendering an image by **freejack**.}}]
 And finally, the Blender plugin, which can be activated and used the same as any other Blender plugin:
@@ Line 91: / Line 114: @@
   - Make it your active renderer in the *Info* panel
-{{ luxblend.jpg }}
+[{{ luxblend.jpg |Selecting the LuxRender engine in Blender.}}]
 <WRAP tip>
 **See Also** \\
-blender \\
+[[blender|Blender]] \\
-mitsuba \\
+[[mitsuba|Mitsuba]] \\
-povray
+[[http://povray.org|Povray]] \\
+[[yafaray|Yafaray]]
 </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>