Starting with Firestorm release 18.104.22.168634, Windows and Mac 64-bit versions are also available for Second Life with Havok support.
Older Firestorm 64-bit versions currently do not include Havok support. This means that:
Older 64-bit versions therefore are OpenSim versions; they can be used both in SL and in other non-SL grids.
The 64-bit version of Firestorm can only be installed on 64-bit operating systems; it will not work on 32-bit. If you are not sure which you have, check in top menu, Help → About Firestorm. This will indicate whether you are on a 64-bit operating system. Examples:
Note the “64-bit” and “x86_64” in the above.
If you attempt to install it on a 32-bit system, Windows users will get an error as shown here. Linux users will get errors on trying to run the program.
If you have 4GB RAM or less, there is no benefit to installing the 64-bit version of the viewer.
If you believe you have found a bug, then please report it as usual; information on how to file a bug report is given on this page. Please be sure to indicate in the title of the report, that the bug affects the 64-bit build, and don't forget to give your system information in the Environment field. Also, it would be helpful if you could verify whether or not the same problem occurs with the 32-bit build of the viewer.
Currently, if you need to reinstall the 64-bit version of Firestorm, you will first need to remove the existing copy manually, via Add/Remove Programs. Note that the 64-bit version identifies differently from the 32-bit, as follows:
So if you have both installed, be careful to remove the correct one.
Below are some issues that some people have run across during testing, and solutions or work-arounds.
If you get the error “The program can't start because MSVCP100.dll is missing. Try reinstalling to fix this problem.” when starting the 64-bit version of Firestorm, you will need to install the package containing this file. Go to this page, download and install both the 32-bit and the 64-bit versions.
If you get this error during install, then the steps (from the JIRA referenced above), as as follows: