Frequently Asked Questions

Installation and Upgrade

After I installed EnFuzion3D, the user interface is unresponsive, what’s wrong?

When the EnFuzion3D Desktop UI is unresponsive, it sometimes means that the EnFuzion3D Control Root is not running. To check this,

  • Open a browser
  • Type in the URL http://<IP address of the Control Root Computer>/10101

If the Web page does not come up, then proceed to the FAQ section on Control Root Configuration for more troubleshooting tips.

Do I need administrative rights to install EnFuzion3D?

Yes.  You need administrative rights to install and run EnFuzion3D on the Control Root Computer and the Compute Nodes.  You also need administrative rights to install EnFuzion3D on User Submit Computers, but artists will not need administrative rights to run EnFuzion3D on their workstations after it is installed.   

Axceleon provides very detailed descriptions on this topic in the EnFuzion3D Installation Guide.  Please consult the product documentation for full details.

During installation on Windows I get the following error message: “Unable to execute file C:\EnFuzion3d\bin\enfstartup CreateProcess failed; Code 740. The requested operation requires elevation.” What does it mean ?

To install EnFuzion3D on a Windows-based computer, you need to have administrative rights, and run the installer program using the Run as administrator option. This is described in EnFuzion3D Installation Guide.  If you run into this error, please exit the installer, find the directions in the EnFuzion3D Installation Guide and try again by following the directions exactly.

How do I batch install all of my render nodes and workstations?

Axceleon offers a separate batch installer that you can use to batch install EnFuzoin3D on your render nodes and artist workstations. Please email support@axceleon.com to request it.

How do I push configuration files to all of my render nodes?

Just as you can use EnFuzion3D to distribute frames to render nodes for rendering, you can also use EnFuzion3D to push configurations out to render nodes and artist workstation in batch mode. Please email support@axceleon.com so we can help you to do this.

How do I uninstall EnFuzion3D on OS X?

Please note that there is no need to uninstall EnFuzion3D prior to an upgrade, unless you are specifically told otherwise by Axceleon.

To uninstall EnFuzion3D on the User Submit Computers:

  • Delete the enfuzion directory from the computer user’s home directory. For example, for a user called bob, you need to delete the /Users/bob/enfuzion

To uninstall EnFuzion3D on the Control Root Computer:

  • Using the Activity Monitor, locate the processes called enfdispatcher and enfeye, and choose Quit Process to stop both processes.
  • Delete the enfuzion directory from the admin user’s home directory, i.e. the /Users/admin/enfuzion directory.
  • Delete the /Library/StartupItems/EnFuzion3D

To uninstall EnFuzion3D on the Compute Nodes:

  • Using the Activity Monitor, locate the process called enfnodeserver and use Quit Process to stop it.
  • Delete the enfuzion directory from the admin user’s home directory, i.e. the /Users/admin/enfuzion

Delete the /Library/StartupItems/EnFuzionNode directory.

How do I uninstall EnFuzion3D on Windows?

Please note that there is no need to uninstall EnFuzion3D prior to an upgrade, unless Axceleon specifically tells you otherwise.

To uninstall EnFuzion3D on the User Submit Computers:

  • Choose Windows->Start->All Programs->EnFuzion->Uninstall EnFuzion.

To uninstall EnFuzion3D on the Control Root Computer:

  • Choose Windows->Start->All Programs->EnFuzion->Control Root Utilities->Stop EnFuzion Root Service,
  • Choose Windows->Start->All Programs->EnFuzion->Control Root Utilities->Unregister EnFuzion Root Service, and
  • Choose Windows->Start->All Programs->EnFuzion->Uninstall EnFuzion.

To uninstall EnFuzion3D on the Compute Nodes:

  • Choose Windows->Start->All Programs->EnFuzion->Compute Node Utilities->Stop EnFuzion Node Service,
  • Choose Windows->Start->All Programs->EnFuzion->Compute Node Utilities->Unregister EnFuzion Node Service, and
  • Choose Windows->Start->All Programs->EnFuzion->Uninstall EnFuzion.

 

