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
mitsuba [2015/06/21 00:17]
slackermedia
mitsuba [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;​}luxrender|]] 
  
-[[{arrown.png|border:​0;​background:​none;​width:​0;​display:​inline-block;​position:​absolute;​top:​0;​margin-left:​2.5em;​}mixxx|]] 
  
 ====== Mitsuba ====== ====== Mitsuba ======
Line 7: Line 5:
 [[http://​www.mitsuba-renderer.org|Mitsuba]] is a GPLv3 research-oriented rendering system in the style of physically-based rendering technology. It is written in C++, implements unbiased as well as biased techniques, ​ and contains heavy optimizations targeted towards current CPU architectures. ​ [[http://​www.mitsuba-renderer.org|Mitsuba]] is a GPLv3 research-oriented rendering system in the style of physically-based rendering technology. It is written in C++, implements unbiased as well as biased techniques, ​ and contains heavy optimizations targeted towards current CPU architectures. ​
  
-It is experimental by its own mission statement, so it may not be a rendering engine ​you want to use exclusively, but its code has been used as a basis for some very important engines, and the render results speak for themselves. +It is experimental by its own mission statement, so it is not a rendering engine ​for everyday ​use without testing, but its code has been used as a basis for some very important engines, and the render results speak for themselves.
  
 <WRAP notice prewrap 50%> <WRAP notice prewrap 50%>
Line 18: Line 15:
  
 <WRAP indent> <WRAP indent>
-Mitsuba has not only all the usual features of modern render engines, but it maintains a lead ahead of others due to its commitment to experimentation.+Mitsuba has not only all the usual features of modern render engines, but it maintains a lead ahead of others due to its commitment to experimentation. It features important advances in ambient occlusion, direct illumination,​ photon mapping, particle tracing, instant radiosity, and much more.
 </​WRAP>​ </​WRAP>​
  
Line 40: Line 37:
 ===== Install ===== ===== Install =====
  
-Installing ​Luxrender ​broadly requires, like other renderers, the installation of the Luxrender ​base package, and then the plugin that will make it useful in your application of choice (probably [[blender]]).+Installing ​Mitsuba ​broadly requires, like other renderers, the installation of the Mitsuba ​base package, and then the plugin that will make it useful in your application of choice (probably [[blender]]).
  
-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.+To get the basic Mitsuba ​package installed, first install its dependencies;​ all of them are available from [[http://​slackbuilds.org]].
  
-Once the dependencies are installed, install ​Luxrender ​from [[http://​slackbuilds.org]].+Once the dependencies are installed, install ​Mitsuba ​from [[http://​slackbuilds.org]].
  
-==== OpenCL ​====+==== OpenGL (libGLEW) ​====
  
 +Mitsuba requires ''​libglewmx''​. While Slackware ships with ''​GLEW'',​ it has not been compiled to include ''​libglewmx''​ (Slackermedia sent a patch to Slackware, so ''​libglewmx''​ will be included in the next version), so you will have to re-compile and re-install it manually.
  
-To compile and install ​LuxRender without OpenCL support:+To do this, get the ''​glew''​ SlackBuild from your install ​disc (it is in the ''​x''​ series) or download it from your nearest Slackware mirror (for example, [[ftp://​ftp.osuosl.org/​pub/​slackware/​slackware-14.1/​source/​x]]). Download the ''​glew''​ source code. 
 + 
 +Change the ''​make''​ line in the SlackBuild to:
  
 <​code>​ <​code>​
-OPENCL=no ./luxrender.SlackBuild+make install.all GLEW_DEST=$PKG/usr
 </​code>​ </​code>​
  
-or +Remove the old version of ''​glew''​ and install the new version with ''​upgradepkg'':​
  
 <​code>​ <​code>​
-$ OPENCL=no sport i luxrender+# upgradepkg --install-new \ 
 +--reinstall /​tmp/​glew*tgz
 </​code>​ </​code>​
  
-If you do not know what OpenCL isyou probably do not need itIf 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.+<WRAP alert> 
 +Install only the //same version// of ''​glew''​ as the version that Slackware ships with. If you impulsively decide to upgrade to later GLEW codethen other packages using ''​libglew''​ could break, since they have been built to look for a specific version and, after your new install, they will not be able to find them. 
 +\\  
 +Sometimes repairing a missing library ​is as easy as lying to your system: 
 +\\  
 +<​code>​ 
 +ln -s /​usr/​lib64/​libGLEW.so.1.12 /​usr/​lib64/​libGLEW.so.1.9 
 +</​code>​ 
 +\\  
 +This often fixes the problem, but theoretically ​it can cause less obvious problems in the application wanting the older version of the libraryespecially if something important has changed between ​the old version and the new version, so it's best to avoid situations like this. 
 +</​WRAP>​
  
-The LuxRender ​package ​+Confirm that ''​libglewmx''​ support has been built. If nothing is returned, then ''​glewmx''​ is still missing. Otherwise, the install was a success: 
 + 
 +<​code>​ 
 +$ grep glewmx /​var/​log/​packages/​glew-X.Y.Z-x86_64  
 +usr/​lib64/​pkgconfig/​glewmx.pc 
 +</​code>​ 
 + 
 +Once all dependencies and the ''​glew''​ patch has been made, install Mitsuba. 
 + 
 +==== Blender ==== 
 + 
 +If you intend to use Mitsuba with Blender, install the Mitsuba-blender ​package ​from SlackBuilds.org
  
 ===== Usage ===== ===== Usage =====
  
-LuxRender ​has several entry points. It can be launched as a shell application:​+Mitsuba ​has several entry points. It can be launched as a shell application:​
  
 <​code>​ <​code>​
-luxconsole ​/​path/​to/​file.lxs+mitsuba ​/​path/​to/​file.xml -o render.exr
 </​code>​ </​code>​
  
Line 76: Line 98:
  
 <​code>​ <​code>​
-luxrender&+mtsgui&
 </​code>​ </​code>​
  
-{{ luxrender.jpg?666 }}+{{ mtsgui.jpg?666 }}
  
 And finally, the Blender plugin, which can be activated and used the same as any other Blender plugin: And finally, the Blender plugin, which can be activated and used the same as any other Blender plugin:
Line 86: Line 108:
   - Make it your active renderer in the *Info* panel   - Make it your active renderer in the *Info* panel
  
-{{ luxblend.jpg }} +[{{ mtsblend.jpg | Use an alternate render engine for Blender. ​}}]
- +
  
  
 <WRAP tip> <WRAP tip>
 **See Also** \\ **See Also** \\
-blender \\ +[[blender|Blender]] ​\\ 
-mitsuba ​\\ +[[http://​povray.org|Povray]] ​\\ 
-povray+[[yafaray|Yafaray]] \\ 
 +[[luxrender|Luxrender]]
 </​WRAP>​ </​WRAP>​
  
- +<WRAP centeralign>​ 
-[[{arrown.png|border:​0;​background:​none;​width:​0;​display:​inline-block;​float:​right;​}mixxx|]][[{arrowp.png|border:​0;​background:​none;​width:​0;​float:​right;​}luxrender|]]+<wrap fa>[[milkytracker|R]]</​wrap>​ <wrap fa>​[[start|S]]</​wrap>​ <wrap fa>[[mixxx|Q]]</​wrap>​ 
 +</​WRAP>​