|
|
 |
 |
|
 |
 |
|
VFXPedia is a central resource for visual effects artists who use eyeon Software's Fusion, Digital Fusion, DFX+, Rotation and Vision. To visit VFXPedia.com, please click here.
The following are responses to common support and registration issues that we
see at eyeon Software on a regular basis. If you do not find the answer to your
question here, please feel free to contact us at
 tech@eyeonline.com
|
|
How do I add the 3GB switch to my computer to assist with caching under version 4?
Where can I find the required information for registration?
Something I have done is repeatedly causing a visit from Dr. Watson. (A Crash)
I just installed Windows XP, and now Fusion/DFX+ can't find a dongle!
Why does my text look crappy and/or have a dark edge to it?
How do I use cache to disk?
Why doesn't my network render?
Why doesn't my network license work?
I can't create flipbooks on my computer. What gives? (Wildcat video cards.)
What .dll and plugins do I need to load Toaster files without the hardware installed?
My Velocity 9.x upgrade updated my DFX+, now it says I do not have a valid license file?
Fusion no longer runs after installing Quicktime 7
Network Render Queue Not Auto Saving
Why do I see a red "X" in the view?
Slow performance on adding tools and changing connections
Linux: Overview
Crash Logs not emailing correctly
Linux OS Recommendations
xp64
Filter methods for transform tools
|
How do I add the 3GB switch to my computer to assist with caching under version 4?
With Digital Fusion 4 and DFX+ 4 came a whole new way to work with our software that allowed our users to really take advantage of the RAM they
had on their systems to actively cache the project they were working on. However at the same time version 4's new caching capabilities started to
really push the limits of Windows memory management. On systems running 2 GB of RAM or more certain instabilities were found when Fusion or DFX+
started filling up the 2GB of RAM with its cache. In Windows by default any application can only use 2 GB of RAM at most. However under certain
versions of Windows, applications could actually use up to 3 GB or RAM if it was available. (A list of the supported operating systems is included
below. Please note that Windows 2000 Pro is NOT supported.) To 'activate' this capability you need to add the 3GB switch (instructions below) to your system. Not only does this allow an application
to use up to 3GB of RAM if available, but it also makes using 2GB of RAM considerably more stable and reliable as a result.
Please be aware that the 3GB switch will only improve stability on systems with 2 or more GB of RAM, and running one of the operating systems
referenced below. Once the 3GB switch has been activated we recommend setting the DFX+/Fusion cache limit to about 80% in the preferences to
ensure stable performance.
Adding the 3GB switch is very simple. You first need to locate your machines Boot.ini file which should be located in the root of your
main system drive. (Be aware that this file may be hidden and marked as read-only initially.) You will want to open this
file in a program such as Notepad to edit it properly.
Before adding the 3GB switch though it is important to note that the switch is very picky, and requires that every device and driver
on your system be fully WinXP compatible in order to work at all. If anything in the system is not compatible, Windows will not load at all
when restarting with the 3GB switch activated. The only way to then remove the switch from the Boot.ini file so that Windows
can load is to either mount the drive in another system and manually change the boot.ini file, or reformat the drive and
re-install Windows. Both solutions are far from ideal.
To safely add the 3GB switch we recommend adding a second instance of the OS in the boot.ini, and add the /3GB switch to that second version.
----- default boot.ini without 3GB Switch -----
This is what a default boot.ini file will look like. (This may differ from system to system.)
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Pro"
----- updated boot.ini with 3GB Switch -----
This is what the updated version should look like. Notice the /3GB that has been added to the second instance of the OS line.
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Pro"
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Pro with /3GB" /3GB
Once you have updated your boot.ini file accordingly and have saved the changes, simply restart your system for the changes to
take affect. When your system reboots you will be given the option to choose either the standard Windows XP version or the
3GB switch enabled Windows XP version. If you choose the 3GB version and it fails to allow Windows to properly load, just
restart your system and you will be given the two options once again, where you can then choose the standard Windows XP
version to load. Either way, if it works or doesn't, you can then remove whatever line you don't need in the boot.ini file.
Please note: The 3GB switch is only compatible with the following versions of Microsoft Windows.
- Windows XP Professional (and greater)
- Windows Server 2003
- Windows Server 2003, Enterprise Edition
- Windows Server 2003, Datacenter Edition
- Windows 2000 Advanced Server
- Windows 2000 Datacenter Server
- Windows NT Server 4.0, Enterprise Edition
For a more detailed explanation of the 3GB switch and usage please visit the following page on the Microsoft website.
http://www.microsoft.com/whdc/hwdev/platform/server/PAE/PAEmem.mspx
In addition:
There is currently a known issue with the 3GB switch and Windows XP SP1, that may cause Windows not to start. A supported fix is
available from Microsoft, but it is only intended to correct the problem resulting from this specific setup. For more information including download
links to this particular fix please visit the following page on the Microsoft website.
http://support.microsoft.com/default.aspx?scid=kb;en-us;328269
Where can I find the required information for registration?
When registering a new copy of Digital Fusion or DFX+ you will need two key pieces of information (in addition to
personal contact info) during the registration process.
The CDKey can be found either on the underside of the software box, or on this inside cover of the manual. Two
copies of this CDKey are shipped with every product. The CDKey itself will be 7 characters long.
The Serial Number is the number that has been encoded to the Hardware Dongle itself. (It does not appear on the
dongle label.) Before registering for the first time you will need to install the DF or DFX+ software, attach the dongle
to your systems parallel port and then start the program. It will launch but then provide a warning saying no valid
license could be located. It will then provide you with the Serial Number that is encoded to the dongle in a window.
It should be 8 characters in length.
Something I have done is repeatedly causing a visit from Dr. Watson. (A Crash)
A Dr. Watson log can be of great use to our developers when trying to figure out what causes a specific crash.
When forwarding a crash log please try to include a detailed description of the steps that caused the crash, as well as your version number and build number of the copy of Fusion/DFX+ you are using. (This can easily be found in the Help > About box of the program while it is running.)
To determine where the Dr. Watson crash logs are being created on your system, or to set a specific location that's easy to remember use the following steps:
1. Under the Start menu use the Run option, and type in drwtsn32.exe and hit OK. (Or browse to 'C:\winnt\system32\drwtsn32.exe and run the executable.) This will open the configuration window for Dr. Watson.
2. At the very top of this window is a path entry. Take note of the current path as this is where the crash log text file is being created. Alternately use the 'Browse' button to change the path to a different location.
3. Make sure that the 'Create Crash Dump File' option is turned OFF and hit OK to close this window and save your settings.
4. Run Fusion/DFX+ again, and repeat the steps to generate the crash. When the application crashes be sure to let Dr. Watson finish compiling it's report. (The Dr. Watson error log dialogue will have an OK button when it completes.)
5. Locate the Dr. Watson crash log (it will be a text file) and email a copy of it eyeon Software Technical Support.
Crash logs will be continually appended to the end of this file so you may want to delete the log each month to ensure the file remains small in size and easy to email. Once deleted a new log will be automatically created the next time a crash occurs.
I just installed Windows XP, and now Fusion/DFX+ can't find a dongle!
Upon the release of Windows XP it was discovered that the HASP Dongle drivers did not support the new operating system.
This issue
was soon resolved by Aladdin, the makers of our HASP drivers, and new drivers were provided within days of the
problem being discovered.
The new drivers were incorporated into our upgrade installer as soon as they were released. Log into your
account and download the current upgrade installer to ensure that you have the latest HASP drivers.
Why does my text look crappy and/or have a dark edge to it?
Text is designed to be premultiplied by it's alpha channel. To remove the dark edge, be sure to set your merge to
additive. For more explanation on this, please visit the Techniques section of our website for a
Tip n' Trick that specifically deals with pre-multiplication.
To further increase the look of your text to get a better idea of how it will look on final renders, be sure to
enable the HI-Q checkbox, and the 1:1 option.
How do I use cache to disk?
For more explanation on this, check out the Tips n' Tricks under the Techniques section of our website.
Why doesn't my network render?
When dealing with a render node, there are a few things to keep in mind. All of your loaders and savers should
be mapped to a unc filename (i.e.: \\my computer\footage\project\element.####.tga) or should be mapped as identical
drives. (i.e. drive E: on your computer is mapped as E: on the render node(s).)
As far as setting up a node, All that is necessary, is to enter the IP or name of the master system into the network
preferences of each application. Typically you want to define one system as a master, and point both/other systems to it.
From there when in the render manager dialogue, you can use "scan" to find the additional nodes and full copies of
Digital Fusion.
Also make sure you have entered a UNC file path or identically mapped drive letter for the "render queues", "preview
renders" and "cache to disk" under the paths section of your preferences in order to utilize those functions.
1. Open your preferences on BOTH the NODE, and your WORKSTATION, and check the following paths:
a. Flows
b. Render Queue's
c. Preview Renders
d. Cache to Disk.
Make sure they are all UNC style directories, pointing to the appropriate directory.
2. Also check your saver, it too should have a UNC style filename.
3. Also be sure to have QuickTime installed on the render node if you plan on saving out to that format.
4. If you are using a DPS hardware device use the virtual file system. Rather than pointing your loaders to name.dps point it to the appropriate name.tga sequence. This is because name.dps requires the hardware to decode the image. By using the virtual file system, the host machine will decode all frames as they are called by the render node(s).
This also applies to the saver. To save a dps file, create a place holder .dps file first, and then point your saver to that virtual file system directory.
Why doesn't my network license work?
For users that have more than 3 licenses in total of Fusion, Render Node and DFX+, we offer network licensing. If
you have any questions about setting up floating license environments in your facility please visit
this page for
complete instructions and necessary files for download.
I can't create flipbooks on my computer. What gives? (Wildcat video cards.)
We have been hearing of a problem like this recently with the Wildcat 4210, 6110 and similar Wildcat video
cards. We suspect the wildcats support for DirectDraw is less than ideal. This may be caused by the driver
incorrectly reporting support for hardware scaling which we do in DF 3.1.
Hardware scaling is only done if there is enough video memory to support it, and if the board reports
that its hardware is capable of it. If the Wildcat is incorrectly stating that it does support hardware
scaling, Fusion will try to use it, and it'll be slow, or maybe even broken.
Please try setting a new environment variable (in your control panel, under system/advanced) named
DF_FBSTRETCH and make the value FALSE . Then restart Fusion . This should disable the hardware scaling
and use the Windows software scaling instead.
...from 3Dlabs:
"If it (Fusion) requires DirectX, then I'm afraid it will not work in a dual head configuration at
present. This is something we're working on, and hope to have available in a future driver release."
Charlie Peerless (MCP)
3Dlabs Technical Support
What .dll and plugins do I need to load Toaster files without the hardware installed?
You need a number of NewTek provided .dll's for Fusion to be able to read and write RTV files. newtekrtme.dll, rtvlib2.dll
(or rtvlib.dll for Toaster[1]), nt_tools.dll, proof.dll and beethoven.dll
The hardware is not required for file I/O.
These files need to be copied somewhere Fusion will find them, which means the system32 or windows folder, or Fusion's own plugin folder
(alongside the Toaster plugins). If Fusion is successful in finding these files when it loads you should find 'Toaster files (*.rtv)
listed in the the Loader and Saver's format pulldown lists.
My Velocity 9.x upgrade updated my DFX+, now it says I do not have a valid license file?
At present time Harris/DPS provides two(2) different variations of the Velocity 9.x upgrade. One of which includes the ability to update your copy of DFX+ to v4 as well as the Velocity software.
The other option that is available is the Velocity upgrade only. The CD which you recieve with your upgrade includes both updates and defaults to install both upgrades regardless of
your current license file or the upgrade you purchased.
If you do not have a valid license file for the DFX+ 4.0 upgrade you will need to reinstall the previous version of DFX+.
To confirm if you are entitled to a copy of the DFX+ 4.0 upgrade with your Velocity 8 upgrade you will want to contact Leitch registration
department via e-mail at
registration@leitch.com
Fusion no longer runs after installing Quicktime 7
Installing Quicktime 7 will cause Fusion to crash on startup. This is caused by a bug in Quicktime 7.0.0 through 7.0.2. Apple fixed the problem in Quicktime 7.0.3, which was released on Thursday, October 12th, 2005.
To prevent Fusion or DFX+ from crashing on startup either remove Quicktime from the system or upgrade to Quicktime 7.0.3 or higher.
Network Render Queue Not Auto Saving
There is a known bug in 5.0 to 5.02 build 82 where the render manager does not create the "autosaves" directory. If the user creates the directory manually, the queue will save as expected.
Why do I see a red "X" in the view?
The red "X" is drawn in the view when you do not have enough graphics memory, system memory, or your video card drivers are not supporting the required features for Fusion 5.0x. You may wish to ensure your video drivers are up to date. There have been known problems with Matrox videocards stating that they support OpenGL, however in practice it is very limited support. We have tested on modern ATI and Nvidia cards without issue.
If your video drivers are up to date, and the red X still persists, then please do the following to send in your hardware information;
1) Hold shift on the keyboard, and right click on the lower right area of the fusion interface that displays memory usage.
2) Choose the Debug: List OpenGL Hardware Info
3) Save the text that is displayed to a document you can find.
4) Email the document to tech@eyeonline.com
If your hardware information is empty it is possible that windows performed an update. This can install microsoft video drivers that don't support opengl and only ship with direct3d support. If the GLHardware log comes back empty the video drivers do not support any openGL at all. If this is the case, be sure to download the latest video card drivers from the Nvidia or ATI website and install those.
Slow performance on adding tools and changing connections
There is a known issue with the timeline view being set to heirarchy or reverse causing slowdowns as it sorts out the tool tree and connections. Setting this to all tools will restore the speed of the comp.
Linux: Overview
Quick Points about Fusion Linux.
* True, native, highly optimized x86 code.
* Is not running under an emulator at all.
* Wine is used for the GUI and Interface services.
* Has the largest number of 3rd party plugins.
* Completely cross platform render compatible.
* Plugins do not have to be redone for different Linux distributions.
* Exactly the same rendering result, platform to platform.
Fusion Linux is not running under emulation at all. All Operating systems have a base core and then layers to supply other services, Xwindows, OpenGL, Audio layers, desktops are all layers on top of Linux or any OS, as well as third party Libraries like Tiff, Jpeg etc. Whether these are in the OS core or DLL’s or layers they all layers of functions and code.
The processor wars are over, today it is all X86 architecture irrespective of OS, OSX, Linux, Windows. We developed a system to be cross platform yet easy to maintain with a minimum OS specific code. Fusion is a very large complex and deep application with a highly multithreaded core, the compiler and optimization methods that eyeon use includes hand coded SSE2 assembler. Performance is paramount and our highly optimized native X86 SSE2 and processing cores are in machine code and will execute on any x86 processor irrespective of OS and all system calls are done in cross platform standard ANSI C/C++ and again are not being emulated. We also use OpenGL and GPU acceleration these again are independent of the OS and are the native versions on the OS and have nothing to do with the Wine API. We use exactly the same compiler technology for all our Fusion builds and the rendered results will exactly the same from OS to OS and distribution to distribution.
We have developed our own version of Wine (wine is not an emulator, look it up) to supply a compatibility layer for some functions. The main function that the Wine provides is for the Interface and GUI and has no impact on the native x86 core processing code. Also this allows us to bring all our 3rd party developed plugins immediately to linux, without delay. Other developers use interface developer kits and cross platform frame works like TrollTech QT. All of these cross platform GUI frameworks have libraries of functions, they will get complied into you application, but note that these are still a layer of code to supply functionality, we choose to not compile in these functions but to keep them separate for better and easier development of the Fusion product. There is no difference between our approach and the third party library approach.
We have made system that is cross platform and can work in a mixed environment of different operating systems as well as bringing a huge range of resources to the Linux platform. Some customers are using Windows workstations and Linux Render nodes. These will render the same results and also use the exact same plugins. As Linux distribution cores change and break compatibility, all the applications and plugins have to reworked and recompiled for that distribution. For plugins and Fusion’s image processing core under Linux this does not happen at all since we supply the services to make them work, again this makes our system much more maintainable and upgradeable under different distributions.
Crash Logs not emailing correctly
If a user can not send a crash dump automatically from fusion's exception handler, any crash dumps Fusion or the RenderSlave generate will be at C:\eyeon.dmp and C:\eyeon.log which can be e-mailed to us separately using a normal e-mail client.
Linux OS Recommendations
Currently fusion for linux is undergoing testing. We have run Redhad Enterprise version 3 or 4 without issue. It has been operating under a number of fedora, and suse os's as well. As we get closer to a Linux release after 5.1, we will have a more complete list and list of known issues.
xp64
Using an update zip file doesn't register as valid software and the Rendernode won't start cleanly because an "authentication for windows" dialogue appears.
Filter methods for transform tools
The reason that selection of filtering methods are not available to the transform tools is that a lot of the methods are not capapble of either sub pixel rendering of offsets, or dealing with rotations of the image. The merge and transform tools are optimized for dealing with these issues.
|
|
|
 |
 |
|
 |
|