How much disk space is required by EnFuzion3D?

EnFuzion3D executables are less than 20MB in size. Because EnFuzion doesn’t require other software packages, patches, or external databases to run, you don’t need to add additional disk space for EnFuzion3D on most workstations and render nodes.

For the machine you use as your Control Root Computer, because it holds extensive log files for your render farm, we suggest that you have at least 100MB of disk space available to start, and adjust the disk space as needed.

I have been using EnFuzion3D, do I choose Upgrade or New Installation to update my software?

In this situation, we strongly recommend that you choose the Upgrade option. This option will preserve your current working environment, including your license file, the Work directory, and all the submission information, allowing a completely controlled migration.  Please refer to the EnFuzion3D Installation Guide for more detail on how to plan and carry out an upgrade of EnFuzion3D software on your render farm.

What is the quickest way to install and try EnFuzion3D?

It takes less than 5 minutes to create a one-machine render farm, making it the quickest way to try out EnFuzion3D.  Please refer to the EnFuzion3D Installation Guide for directions on how to do this.

What user account should I install EnFuzion3D under?

For the Control Root Computer, you must install EnFuzion3D using an account with administrative rights.

On Compute Nodes, you must install EnFuzion3D using an account with administrative rights. Furthermore, we strongly recommend that you install EnFuzion3D to run using the same account as what your rendering software (e.g. Maya) uses.  Please note that EnFuzion3D will also require administrative right to execute on Compute Nodes.

On User Submit Computers, you must install EnFuzion3D using an account with administrative rights, but once EnFuzion3D is installed, an artists does not need administrative rights to run it.

Please refer to the EnFuzion3D Installation Guide for full details.

What Windows UAC level an EnFuzion3D run at?

EnFuzion3D can run at any Windows UAC level if you install EnFuzion3D by following the steps we provide in the EnFuzion3D Installation Guide.

What’s the system requirements for running EnFuzion3D?

EnFuzion3D has no special system requirements to run on supported versions of Windows, OS X and Linux operating systems.  Any computer deemed adequate for running 3D applications is adequate for running EnFuzion3D.

The machine chosen to be the Control Root Computer on your render farm needs to run all the time, and it needs to have a static IP address.

 

Control Root Configuration

How do I configure a Linux based EnFuzion root computer to start EnFuzion at boot time?

Verify that the EnFuzion startup script is installed. The script is in the file /etc/init.d/EnFuzion.

If the file /etc/init.d/EnFuzion does not exist, go to the directory with an unpacked EnFuzion distribution, log in as a root user and execute:
./install-service

If the file /etc/init.d/EnFuzion exists, verify that EnFuzion is on the list of services that are started at the boot time. Execute the command:
chkconfig –list | grep EnFuzion
Output should include several on levels:
EnFuzion 0:off 1:off 2:on 3:on 4:on 5:on 6:off

To start EnFuzion, execute the following command line:
/etc/init.d/EnFuzion start

How do I configure a Mac OS X based EnFuzion root computer to start EnFuzion at boot time?

Verify that the EnFuzion startup files are installed. The files are in the directory /Library/StartupItems/EnFuzion. The directory should include two files, EnFuzion and StartupParameters.plist.

If the directory or the files do not exist, go to the directory with an unpacked EnFuzion distribution and execute: sudo ./install-service

If the directory and the files exist, verify that EnFuzion is listed in the system startup file. The system startup file is /etc/hostconfig. The file should contain a line:
ENFUZION=-YES-

To start EnFuzion, execute the following command line:
sudo SystemStarter start “EnFuzion Control Root Service”

How do I install an EnFuzion license key?

EnFuzion license keys are stored in file /config/enflicense.txt. Verify that the file exists and that it contains your license key.

If the license key file does not exist, copy your EnFuzion license key to /config/enflicense.txt.

If the license key file exists, but the enfdispatcher process is not running, verify that there are no messages about an invalid license in the EnFuzion log file in /work/enfuzion.log.

