From VFXpedia

Last Updated: 22:39, 2 February 2009 (CST)

Contents 1 Install Files 1.1 Licensing 1.2 eyeon_wine 1.3 Fusion 1.4 OpenGL vs non-OpenGL Render Nodes 1.5 Non-RPM installations 2 Setup 2.1 Wrapper scripts 2.1.1 Configuration file 2.1.2 License server 2.1.3 Fonts 2.2 Prefs 2.3 Profile 3 Known Issues 3.1 NVidia Driver Issue 3.2 Tablets 3.3 Help 3.4 Too many fonts

Install Files

Licensing

Fusion for Linux requires a network license. If you are using a pre-existing windows license server you will not need to use the HASP drivers or FlexNET for Linux.

FLEXnet_eyeon.tar.gz - This contains all the FLEXnet files. Install instructions are contained in the PDF within that archive.

HDD_Linux.tar.gz, HASP_SRM_Linux_3.50_Redistribute.tar.gz - These are the HASP drivers for Linux. There are a couple of readme.txt files in there that explain how to install the driver(s).

With both the FLEXnet files and the HASP drivers, the user/sysadmin will have to add things to a script to start them each time the machine boots (or a user logs in).

eyeon_wine

eyeon_wine-1.1.4.2-1.i586.rpm - This is the package for an eyeon specific version of Wine.

To install the package:

rpm -i eyeon_wine-1.1.4.2-1.i586.rpm

To upgrade from an older release of the eyeon_wine package:

rpm -Uvh eyeon_wine-1.1.4.2-1.i586.rpm

Current builds of eyeon_wine have moved all configurations from ~/.wine to ~/.eyeon_wine to allow for a side-by-side installation of mainstream Wine releases and eyeon specific releases. Registry keys should go into ~/.eyeon_wine/system.reg file; /opt/eyeon/wine/bin/regedit can be used to get a regedit GUI, which will use the correct registry storage.

Source for eyeon_wine is available on request.

Fusion

eyeon_fusion_5.3.1.74.i586.rpm - This contains the workstation version of Fusion.

To install the package:

rpm -i eyeon_fusion-5.3.1.74-1.i586.rpm

To upgrade from an older release of package:

rpm -Uvh eyeon_fusion-5.3.1.74-1.i586.rpm

OpenGL vs non-OpenGL Render Nodes

We offer two Linux versions of the “render node”.

• eyeon_consoleslave_5.3.1.74.i586.rpm is a non-OpenGL version. It does not require a working X11 server, but it will not render any OpenGL tools (PAW and some plugins), as these tools require an OpenGL capable machine.

• eyeon_renderslave_5.3.1.74.i586.rpm requires OpenGL to run and will render OpenGL tools, provided an X11 server with OpenGL is running. Inside the eyeon_renderslave.rpm file is a second copy of a ConsoleSlave.exe, but this is a secondary interface to the same exe build - it still requires OpenGL and an X11 server. You can use this version to run any OpenGL comps via your command line renderer.

In order to have OpenGL support, you will need to run an X11 server of some sort. This could be a graphics card with a matching X.org driver or Xvfb (Virtual Frame Buffer) driver.

Non-RPM installations

Fusion and/or RenderSlave and/or ConsoleSlave and eyeon_wine can be extracted from their RPM files on systems that do not use RPM as the package format. The extracted files should be located under /opt/eyeon folder after installation:

$ ls /opt/eyeon/
bin  ConsoleSlave  etc  Fusion  RenderSlave  wine

Setup

Wrapper scripts

There are wrapper scripts provided for Fusion, ConsoleSlave and RenderSlave. These are located in /opt/eyeon/bin. The wrapper scripts are the preferred method for launching each of the above programs. The scripts set up the required environment and will also import settings from a configuration file in the user's home directory.

Configuration file

The per-user configuration is located in ~/.eyeon_fusionrc and is a bash script. If this configuration file does not exist, a template will be created.

License server

The user will need to point Fusion to a source of a valid license. This can be achieved by setting the environment variable EYEON_LICENSE_FILE to point to the correct license server. The simplest method is to edit the ~/.eyeon_fusionrc configuration file to include a line similar to this:

EYEON_LICENSE_FILE="@licenseserver;"

The same result can be achieved by manually configuring the env var by entering in a console:

export EYEON_LICENSE_FILE="@licenseserver;"

Fonts

You will need to acquire a number of Windows fonts in order for the Fusion interface to appear correct. The fonts are;

• tahoma.ttf
• marlett.ttf
• micross.ttf
• sserife.fon

Fusion can be configured to look for fonts in multiple locations. This can be achieved by setting the environment variable FUSION_FONTS to include a list of semi-colon separated paths. The ~/.eyeon_fusionrc configuration file can include a line similar to this:

FUSION_FONTS="/usr/share/fonts;/usr/local/fonts/truetype"

If the FUSION_FONTS environment variable is not set, the wrapper script will use fontconfig to scan the system for fonts and use an autogenerated path. The font discovery script is located in /opt/eyeon/bin/find_fontdirs

Prefs

The default Profiles (prefs) directory is User:Fusion/Profiles (i.e. $HOME/Fusion/Profiles), similarly things like the Comps, Defaults, Settings, etc. dirs are in the UserData: directory. So prefs, comps, defaults, etc. will by default NOT use the ones in the Fusion dir. This does mean that any of the Comps, Scripts, Defaults, Macros, etc. contained within the Fusion RPM file won't be immediately available to a Linux user.

Profile

The profile dir can be changed with the FUSION_PROFILE_DIR env var, then the individual profile subdir within that can be set using the FUSION_PROFILE env var, just like the Windows version. Most users would likely want to use the eyeonServer_LibrariesDir env var to set an appropriate UserData: or $HOME related path for eyeonServer too. Unlike the FUSION_PROFILE_DIR env var, it doesn't have access to pathmaps, so it must contain a full normal path. Since eyeonServer usually uses a Libraries directory off its own executable directory, if it is run from a common read-only place it likely won't be able to create its directory and serve even local bins. So changing the eyeonServer_LibrariesDir env var is probably essential.

Known Issues

NVidia Driver Issue

There appears to be some NVidia drivers that do not do data format conversions properly. When this is the case the top half of 16bit int or 16bit or 32bit float textures in the 3D view will be black. If this happens setting the env var FUSION_TEXTURE_CONVERT=True will cause Fusion to do the data conversions, and that will hopefully get around the problem. This issue doesn't affect viewing 2D images.

Tablets

Some problems may occur when dragging certain view controls on a second monitor when using a tablet. If this happens, use of tablet messages can be disabled with the env var FUSION_TABLET=False. The down-side of this is that Paint won't get pressure information anymore.

Additionally, installing tablet drivers and then attempting to run Fusion without a tablet connected to the machine may result in a failure within Wine. These issues should now be resolved with the latest version of Wine.

Help

Linux Fusion contains an HTML version of the help. There's no easy way for Fusion to determine automatically which app to use to view it (file associations are all desktop system specific), so Fusion uses the "HelpApp" entry in the Help\Linux.helpmap file. Same goes for VFXpedia help, except of course it uses the entry in the Online.helpmap file. Those files currently have the HelpApp entry set to "/usr/bin/firefox". If of course Firefox is somewhere else, or Firefox isn't installed but some other browser is, then those entries will need to be changed.

Too many fonts

In some cases the /opt/eyeon/bin/find_fontdirs script can find too many font directories, which can result in a crash at startup. The workaround is to use a shorter font path, for example:

FUSION_FONTS="/usr/share/fonts;/usr/local/fonts/truetype"