RENDERMAN 22 DOCUMENTATION

Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Minimum System Requirements

The following operating systems are supported for this release. RenderMan may operate outside of this requirement, but it may be unstable and is not supported:

  • Linux CentOS  6 and higherCompatible with any Linux distribution supporting gcc 4.4.5 and glibc 2.12 or higher (e.g. RHEL6 and newer)

RenderMan is designed to efficiently scale across many CPU cores, so while the above is a minimum requirement, systems with multiple processors will see the best performance.

...

The flavor string includes the common distribution, e.g. RHEL6, the gcc/icc versions, and the microprocessor instruction set. Putting them all together provides, for example, a Linux CentOS an RHEL package named RenderMan-Installer-21.0_1590950-linuxRHEL6_gcc44icc150.x86_64.rpm.

Note

Note that users must set their environment variables manually on Linux to allow for using executables from a terminal window. This process is explained below Command Line Installation.

The following additional requirements must be met (depending on which product you are using RenderMan with):

  • All: CPU capable of running the full SSE4 instruction set.
  • Maya: Compatible with 2017, 2016.5, 2016 & 2015
  • Katana: Compatible with 2.0, 2.1, 2.2, and 2.5

GUI-based Installation

Carousel Image Slider
infinitefalse
sliderHeight350
labelsFilterinstallersteps
slidesToScroll2
slidesToShow2

Command Line Installation

The software can also be installed via command line using a terminal window. You must obtain the .pkg files using your forum login.

 

Installing to the default location

...

Although RPM packages are typically installed via command line, some Linux distributions have GUI-based package managers, like gnomerpm. Some distributions will also allow for double-clicking the RPM file in a directory browser, which will invoke RPM with default arguments.

 

During the installation process, you will first be given a chance to select a root directory. By default, this location is /Applications/Pixar This will become the root directory for all of the software components listed above.

. You can try this with your Linux-based system. Should it not begin the installation on its own (because you do not have the necessary components to double click an .rpm) then you may begin the process using the steps below.


Code Block
themeConfluence

...

rpm 

...

-

...

ivh 

...

For example:

...

themeConfluence

...

RenderMan-Installer-21.0_1590950-

...

linuxRHEL6_

...

gcc44icc150.x86_64.

...

 

Installing to a drive other than /

To install the packages to a different drive, the / target of the default path can be replaced. For example, to install to a second disk/Volumes/HD2/, from a root shell type:

rpm


If you have already unpacked the .rpm, you can then run the following command to begin the GUI-based installer:

 

 

Code Block
themeConfluence

...

> installer -pkg RenderManProServer-21.0-osxLion_gcc44icc121.x86_64.pkg -target /Volumes/HD2

Setting Up the User's Environment

Environment Variables

There are several environment variables that users should set. These can be added to your .cshrc, .tcshrc (or other startup) file, like so:

setenv RMANTREE /Applications/Pixar/RenderManProServer-21.0

or, if you are using bash:

export RMANTREE=/Applications/Pixar/RenderManProServer-21.0

The following environment variables are recommended:

  • RMANTREE - establishes the location of your PRMan distribution.
  • RMANFB - establishes your framebuffer display program.
  • path - establishes the searchpath for the execution of programs, this probably already exists, so it is just a matter of adding $RMANTREE/bin to your path.
  • RDIR - specifies a directory where additional configuration files can be found, e.g. a site-specific rendermn.ini file.

Systems administrators may also choose to use the PIXAR_LICENSE_FILE variable to point to their software license, in lieu of using the defaults, or may point to an arbitrary location for their license via the /licenseserver preference in their own custom, site-specific .inifiles, and absolutely should not add that preference to a factory-shipped .ini.

RenderMan for Maya users should consult the RenderMan for Maya (RfM) documentation for more information about RfM-specific environment variables.

 

If you wish to use a location other than the default for your pixar.license file, you can optionally set a PIXAR_LICENSE_FILE environment variable to point to an arbitrary location.

 

Note
We highly recommend that, rather than editing the rendermn.ini file in your installation directory ($RMANTREE/etc), you create a duplicate file containing your site-specific overrides and place it in a separate directory, referenced via an $RDIR environment variable
sudo /opt/pixar/RenderMan-Installer/bin/RenderManInstaller

 

The installer will connect with the RenderMan Pixar Server and download your licensed components. During the installation process you will see that the default location for installation is /opt/pixar This will become the root directory for all of the software components listed above.

We'll no go step by step through the process. First you must login with your forum account and provide the serial number for the license you have purchased.

Image Added

Next you may see the following if you are installing on a floating license server for the FIRST time:

 Image Added 

This is telling you that the installer is about to key your license server to the host you are running the installer on.

Warning

If this is NOT the machine you want to run your license server on, press the Cancel button and re-run the installer on the machine you want to designate as the license server.

If you decide to make this machine your license server or you are installing a node-locked license, the installer will then contact Pixar and retrieve your license file. It will place this license file by default in:

  • Windows: C:\Program Files\Pixar\pixar.license
  • macOS:  /Applications/Pixar/pixar.license
  • Linux: /opt/pixar/pixar.license

Next you will see a list of packages you wish to install. 

Image Added

The installer will try to find the appropriate plugins to install as well. However if it cannot find a Maya installation or determines you have already installed the latest version of the software, you will give you a warning that something strange is afoot.

Here you can now decide which software and packages you wish to install. For instance if you do not wish to install the Katana plugins, you can deselect those. If you WOULD like to instal the license server for a floating license installation, you may select the "Show All" button and select the license server package as well. Installing The License Server talks in detail about the steps that must be taken on each platform once the installation finishes to ensure that the floating license server is functioning correctly.

Once the desired packages are selected, hitting the Next button goes to the download and installation phase.

Image Added

Once this phase is complete a Success! screen should appear. At this point you can exit the installer.

Image Added

Warning

When the installer is finished, the floating license service has NOT BEEN INSTALLED or STARTED.

Linux License Server goes over all the details for installing and starting the floating license services.

 

Downloads

Other types of files besides RenderMan, the License Server and the DCC plugins can be downloaded with the installer as well. These include the RenderMan Examples. These will be placed in the user who ran the RenderManInstaller Download directory.

Python

If you plan to take advantage of the Python binding you will need to download Python installer from www.python.org. RenderMan Pro Server 21 binding is compatible with 2.7, 3.4, or 3.5.

Help

If you require further assistance, please check out the RenderMan Support Forum. Note that registration is required.

...