If your license key is invalid then the log file contains messages similar to the following:
Mon Jan 16 18:52:51 2006: CL10102 cluster host3:10102 create port 10102
Mon Jan 16 18:52:51 2006: CL10102 cluster host3:10102 message build 9.0.006 for Linux 2.4.5-3smp i686
Mon Jan 16 18:52:51 2006: CL10102 cluster host3:10102 message reading root options from file “/home/john/enfuzion/config/root.options”
Mon Jan 16 18:52:51 2006: CL10102 cluster host3:10102 message the license file “/home/john/enfuzion/config/enflicense.txt” contains an invalid EnFuzion Root license.
Mon Jan 16 18:52:51 2006: CL10102 cluster host3:10102 message The license is invalid for the following reasons:
Mon Jan 16 18:52:51 2006: CL10102 cluster host3:10102 line 2: day date 16 1 2006, expired 15 12 2005
Verify that the content of /config/enflicense.txt matches the content of the EnFuzion license key that you received in your e-mail.

If your EnFuzion license key expired, send a request for a new license key to support@axceleon.com.
For an additional assistance, report the problem to support@axceleon.com and include /work/enfuzion.log and/config/enflicense.txt in your message.

How do I verify that the EnFuzion root is running?

On Windows, open Task Manager and confirm that the following processes are running: enfDispatcher.exe and enfeye.exe.

On Mac OS X and Linux, execute the following command line:
ps ax | grep enf
Confirm that the following processes are running: enfdispatcher and enfeye.bin.

If the enfeye process is not running, reboot the machine.

If the enfdispatcher process is not running, check out the enfdispatcher section.

How to set up my EnFuzion Root to start automatically at boot time?

The EnFuzion installers, by default, configures the Control Root Computer to start automatically at boot time.

If your Control Root process does not start automatically after the reboot, please first consult other troubleshooting tips in this FAQ section, and make sure to check this log file for any clues:  /work/enfuzion.log.

On Windows machines, please make sure that Group Policy is installed.  EnFuzion uses a startup script on the EnFuzion root host to start after a reboot and Group Policy is required for this functionality to work. Execute the following steps to install Group Policy:

  • Start the Microsoft Management Console
    • in Start menu, select Run…
    • type mmc
  • Add Group Policy Snap-In in the Management Console
    • in Console/File menu, select Add/Remove Snap-In…
    • click Add…
    • select Group Policy
    • click Add
    • click Finish
    • click Close
    • click OK
  • Verify the Dispatcher startup script
    • double click Local Computer Policy
    • double click Computer Configuration
    • double click Windows Settings
    • click Scripts (Startup/Shutdown)
    • in the panel on the right, double click Startup
    • verify that the C:\EnFuzion\bin\enfstartup.exe is on the list
    • click OK
  • (Optional) specify 10s for time that Windows will wait for a startup script
    • double click Administrative Templates
    • double click System
    • in the panel on the right, double click Maximum wait time for Group Policy scripts
    • select Enabled
    • type 10 in the Seconds field
    • press the key
  • (Optional) specify that startup scripts should execute asynchronously
    • in the panel on the right, double click Run startup scripts asynchronously
    • select Enabled
    • click OK
    • exit the Microsoft Management Console
    • in Console/File menu, select Exit
    • click No

What to do when I am unable to connect to the EnFuzion Web?

Verify that the URL address in your Web browser is correct. The EnFuzion Web address is:

http://:10101

You should be greeted by the EnFuzion Welcome page.

If the EnFuzion Welcome page is not displayed, verify that EnFuzion Root is running and that the network to the EnFuzion Root host is working.

If the EnFuzion Welcome page is displayed, click on the Cluster link in the header to verify EnFuzion operation.

If the Cluster link returns a General Error page, then verify that the EnFuzion Root is running.

What to do when my enfboot.bat program does not start the EnFuzion root on a Windows computer?

If you are unable to start the EnFuzion Dispatcher with an enfboot.bat file, sometimes it is due to Windows caching issues. The workaround for this is as follows:

  • On the root machine, click Start menu
  • In the search box, type group policy
  • Select Edit group policy
  • In the left menu, double click Computer Configuration:Windows Settings
  • In the right window, under Name, double click Scripts (Startup/Shutdown)
  • In the right window, double click Startup
  • In the dialog, click OK
  • Select File:Exit
  • Reboot the machine and confirm that the Dispatcher is running

What to do when the enfdispatcher process is not running on the EnFuzion root computer?

Verify in the Task Manager on Windows or with the ps ax command on Mac OS X and Linux that there is no enfdispatcher process.

If there is no enfdispatcher process, check out the dispatcher log for any error messages. The dispatcher log is located in the directory /work/enfuzion.log. The most common problems are a missing or invalid EnFuzion license key or no space on the working disk.

If the EnFuzion license key is missing or invalid, install the key.

If your working disk is running out of space with less than a few Mb available, EnFuzion Root software records this in the log and preventively terminates. Delete redundant files and reboot the machine or restart EnFuzion.

If the log file /work/enfuzion.log does not exist, delete all the files in the /work directory, verify that the EnFuzion user can write to the directory and reboot the machine.

If there is still no enfdispatcher process and no EnFuzion.log file after the machine is rebooted, verify that EnFuzion is configured to start at the boot time.

 

Render Node Configuration

A Linux based Compute Node doesn’t start, why?

Verify with the ps ax command that there is no enfnodeserver process.

Verify that the EnFuzion startup script is installed. The script is in the file /etc/init.d/enfnode.

If the file /etc/init.d/enfnode does not exist, go to the directory with an unpacked EnFuzion distribution, log in as a root user and execute:  ./install-svcnode

If the file /etc/init.d/enfnode exists, verify that EnFuzion is on the list of services that are started at the boot time. Execute the command:  chkconfig –list | grep enfnode

Output should include several on levels:  enfnode 0:off 1:off 2:on 3:on 4:on 5:on 6:off

To start EnFuzion, execute the following command line:  /etc/init.d/enfnode start

If the enfnodeserver process is still not running, then check out the Node Server log. The log consists of two files in the /tmp directory. Files are called .enfnodea.log and .enfnodeb.log. EnFuzion uses a circular double buffering to keep the file sizes limited. The file with the latest entries contains the latest reports. The files contain any critical error messages by the Node.
If the problem is not evident from the Node Server log, then send a report to support@axceleon.com and include files .enfnodea.log and .enfnodeb.log.

A Windows based Compute Node doesn’t start, why?

To quickly identify the cause for this, check these EnFuzion log files for error messages:

  • The EnFuzion  Starter Service Log file <EnFuzion Installation Dir>\temp\enfstarter.log
  • The EnFuzion Node Server Log files <EnFuzion Installation Dir>\temp\enfnodea.log and enfnodea.log

A Compute Node is “working” after the EnFuzion Starter Service starts the enfnodeserver process on that Compute Node.  The EnFuzion Starter Service reports any errors that happens during that process in the Starter Service Log, which is here: <EnFuzion Installation Dir>\temp\enfstarter.log.

A common cause for a Compute Node failing to start is an invalid user name or password given during the Compute Node installation. When this happens, the Starter Service log will show the following message:

Thu Jan 12 20:00:41 2006: Logon failed for user ‘EnFuzion’ – Logon failure: unknown user               name or bad password.

There are two ways to correct this:

  1. Re-install the Compute Node with a valid Administrative user name and password, or
  2. Edit the file <EnFuzion Installation Dir>\service.config.txt or the file <EnFuzion Installation Dir>\Config\enfuzion.nodes.txt and change the password to match that of the Administrator user you intend for EnFuzion to run under on the Compute Node.  Which file contains the password you need to change depends on how the Node was created. Refer to the EnFuzion User Manual for more information on “locally-defined” Nodes vs. Nodes “defined on the Root computer”.

