Difference between revisions of "Blender"

From UFRC
Jump to navigation Jump to search
 
(27 intermediate revisions by 7 users not shown)
Line 1: Line 1:
−
{|align=right
+
[[Category:Software]][[Category:Graphics]]
−
  |__TOC__
+
{|<!--CONFIGURATION: REQUIRED-->
−
  |}
+
|{{#vardefine:app|Blender}}
−
[[Image:tux.jpg|right|Rendered version of Tux]]
+
|{{#vardefine:url|http://www.blender.org/}}
−
==Description==
+
<!--CONFIGURATION: OPTIONAL (1=ON)-->
−
Blender is an integrated suite of tools enabling the creation of a broad range of 3D content with the singular benefits of cross-platform interoperability and an incredibly small download file size. It is the most popular Open Source 3D graphics application in the world, and is one of the most downloaded.
+
|{{#vardefine:exe|1}} <!--RUNNING -->
−
==Website==
+
|{{#vardefine:conf|}} <!--CONFIGS-->
−
* Main website: [http://www.blender.org www.blender.org]
+
|{{#vardefine:pbs|}} <!--PBS SCRIPTS-->
−
* Documentation website: [http://wiki.blender.org/index.php/Manual Wiki.blender.org]
+
|{{#vardefine:policy|}} <!--POLICY-->
 +
|{{#vardefine:testing|}} <!--TESTING/PROFILING-->
 +
|{{#vardefine:faq|}} <!--FAQ-->
 +
|{{#vardefine:citation|}} <!--CITATION-->
 +
|{{#vardefine:installation|}} <!--INSTALLATION-->
 +
|{{#vardefine:tutorial|1}} <!--TUTORIAL-->
 +
|}
 +
<!--BODY-->
 +
<!--Description-->
 +
{{#if: {{#var: url}}|
 +
{{App_Description|app={{#var:app}}|url={{#var:url}}|name={{#var:app}}}}|}}
  
−
==Location==
+
3D graphics rendering
−
/apps/blender/2.44
 
−
==Usage==
 
−
Remember, the HPC computational resources are not to be used for developing the blend file! The idea is that you get the blend file ready to go, then transfer that blend file to the HPC Center and submit a job to do the rendering. This is where a good portion of the time takes place.
 
  
−
==Command Line Arguments==
+
<!--Modules-->
−
<pre>
+
==Environment Modules==
−
Blender 2.44 (sub 0) Build
+
Run <code>module spider {{#var:app}}</code> to find out what environment modules are available for this application.
−
Usage: blender [options ...] [file]
+
==System Variables==
−
 
+
* HPC_{{uc:{{#var:app}}}}_DIR - installation directory
−
Render options:
+
<!--Additional-->
−
  -b <file>    Render <file> in background
+
{{#if: {{#var: exe}}|==Additional Information==
−
    -S <name>  Set scene <name>
+
* Note: The server hardware that this will run on does not have any audio hardware built in, nor would it be audible since the hardware is installed in a separate room. As such, the blender command has been aliased so that the "'''-noaudio'''" flag is automatic.
−
    -f <frame>  Render frame <frame> and save it
+
|}}
−
    -s <frame>  Set start to frame <frame> (use with -a)
+
<!--Configuration-->
−
    -e <frame>  Set end to frame (use with -a)<frame>
+
{{#if: {{#var: conf}}|==Configuration==
−
    -o <path>  Set the render path and file name.
+
See the [[{{PAGENAME}}_Configuration]] page for {{#var: app}} configuration details.
−
      Use // at the start of the path to
+
|}}
−
        render relative to the blend file.
+
<!--PBS scripts-->
−
      Use # in the filename to be replaced with the frame number
+
{{#if: {{#var: pbs}}|==PBS Script Examples==
−
      eg: blender -b foobar.blend -o //render_# -F PNG -x 1
+
See the [[{{PAGENAME}}_PBS]] page for {{#var: app}} PBS script examples.|}}
−
    -F <format> Set the render format, Valid options are..
+
<!--Policy-->
−
        TGA IRIS HAMX FTYPE JPEG MOVIE IRIZ RAWTGA
+
{{#if: {{#var: policy}}|==Usage Policy==
−
        AVIRAW AVIJPEG PNG BMP FRAMESERVER
+
WRITE USAGE POLICY HERE (perhaps templates for a couple of main licensing schemes can be used)
−
    (formats that can be compiled into blender, not available on all systems)
+
|}}
−
        HDR TIFF EXR MPEG AVICODEC QUICKTIME CINEON DPX
+
<!--Performance-->
−
    -x <bool>  Set option to add the file extension to the end of the file.
+
{{#if: {{#var: testing}}|==Performance==
−
    -t <threads>       Use amount of <threads> for rendering
+
DOUBLE_CLICK_TO_WRITE_PERFORMANCE_TESTING_RESULTS_HERE
−
 
+
|}}
−
Animation options:
+
<!--Faq-->
−
  -a <file(s)>  Playback <file(s)>
+
{{#if: {{#var: faq}}|==FAQ==
−
    -p <sx> <sy>        Open with lower left corner at <sx>, <sy>
+
*'''Q:''' **'''A:'''|}}
−
    -m          Read from disk (Don't buffer)
+
<!--Citation-->
−
 
+
{{#if: {{#var: citation}}|==Citation==
−
Window options:
+
If you publish research that uses {{#var:app}} you have to cite it as follows:
−
  -w            Force opening with borders (default)
+
DOUBLE_CLICK_TO_WRITE_CITATION_HERE
−
  -W            Force opening without borders
+
|}}
−
  -p <sx> <sy> <w> <h>  Open with lower left corner at <sx>, <sy>
+
<!--Installation-->
−
                        and width and height <w>, <h>
+
{{#if: {{#var: installation}}|==Installation==
−
 
+
See the [[{{PAGENAME}}_Install]] page for {{#var: app}} installation notes.|}}
−
Game Engine specific options:
+
<!--Tutorial-->
−
  -g fixedtime          Run on 50 hertz without dropping frames
+
{{#if: {{#var: tutorial}}|==Tutorial==
−
  -g vertexarrays      Use Vertex Arrays for rendering (usually faster)
+
* There are a number of different tutorials on the [http://www.blender.org/support/tutorials/ Blender Tutorial] webpage.
−
  -g noaudio            No audio in Game Engine
+
|}}
−
  -g nomipmap          No Texture Mipmapping
+
__NOTOC____NOEDITSECTION__
−
  -g linearmipmap      Linear Texture Mipmapping instead of Nearest (default)
 
−
 
 
−
Misc options:
 
−
  -d            Turn debugging on
 
−
  -noaudio      Disable audio on systems that support audio
 
−
  -h            Print this help text
 
−
  -y            Disable script links, use -Y to find out why its -y
 
−
  -P <filename> Run the given Python script (filename or Blender Text)
 
−
  -v            Print Blender version and exit
 
−
</pre>
 
−
As a note, all attempts so far to get the -o OUTPUTFILE option to work have been unsuccessful. Please be sure to define the output file location in the blend file itself.
 
−
 
 
−
==Sample Script==
 
−
<pre>
 
−
#!/bin/csh -f
 
−
#
 
−
#PBS -N tux
 
−
#PBS -r n
 
−
#PBS -o tux.out
 
−
#PBS -e tux.err
 
−
#PBS -j oe
 
−
#PBS -m abe
 
−
#PBS -M <ADD EMAIL ADDRESS HERE!>
 
−
#PBS -l nodes=1:ppn=2
 
−
#PBS -l pmem=400mb
 
−
#PBS -l walltime=2:00:00
 
−
 
 
−
 
 
−
set EXE = /apps/blender/2.44/blender
 
−
 
 
−
cd /home/jka/
 
−
$EXE -b Tux.blend -f 1 -x 1 -t 2
 
−
</pre>
 
−
Note that you should add your address to the appropriate line in this case. Also note that the walltime has been set to 2 hours. You will have to figure out through trial and error what the most appropriate amount of time for a rendering should be. In this particular example:
 
−
* Blender will render the first frame of either a static or dynamic animation.
 
−
* It will use two threads to perform this operation, hence defining that PBS should use two processors on a single node.
 
−
** With preliminary testing, this also does not appear to be working properly. There is a setting within the rendering options in Blender itself that you can set the number of threads to work from. I recommend setting this to four, and defining the ppn above to four as well.  
 
−
* The output of the frame will be wherever it was defined in the blend file that was originally saved.
 
−
 
 
−
Setting the proper path for the output in the blend file is '''critical''', as this is a batch based system and you will have no idea which computational node actually does the processing. Be sure to set the output path to a known location in the global filesystem, either /scratch/ufhpc or /home/<username>. The default in linux is to set this to /tmp, which will simply dump the output to that directory on the local computational node, which means you will not get the results.
 

Latest revision as of 13:03, 15 August 2022

Description

Blender website  

3D graphics rendering

Environment Modules

Run module spider Blender to find out what environment modules are available for this application.

System Variables

  • HPC_BLENDER_DIR - installation directory

Additional Information

  • Note: The server hardware that this will run on does not have any audio hardware built in, nor would it be audible since the hardware is installed in a separate room. As such, the blender command has been aliased so that the "-noaudio" flag is automatic.




Tutorial

Retrieved from "https://help.rc.ufl.edu/mediawiki/index.php?title=Blender&oldid=25112"