After you change the service.config.txt  file, you must restart the Compute Node as follows:

  • Stop the Node by selecting Windows->Start->All Programs->EnFuzion->Compute Node Utilities->Stop EnFuzion Node service.
  • Start the Node by selectingWindows->Start->All Programs->EnFuzion->Compute Node Utilities->Start EnFuzion Node service.

After you change the enfuzion.nodes.txt file,  you must restart the EnFuzion Root as follows:

  • Stop the Root by selecting Windows->Start->All Programs->EnFuzion->Control Root Utilities->Stop EnFuzion Root service.
  • Start the Root by selecting Windows->Start->All Programs->EnFuzion->Control Root Utilities->Start EnFuzion Root service.

When you report problems to our support team, please make sure to include your enfstarter.log,  enfnodea.log and enfnodeb.log files.

An OS X based Compute Node doesn’t start, why?

Verify with the ps ax command that there is no enfnodeserver process.

Verify that the EnFuzion Node startup files are installed. The files are in the directory /Library/StartupItems/EnFuzionNode. The directory should include two files, EnFuzionNode and StartupParameters.plist.

If the directory or the files do not exist, go to the directory with an unpacked EnFuzion distribution and execute:
sudo ./install-svcnode

If the directory and the files exist, verify that EnFuzion is listed in the system startup file. The system startup file is /etc/hostconfig. The file should contain a line:
ENFNODE=-YES-

To start EnFuzion, execute the following command line:
sudo SystemStarter start “EnFuzion Compute Node Agent”

If the enfnodeserver process is still not running, then check out the Node Server log. The log consists of two files in the /tmp directory. Files are called .enfnodea.log and .enfnodeb.log. EnFuzion uses a circular double buffering to keep the file sizes limited. The file with the latest entries contains the latest reports. The files contain any critical error messages by the Node.

If the problem is not evident from the Node Server log, then send a report to support@axceleon.com and include files .enfnodea.log and .enfnodeb.log.

Are my Compute Nodes working, how do I check?

Open the EnFuzion Web page in your Internet browser:
http://:10101

Click on the Nodes link in the header to obtain the Nodes table.

Under the Host column, find the host name for the Node and check its Status.

If the node status is Idle, Executing or Busy, then the Node is working.

If the host name is not in the table or if its status is Down, then the Node is not working. In that case, verify that the EnFuzion Node is running on the host.

How do I know if my Compute Nodes are running?

On Windows, open Task Manager and confirm that the following processes are running: enfStarterSvc.exe and enfNodeServer.exe.

On Mac OS X and Linux, execute the following command line:
ps ax | grep enf
Confirm that the following process is running: enfnodeserver.

If the enfnodeserver process is not running, check out the enfnodeserver process section.

If the enfnodeserver process is running, confirm that the node is not working, using the EnFuzion Web.

If the enfnodeserver process is running, but the node is not working, then the Node is not connecting to the EnFuzion Root. Check out the section on Node is not connecting.

What to do when an EnFuzion node is not connecting to the EnFuzion Root?

Verify that there is no active firewall on the EnFuzion Root Computer. If a firewall is required on the EnFuzion Root Computer, then configure EnFuzion to use static port numbers. Perform the following steps on the EnFuzion Root Computer:

add the following line to /config/root.options:
jobport 10104

in the firewall configuration, open the following ports:
10101, 10102, 10103, 10104;
restart EnFuzion on the Root Computer.

Verify in the Task Manager on Windows or with the ps ax command on Mac OS X and Linux that the enfnodeserver process is running.

If the process is not running, check out the section on Node is not running.

If the enfnodeserver process is still not running, then check out the Node Server log. The log consists of two files. On Windows, files are called enfnodea.log and enfnodeb.log and are in the \temp directory. On Mac OS X and Linux, files are called .enfnodea.log and .enfnodeb.log and are in the /tmp directory. EnFuzion uses a circular double buffering to keep the file sizes limited. The file with the latest entries contains the latest reports. The files contain any critical error messages by the Node.

If the problem is not evident from the Node Server log, then send a report to support@axceleon.com and include the files enfnodea.log and enfnodeb.log.

What to do when my compute nodes don’t start after a reboot on a Windows machine?

This can happen when a Windows machine cannot complete booting and configuring its networking settings before the EnFuzion Node Service processes try to start.  EnFuzion is designed to overcome this condition by introducing a delay before it starts on compute nodes after a reboot.

You can configure this in the service.config file, which is located in the EnFuzion Installation Directory by default.  In this file, set the value for the startdelay <value> option.

This option tells EnFuzion to delay the start of the EnFuzion Node Service by an amount of time specified in seconds. For example, a value of 60 means 60 seconds of delay. This delay is used to give the Compute Node more time to complete its booting process and networking configuration, before the EnFuzion Node Service can successfully start.

You need to unregister and reregister the EnFuzion Node Service and reboot the Compute Node after making this change.

 

Artist Workstation Configuration

How can I submit scenes for rendering from my 3D application software?

Axceleon provides direct submission scripts for supported 3D application software.  In most instances they can be installed from the EnFuzion3D Desktop, using the Tools->Install Application Scripts command.   The complete details on how to do this for each support application is in the EnFuzion3D User Guide.

How do I check if my workstation is connected to the render farm?

Select Tools:Test Control Root Access.
This opens a dialog for testing the connection. Press Test Connection button.

If the test is successful, then EnFuzion for Render Farms is connected.

If the test fails, then verify the address of the EnFuzion Control Root in the file
/config/submit.config.txt.

If the address is correct, then verify that the EnFuzion Control Root is operational and accessible over the network.

 

Image Rendering

After Effects: After Effects fails to render on OS X based render nodes, why?

If no user is logged in on the Mac OS X platform, then rendering might fail with the following message:

INIT_Processeses(), could not establish the default connection to the WindowServer

There are two workarounds to avoid this situation:

  • Login the EnFuzion user permanently;
  • Set the ownership of the After Effects aerender command to root with the following commands:
    cd /Applications/Adobe After Effects 6.5
    sudo chmod +s aerender
    sudo chown root aerender

Can I have multiple versions of 3D application software on render nodes?

Yes, you can.  EnFuzion3D supports multiple versions of 3D applications to co-exist on render nodes.  At job submission time, you simply specify which version to use, either with a choice made and stored in the scene, or from the EnFuzon3D Desktop.

CINEMA 4D: CINEMA 4D fails to render on OS X based render nodes, why?

Verify that your scene is prepared for rendering on an EnFuzion render farm. The logging in the scene must be turned on. To turn on the logging, open the scene in CINEMA 4D and select Render Settings:Options, turn on Log File.

If the logging is turned on, but the scene is still not rendering, then verify that your Compute Node is configured for rendering with CINEMA 4D. The EnFuzion user on the node must have write, read and modify permissions to the CINEMA 4D directory, so that it can manage the render log. These permissions are turned on as follows:

  • right click on C:\Program Files\MAXON\CINEMA 4D R9 in Explorer;
  • select Properties:Security;
  • under Group or user names:, select Users;
  • under Permissions for Users:, turn on Full Control;
  • click OK.

Maya: Can I use the thumbnail browser to show tiles?

This feature is not yet supported. The View Thumbnail feature does not work for frames rendered in tiles.

MAYA: MAYA fails to render on OS X based render nodes, why?

If no user is logged in on the Mac OS X platform, then rendering might fail with the following message:

INIT_Processeses(), could not establish the default connection to the WindowServer

There are two workarounds to avoid this situation:

  • Login the EnFuzion user permanently;
  • Set the ownership of the Maya Render command to root with the following commands:
    cd /Applications/Alias/maya7.0/Maya.app/Contents/bin
    sudo chmod +s Render
    sudo chown root Render

Maya: What to do when Maya frames fails to render on heterogeneous render farms?

Your render farm is heterogeneous if one or more Compute Nodes run a different operating system than your Submit Computer.

All external texture and other file references in the scene must be relative to the Maya project. EnFuzion automatically adjusts path values between different platforms when it calls the renderer from a command line. EnFuzion will not change any paths that are specified in the scene itself. If you want to use file paths that are not relative to the project and have a heterogeneous render farm, please contact Axceleon at info@axceleon.com.

Mental Ray: How do I generate .mi files from the command line or with a script?

The following command takes a Maya scene and generates .mi files:

maya -batch -command “Mayatomr -mi -pf 2 -file .mi -xp rrarrarrrr” -file

Replace with the name of the output .mi files and with the Maya scene file.

The command can be included in a script or executed from a command line.

My output images are not correct, why?

Make sure that your scene and your render global parameters are correct by rendering several images locally on your workstation before submitting the scene to your render farm.

If images are correctly rendered locally, but fail to render on the render farm, check out the section on failed rendering.

My rendering didn’t complete, what to do next?

Select the run with failed jobs and double click on the run to open its Job List window. Check the Show All checkbox in the upper right corner. This will show all job retries, including rescheduled jobs. Select a job which causes problems and right click or Ctrl click on Mac OS X to display the job menu.

Select Show Render Log to view the render log produced by the renderer. Check out the log for any error messages or notices from the renderer that might help to diagnose the problem.

If the render log does not exist or if the log does not contain any indication of the problem, select Show Render Standard Output to view the standard output and Show Render Standard Error to view the standard error. These entries show any messages that are recorded to the standard output and the standard error files by the renderer and other programs.

If Show Render Standard Output and Show Render Standard Error do not help, select Show Render Command. This entry displays the command that EnFuzion used on a Compute Node to render the image. Verify that the command is correct by logging into the Compute Node and typing the command in the Command Prompt. If the command fails, then there is a problem with the rendering application, access to the project files or environment variables on the node. Additional entries in the menu help with the problem identification.

Select Show EnFuzion Job Log to view any additional messages from EnFuzion. This log contains all major events during the job execution as well as all EnFuzion errors for the job. Most common problems that are identified in the log are:
the file or a directory is not found:
The node is unable to access project files. Verify that the project files are shared over the network and accessible to compute nodes.

the following user command exited with status code:
The rendering application failed to complete successfully. Verify that the rendering application is installed on the node, verify the environment variables required by the application and check out the render log, the standard output and the standard error for any error messages.
Select Show Render Environment to view and verify the environment variables that were defined for the renderer. The most common problem with environment variables is that their values are incorrect. If values are incorrect, modify values in the EnFuzion node environment file in /environment.txt.

If the problem persists, select Zip Diagnostic Files. This produces the zip file run-.zip with diagnostic files. The file is created in the /submissions/work directory. Send this zip file to support@axceleon.com for assistance.

Why doesn’t the “Show Images” show any images after the frames have been rendered?

By default, the EnFuzion Image Browser uses the Maya fcheck or the XSI flip utility to display images. You must have Maya or XSI installed for this feature to work properly. Fcheck is tried first, flip is tried second.

You can also configure EnFuzion to use another image browser. Please see the FAQ item on configuring EnFuzion to use a different image browser.

XSI: Why can’t I see images with the XSI image viewer on Windows?

When you try to use Softimage flip.exe to view images, the program might fail with the following message:

flip.exe – Unable to Locate DLL
The dynamic link library ilcor10.dll cannot be found …

In this case, find ilcor10.dll on your system and add the directory it is located in to the PATH environment variable on your system or copy ilcor10.dll to the directory with flip.exe.

XSI: Why don’t I see thumbnails on Windows?

When EnFuzion tries to use Softimage imgconv.exe to convert images to thumbnail JPEGs, the program might fail to work.

In this case, make sure that the SI_IMAGE_PATH environment variable is set to \Application\bin\sil. Default value for XSI 5.0 on Windows is C:\Softimage\XSI_5.0\Application\bin\sil.