Quantcast
Channel: Phoenix Firestorm Project - Wiki
Viewing all 5258 articles
Browse latest View live

classes:people_nearby_plus.png - created


classes:people_recent_list.png - created

classes:people_recent_gear.png - created

classes:inventory_filter_types.png - created

classes:inventory_filters.png - created

classes:inventory_received_items.png - created

classes:inventory_non-fs-w.png - created

fs_install_crash

$
0
0

Crashing During Install or Startup

General

Firestorm "Locks Up" on "Initializing VFS"

If this occurs, chance are good that the inventory cache is corrupt. Deleting it should solve the problem.

  • Locate your cache folder. You will probably need to do this manually, if you are unable to log in. Use a file manager (like Windows Explorer for Windows system, Dolphin, or some such) to locate the cache folder. In its default location, the cache folder is hidden on most OSs. To find it, you will need to show hidden folders. Default cache locations are:
    • Windows XP: C:\Documents and Settings\[USERNAME]\Local Settings\Application Data\Firestorm
    • Windows Vista, 7, 8, 8.1, and 10: C:\Users\[USERNAME]\AppData\Local\Firestorm
    • Mac: ~/Library/Caches/Firestorm
    • linux: ~/.firestorm/cache
  • In this folder, locate the files named data.db2.x.* and index.db2.x.* (where * is a digit: 0, 1, 2, etc; you may have more than one of each type of file)
  • Delete all files that match these two names.
  • Log back into SL, to a quiet region (try Hippo Hollow, Aich or Hatton). Allow your inventory to repopulate fully.

Windows only: If the above doesn't work, then click the speaker icon in the system tray, then touch the volume slider, just enough to change the volume slightly. It may be that the Windows sound system has stalled; this should “give it a kick”.

If the above fails, then try doing a full wipe of all settings.

Login Crash with a Private Pool Error

Ref. FIRE-12339

This is almost always caused by the MemoryPrivatePoolEnabled being set to TRUE. It should never be set to TRUE. But before you try to fix this, we could really use a copy of your crash logs to help us work on a fix. See here for steps to collect your crash logs, then attach those logs to FIRE-12339.

Then, do the following:

  • Make sure hidden files/folders are set to show - see here for steps.
  • Browse to your user_settings folder. This is located at -
    • Windows XP: C:\Documents and Settings [USERNAME] \Application Data\Firestorm\user_settings
    • Windows Vista, 7, or 8, 8.1, and 10: C:\Users [USERNAME] \AppData\Roaming\Firestorm\user_settings
    • Mac: User/Library/Application Support/Firestorm/user_settings
    • Linux: ~/.firestorm/user_settings
  • In the user_settings folder, find the file named “settings.xml”
  • Open settings.xml in a text editor - For Windows, Notepad++ is ideal for this
  • Search settings.xml for the term MemoryPrivatePoolEnabled
    You will see a block of text like so:
<key>MemoryPrivatePoolEnabled</key>
<map>
<key>Backup</key>
<boolean>0</boolean>
<key>Comment</key>
<string>Enable the private memory pool management</string>
<key>Type</key>
<string>Boolean</string>
<key>Value</key>
<boolean>1</boolean>
</map>
  • Near the bottom there, change the “<boolean>1</boolean>” line just above </map> to “<boolean>0</boolean>”
  • Save changes to settings.xml and edit the text editor.
  • Login.
  • Profit.

Other Crash Situations

Issues outside of Firestorm can, and often do, result in viewer crashes….

  • Make sure your file system is not corrupt by running chkdsk or equivalent for your OS.
  • On Windows, ensure that your registry isn't messed up by running CCleaner or similar.
  • Reboot your PC and moder/router.
  • Ensure that video drivers are current, as well as your OS.
  • Do a Reinstall of Firestorm.

By Operating System

Windows Specific

  • If the installer does not run at all, try the following steps (this solution was described for Vista SP1; it has not been confirmed for other Windows versions):
    • Right click the installer .exe
    • Click Properties
    • On the bottom of the general tab is a message “This file came from another computer and might be blocked to help protect this computer”
    • Click Unblock
    • Installer should run.
  • You may have corrupt registry information; refer to this page. This is especially common for those rolling back from Win10 to an older version of Windows.
  • If you crash at startup with an error like: “failed to initialise properly code (0x0150002)”, or you get an error that the “side-by-side” configuration is incorrect, or“Firestorm failed to start because the application configuration was incorrect. Reinstalling the application may correct the problem”, please download this and install it, as your system is likely incompatible with the Visual Studio C++ 2005 SDK DLLs: AppFix.exe
  • Open the Firestorm install folder and search for any files named .config - delete any you find.
  • Note that some anti-virus software will result in errors during installation; more information is here.
  • If you are using an ATI (AMD) graphics card, then please refer here for known problems with these cards.
    For nVidia issues, plese refer to this page.
Windows 10

If you are using Windows 10, and have an Intel 2000/3000 or older graphics card, please refer to this page if you cannot start Firestorm without crashing.

Windows Vista or Windows 7

If you crash during login, then try setting Firestorm to XP compatibility:

  • Locate your desktop shortcut for Firestorm
  • Right click on the icon and select Properties
  • Select the Compatibility tab
  • Check the “Run this program in compatibility mode for:” and select Windows XP from the drop down
  • Click Apply.

If you get a User Account Control security popup, then please see this page.

linux-specific

If you have just installed Firestorm on a linux system and it will not start, it is highly likely that you are missing some required libraries. You need to verify if this is the case.

You need to open Terminal and cd to the Firestorm install directory. If you are unsure how to locate it, use your linux file manager to find it first; it will help you locate the install directory. Useful shorcuts:

  • ~/ - is your home directory
  • ~/Desktop - is your desktop directory

so for example, from terminal, you would do something like this:

cd ~/Firestorm

Assuming that Firestorm is installed in the directory called Firestorm, in your home.

Once there, copy the following into Terminal:

LD_LIBRARY_PATH="./lib:${LD_LIBRARY_PATH}" ldd bin/do-not-directly-run-firestorm-bin 

This will spit out a long list of libraries. Check to see if any are marked as “not found”. If so, you will need to install these with your package manager.



See this page for documentation on Firestorm 4.7.1 (45325) and earlier.


slurl

$
0
0

Clicking on a SLURL Doesn't Activate the Viewer

Windows

Windows only: We have now have a software that makes it very easy to adjust your SLURL settings, in order to open any viewer you have installed.
See here for details

Other suggestions below.

General Windows Instructions

  1. Open Default Programs by clicking the Start button and then clicking Default Programs.
  2. Click Associate a file type or protocol with a program.
  3. Click the file type or protocol that you want the program to act as the default for.
  4. Click Change program.

FireFox

In Firefox, goto Tools → Options → Applications Tab and scroll to Secondlife. Look to see if Firestorm is listed, if not, select “other”, then browse your hard drive to find the Firestorm.exe, click on it, select Open, then click Ok. (Reference: Applications panel—Set how Firefox handles different types of files.)

OR

Download and install the regular SL viewer - but don't run it.

OR

Try this if the above does not work:
http://www.linuxforums.org/forum/gaming-games-multimedia-entertainment/104105-how-firefox-calls-secondlife-slurls.html

Internet Explorer, Chrome and Safari

Download and install the regular SL viewer - but don't run it.

Mac OS X

The application that handles a URL is a system-wide setting, not tied to any one browser. You can change the setting like this:

  • Download RCDefaultApp 2.1 from the RubiCode download page. Yes, it really will run on current versions of OS X, even though it also runs all the way back to 10.2.
  • Install it according to the instructions int he README file.
  • Go to the Apple menu at the top left. Select System Preferences… then Default Apps (near the bottom), then the URLs tab. Now scroll down until you see secondlife in the list on the left. Click on it.
  • Now select the application you wish to use.

linux

  • Open Firefox and in the address bar type in “about:config”
  • Now right click anywhere on that page and choose New and then Boolean to create a new Boolean entry, when prompted for the name of the entry enter “network.protocol-handler.expose.secondlife” (without quotes) then set the entry to 'false', click ok and your just about done.
  • Now the next time you click a slurl you will be prompted to choose an application to open it with, just browse to the folder you installed Firestorm into and select the file named 'firestorm' (a shell script file). Then before you click Ok, make sure you check the little box to make Firefox remember your choice on how to open slurls. 1)

Information gleaned from this page.

Work Around

There is an alternative to clicking a link in a browser to have it pass control to the viewer. Some actually find this work around to be faster and use it normally:

  • right click the SLURL link in your web browser and copy to clipboard
  • in the viewer, paste the link into your local chat and hit Enter.
  • open local chat history
  • click the link shown there; you will be shown the location info with the option to teleport direct to it.

The fist thing to check is the viewer settings: Preferences → Network & Files → Connections, in the Web Browser section, make sure Use My Browser… is selected.

If you get an error saying that no program is associated with the action, or that it doesn't know how to hand that action, make sure your computer settings show that there is a default web browser. An easy way to tell is to open your browser; if you are asked to make it the default, then you need to do so.

1) With thanks to Eclair Mekanic.

graphics_presets - created

$
0
0
  • Presets: Three buttons which allow you to save, load or delete graphics settings presets.
    • To create a preset, set your graphics settings as you like. Click “Save” and give the preset a name.
    • To load a preset that you have created, click “Load” and choose the preset to load.
    • To delete one, click “Delete” and choose the preset to delete.
    • The presets can be accessed either from Preferences → Graphics → General or from the presets button in the upper right of the viewer, near the media and sound controls.

fs_older_downloads

$
0
0

Firestorm - Older Releases

The current release version of Firestorm is available here.

Firestorm 4.7.7 (48706) Release

“n/a” in the table below means “not available”.

Version32/64-bitGridsHavokLevel of SupportDownload
Windows
Windows
32-bit Havok
32 and 64 SL only X Full release Firestorm 4.7.7.48706 32 bit Windows setup.exe
SHA1 Checksum: D77B40B49370CEC519BAC68542C50FD328F33D53
Windows
32-bit OpenSim
32 and 64 SL and other grids Full release Firestorm 4.7.7.48706OS 32 bit Windows setup.exe
SHA1 Checksum: A3743695BE456B34538FD94AB5BD5830276AC452
Windows
64-bit Havok
64-bit only SL only n/a n/a
Windows
64-bit OpenSim
64-bit only
*Does not work on Vista
SL and other grids Full release Firestorm 4.7.7.48706OS 64 bit Windows Setup.exe
SHA1 Checksum: 6D9A61497D6367BFBDF7B253B8BE35DE0B89DD3A
Mac
Mac
32-bit Havok
32 and 64 SL only X Full release Firestorm 4.7.7.48706 Mac.dmg
SHA1 Checksum: A7E4D135A750F561360457AC2ED4BC5CEA3702DB
Mac
32-bit OpenSim
32 and 64 SL and other grids n/a n/a
Mac
64-bit Havok
32 and 64 SL only n/a n/a
Mac
64-bit OpenSim
32 and 64 SL and other grids Full release Firestorm 4.7.7.48706OS 64 bit Intel Mac.dmg
SHA1 Checksum: 01F700859F4FD84815A21F6CCDC156EF6B5F98F6
Linux
Linux
32-bit Havok
32 and 64 SL only X Full release Firestorm 4.7.7.48706 32 bit Linux.tar.bz2
SHA1 Checksum: 3039FDF660CF10061BB48D18106E8F615EF2762B
Linux
32-bit OpenSim
32 and 64 SL and other grids Full release Firestorm 4.7.7.48706OS 32 bit Linux.tar.bz2
SHA1 Checksum: E1D6571D2FB6767D967CD4DC876EE2E8AB5F38D3
Linux
64-bit Havok
64-bit only SL only n/a n/a
Linux
64-bit OpenSim
64-bit only SL and other grids Full Release Firestorm 4.7.7.48706OS 64 bit Linux.tar.bz2
SHA1 Checksum: 4B8BFC2A8BCC4AB18A767F1F24977A1BDB16B5C3

Firestorm 4.7.5 (47975) Release

“n/a” in the table below means “not available”.

Version32/64-bitGridsHavokLevel of SupportDownload
Windows
Windows
32-bit Havok
32 and 64 SL only X Old release Firestorm 4.7.5.47975 32 bit Windows setup.exe
SHA1 Checksum: 4BBCA7B524903E85D44F9CCB90C9F8BF2DB0E786
Windows
32-bit OpenSim
32 and 64 SL and other grids Old release Firestorm 4.7.5.47975OS 32 bit Windows setup.exe
SHA1 Checksum: 21F6BE62E349FB11D70FFD543BF8CFD87D1BCC42
Windows
64-bit Havok
64-bit only SL only n/a n/a
Windows
64-bit OpenSim
64-bit only SL and other grids Old release Firestorm 4.7.5.47975OS 64 bit Windows Setup.exe
SHA1 Checksum: 62A42665593DE240E427E5EEAC631392AEBCE5DF
Mac
Mac
32-bit Havok
32 and 64 SL only X Old release Firestorm 4.7.5.47975 Mac.dmg
SHA1 Checksum: 9604B6EE2E074A836C545AEE864E005AB72DA51B
Mac
32-bit OpenSim
32 and 64 SL and other grids n/a n/a
Mac
64-bit Havok
32 and 64 SL only n/a n/a
Mac
64-bit OpenSim
32 and 64 SL and other grids Old release Firestorm 4.7.5.47975OS 64 bit Intel Mac.dmg
SHA1 Checksum: 6B6F14A6D206797B1940B8BFD0F921E70DD2BDE6
Linux
Linux
32-bit Havok
32 and 64 SL only X Old release Firestorm 4.7.5.47975 32 bit Linux.tar.bz2
SHA1 Checksum: 1F81BA7A92D1EDDAD80D9B93ACE13871BC2FE72D
Linux
32-bit OpenSim
32 and 64 SL and other grids Old release Firestorm 4.7.5.47975OS 32 bit Linux.tar.bz2
SHA1 Checksum: 6321EF05C6085196565476336829156C11C0A447
Linux
64-bit Havok
64-bit only SL only n/a n/a
Linux
64-bit OpenSim
64-bit only SL and other grids Old release Firestorm 4.7.5.47975OS 64 bit Linux.tar.bz2
SHA1 Checksum: 4C81A6403E88BFFB400D185A51FBFD471B0825A1

Firestorm 4.4.2 (34167) - Mac OSX Only

NOTE: This version of Firestorm is only being offered for MacOS. It should only be used in cases where more recent versions don't work well for you. But please note that, given the many changes in SL since 4.4.2 was released, 4.4.2 will be badly broken for you anyway.
Also, Mac OSX 10.5 is not compatible with Firestorm 4.4.2.

Version32/64-bitGridsHavokRelease TypeDownload
Mac
32-bit Havok
32 and 64 SL only X Old release 4.4.2.34167 Intel Mac Download
SHA1 Checksum: ded94ad865d4c5897bb12ba28d663cf14d5ae15e
Mac
32-bit OpenSim
32 and 64 SL and other grids Old release 4.4.2.34167OS Intel Mac Download
SHA1 Checksum: bd8a9313c0f023c505e9ae85c8ec654df06a41ed

firestorm_classes

$
0
0

Firestorm Classes

These classes are based on our official Firestorm release and are conducted in voice and text except when otherwise noted. There's no need to talk, but you may want to be able to hear. We also usually have help available to answer questions in text. This schedule is subject to change.

Note that it is best if you are on Firestorm for the classes.

Locations are indicated in the far right column as follows:

Class times and days change regularly. Classes may be held any day of the week, with start times from 8am to 7pm SLT. Nonetheless, if the class times are still inconvenient you may prefer to watch recorded versions of some of these classes on YouTube.

*All times SLT*

Monday August 15 12:00PM – Menus 2 (TEXT ONLY)
We will cover the Advanced and Develop menus in the top bar.
FS
Wednesday August 17 11:00AM – Odds & Ends 2
Learn about fun and useful items like how to use Autocorrect, using the Command Line for a number of tools, and more.
FS
Thursday August 18 12:00PM – Contact Sets (TEXT ONLY)
There is a cool feature called Contact Sets that lets you organize your contact list. We will cover how to set them up and use this epic feature.
FS
Friday August 19 7:00PM – Odds & Ends 1
This class covers some of Firestorm's handiest features, like Inventory, Radar, and some hard-to-find gems.
FS
Saturday August 20 4:00PM – Reporting Bugs, Requesting Features
Learn how to communicate effectively with our devs to make the changes to Firestorm you want or need.
FS
Monday August 22 12:00PM – Preferences Set 2 (TEXT ONLY)
We will cover some of the Firestorm preferences (Graphics, Network & Cache), based on our current release.
FS
Tuesday August 23 4:00PM – Odds & Ends 2
Learn about fun and useful items like how to use Autocorrect, using the Command Line for a number of tools, and more.
FS
Thursday August 25 12:00PM – Preferences Set 1 (TEXT ONLY)
We will cover some of the Firestorm preferences (General, Chat, Privacy), based on our current release.
FS
Friday August 26 2:00PM – Backing up Settings and Logs
This class covers how to save your settings and chat logs on your computer. Recommended to take this before the Clean Install class.
FS
Monday August 29 12:00PM – Clean Install (TEXT ONLY)
Learn how to correctly and quickly perform this most fundamental and important of tasks. Recommended to take Settings Backup class first.
FS
Tuesday August 30 11:00AM – QuickPrefs Customization + Lag
Two mini-classes in one. One discusses the causes of lag in SL. The other explains how to customize your Quick Preferences.
FS
Thursday September 1 12:00PM – Menus 1 (TEXT ONLY)
We will be covering the menus on the top bar, from Avatar through Help.
FS
Friday September 2 2:00PM – Animation Overrider
On Firestorm, you can save scripts and HUD space by running your AO animations through the viewer. Learn how to set up and get the most out of this feature.
FS
Monday September 5 12:00PM – Odds & Ends 1 (TEXT ONLY)
This class covers some of Firestorm's handiest features, like Inventory, Radar, and some hard-to-find gems.
FS

fs_avatar_complexity_settings - [Avatar complexity slider]

$
0
0

Avatar Complexity Settings Cheat Sheet

To see your own avatar complexity at any time

Go to Avatar → Appearance and look at the bottom right of the window.

Avatar complexity slider

  • This determines which avatars will appear as jellydolls to you, based on their complexity.
  • Go to Preferences → Graphics → General → Maximum Complexity.
  • Note: Lowering this slider will decrease your lag and turn more avatars into jellydolls; raising the slider may lag you but more avatars will be fully visible.
  • Note: Moving this slider all the way to the right is not advised, as this sets this setting to “No Limit” — which means that no avatars will render as jellydolls to you, but you will be subject to lag and worn graphics crashers.

To turn specific avatars into jellydolls, or render them fully

  • Right click on the avatar's name tag and choose from the menu:
    • Render Normally – avatar will be affected by your complexity slider (above)
    • Do Not Render – avatar will be a jellydoll for you
    • Render Fully – avatar will be rendered fully even if over your complexity slider setting
  • In the pie menu, these options are under More → More → Render.

Show/hide avatar complexity information in name tags

  • Go to Preferences → General and set “Show Avatar Complexity,” “Only if too complex,” and “Show own complexity” as you wish.

Show/hide warning about your avatar being too complex for others to see you

  • This appears in the top right of your screen.
  • Go to Preferences → Notifications → Alerts, and move “Warn me if my avatar complexity may be too high” to the “Always show” box or to the “Never show” box, as you prefer.

Show/hide the display of your complexity changes

  • This appears in the upper right of your screen when you change clothes/accessories.
  • Go to Advanced menu → Show Debug Settings → ShowMyComplexityChanges, and set that to zero to hide it, or a larger value to show it. Please make a note of this debug in case you need to activate it again.

Additional complexity info in hover text

  • This shows complexity plus rank and area in hover text over avatars.
  • Go to Avatar menu → Avatar Health → Show Avatar Complexity Information
  • Note: The height of this hovertext cannot be adjusted.

How to find out the rendering weight of a specific item

Two methods:

  • Wear the item and then remove it, noting the change to your avatar complexity in the upper right of the viewer.
  • Wear the item. Edit it → in the Build floater, click “more info” → and see the number listed for “Display.”

Default complexity settings

These are the default settings that determine the threshold at which you view avatars fully rendered or as jellydolls. They correspond with the “Quality and Speed” slider located in Preferences → Graphics → General. When the settings are left at these defaults, avatars whose complexity numbers are below these thresholds will be visible, while avatars with higher complexities will appear as jellydolls to you.

  • Low: 35,000
  • Low-Mid: 100,000
  • Mid: 200,000
  • Mid-High: 250,000
  • High: 300,000
  • High-Ultra: 350,000
  • Ultra: 350,000

fs_compiling_firestorm - [Compiling Firestorm Viewer]

fs_ao_folder - [My Firestorm AO Is Suddenly Empty]

$
0
0

I Dragged Something into the AO Folder and Can't Get it Out!

The #Firestorm → AO folder is protected; this means it cannot be deleted, nor can items in it be removed.

If you have inadvertently dragged something into this folder (or a subfolder), then proceed as follows:

  • From the top menu bar select the Advanced menu, then Debug Settings - or press Ctrl-Alt-Shift-S (if the Advanced menu is not visible, enable it with Ctrl-Alt-D).
  • Type in ProtectAOFolders, and set the value to FALSE.
  • Now drag the item(s) out of the protected folder and into the intended location.
  • Access Debug Settings again, and revert the value of ProtectAOFolders to TRUE.

My Firestorm AO Is Suddenly Empty

If you had a functioning FS AO and it is now empty, it is possible that the #Firestorm → #AO folder has accidentally moved to another location.

To find the moved #AO folder, do an inventory search either for “#AO” (probably the simplest way), or in case that doesn't work, for one of the known animation names. The search will reveal both the original animation and any link to it. The link should reveal the location of the moved #AO folder. Check to see that the moved folder contains all the expected subfolders and animations.

To move the full #AO folder back into the correct location,

  • Unprotect the new, empty #Firestorm → #AO folder by going to Advanced menu → Show Debug Settings. Type in ProtectAOFolders and set to False
  • Delete the new, empty #Firestorm → #AO folder
  • Move the full #AO folder back into the #Firestorm folder
  • Protect the full #AO folder by going to Advanced menu → Show Debug Settings. Type in ProtectAOFolders and set to True. (Note: if this doesn't work, a relog may be needed, followed by setting it to True.)

fs_compiling_firestorm_32bit_ubuntu_16

$
0
0

Building Firestorm in 32-bit Ubuntu 16.04

There is no official support for compiling or operating self-compiled viewers. Unofficial support options are listed at the bottom of this page.

This procedure is used for building a non-standalone viewer on 32-bit Ubuntu 16.04 LTS systems and was tested on a fresh installation within a virtual guest. This procedure assumes that your Ubuntu system has been properly updated, and also assumes any derivative system (eg.: Mint) includes all the standard Ubuntu libraries.

Establish your programming environment

This is needed for compiling any viewer based on the LL open source code and only needs to be done once.

Install Required Tools

The required tools are:

bison bzip2 cmake curl flex g++ 4.7 m4 (for make) mercurial (for hg) python newer than 2.4.3 but not 3.0 python development pip llbase
sudo apt-get update # to make sure the repository list is current
sudo apt-get upgrade # to make sure all installed packages are current
sudo apt-get install --install-recommends bison bzip2 cmake curl flex g++-4.7 m4 mercurial python python-dev python-pip
sudo pip install --upgrade pip # The version in the repository is not the latest version
sudo pip install llbase

(the –install-recommends flag tells apt-get to install all packages recommended by each named package.)

In case you have multiple versions of g++ installed, which is possible, we need to identify 4.7.x as the default version.

update-alternatives --remove-all gcc 
update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.7 47 --slave /usr/bin/g++ g++ /usr/bin/g++-4.7 --slave /usr/bin/gcov gcov /usr/bin/gcov-4.7
update-alternatives --config gcc

It doesn't hurt to run those commands if you only have one g++ version installed.

Install Required Libraries

These libraries may be included with your distribution, and some may be automatically installed as dependencies for the tools you just installed:

libc.so (libc6-dev) libGL.so (libgl1-mesa-dev) LibGLU.so (libglu1-mesa-dev) libstdc++.so.6 (libstdc++6)
libx11.so (libx11-dev) libxinerama.so (libxinerama-dev ) libxml2.so (libxml2-dev) libXrender.so (libxrender-dev)
sudo apt-get install --install-recommends libc6-dev libgl1-mesa-dev libglu1-mesa-dev libstdc++6 \
  libx11-dev libxinerama-dev libxml2-dev libxrender-dev 

You can optionally install doxygen to eliminate related errors, but it is not needed to build Firestorm

sudo apt-get install --install-recommends doxygen

Install Autobuild

Autobuild is a Linden Lab resource that does all the hard work. For Firestorm, you will need a modified version of autobuild from one of our Developers.

sudo hg clone https://bitbucket.org/NickyD/autobuild-1.0 /opt/autobuild
ln -s /opt/autobuild/bin/autobuild /usr/bin/autobuild 

Set up your source code tree

Plan your directory structure ahead of time. If you are going to be producing changes or patches you will be cloning a copy of an unaltered source code tree for every change or patch you make, so you might want to have all this work stored in its own directory. If you are a casual compiler and won't be producing any changes, you can use one directory. This document will refer to src in your home directory, ~/src.

cd ~/src

There are several repositories but the one we are after is the development repository. You can grab all the sources if you wish, but but keep in mind that each FS source requires around 110MB initially and around 4.3GB after the binaries have been built, plus possible compiling overhead.

hg clone http://hg.phoenixviewer.com/phoenix-firestorm-lgpl

It will create a folder called phoenix-firestorm-lgpl. You can choose a different destination folder by adding that folder's name to the end of the command, such as:

hg clone http://hg.phoenixviewer.com/phoenix-firestorm-lgpl firestorm-source

The rest of this document will assume the default directory, phoenix-firestorm-lgpl

Cloning the Firestorm repository can take a bit, it's a rather large download. On a slow network, it may fail, and this script can help:

pull_in_chunks.sh
#!/bin/bash
 
cd ~/src
hg clone -r 10000 http://hg.phoenixviewer.com/phoenix-firestorm-lgpl
cd phoenix-firestorm-lgpl
for i in {15000..40000..5000}
do
	echo "Grabbing to change $i"
	hg pull -u -r $i
done
echo "Grabbing to tip"
hg pull -u
cd ~/src

Configuring the Viewer

cd ~/src/phoenix-firestorm-lgpl
autobuild configure -c ReleaseFS_open

This will set up to compile with all defaults and without third party libraries. It will fetch any additional necessary libraries.

Configuration Switches

There are a number of switches you can use to modify the configuration process. The name of each switch is followed by its type and then by the value you want to set.

  • LL_TESTS (bool) controls if the tests are compiled and run. There are quite a lot of them so excluding them is recommended unless you have some reason to need one or
    more of them.
  • clean will cause autobuild to remove any previously compiled objects and fetched packages. It can be useful if you need to force a reload of all packages
  • package will result in a bzip2 archive of the completed viewer. Enabled by default, you would have to use -DPACKAGE:BOOL=Off to disable it

TIP: OFF and NO are the same as FALSE; anything else is considered to be TRUE

Examples:

autobuild configure -c ReleaseFS_open -- --clean -DLL_TESTS:BOOL=FALSE
autobuild configure -c ReleaseFS_open -- --clean

The first time you configure, several additional files will be downloaded from Firestorm and Second Life sources. These are mostly binary packages maintained outside the viewer development itself. And if you use the –clean switch, you will re-download them all.

Compiling the Viewer

autobuild build -c ReleaseFS_open

Now, sit back, read War and Peace, calculate PI to 50 places, tour the country, whatever you desire. Compiling can take quite a bit of time depending on your computer's processing power.

NOTE: It is possible to use autobuild to do both the configure step (only needed once) and the build step with one command (autobuild build -c ReleaseFS_open [– switches] . For clarity, they are mentioned separately.</WRAP>

Running your newly built viewer

Running from a menu item

Create the desktop launcher

cd ~/src/phoenix-firestorm-lgpl/build-linux-i686/newview/packaged/etc
./refresh_desktop_app_entry.sh

Then open your applications menu and look in the Internet or Network branch for the Firestorm launcher.

Running from command line or file browser

cd ~/src/phoenix-firestorm-lgpl/build-linux-i686/newview/packaged
./firestorm

"Installing" the viewer

You can copy or move the contents of ~/src/phoenix-firestorm-lgpl/build-linux-i686/newview/packaged to another location if you choose, and then launch firestorm from there. Example:

mkdir ~/Firestorm
cp -a ~/src/phoenix-firestorm-lgpl/build-linux-i686/newview/packaged/* ~/Firestorm
cd ~/Firestorm
./firestorm # or etc/refresh_desktop_app_entry.sh to create a desktop launcher

Troubleshooting

Handling problems

If you encounter errors or run into problems, please first double check that you followed the steps correctly. One typo can break it. Then, check whether someone else already had the same issue. A solution might be known already.

  • IRC:The #phoenixviewer-dev channel is the best place to look for solutions.
    A lot of self-compilers and project developers hang out there and are ready to help you.
  • Jira:JIRA may contain resolved tickets.
    Search using the error you encountered.
  • Included documentation: In the Firestorm root folder are several “README” documents. You should make yourself familiar with their content, even if they appear to be out of date.

If you found a procedural error in this document, please let us know in as much detail as you can, either contact the author (preferred) or discuss on IRC.

Common Issues/Bugs/Glitches And Solutions

  • Missing libraries/applications/packages This may occur if you did not or could not install the listed packages. The packages do exist in the default Ubuntu repositories, so make sure you did not disable those. If you find that a library or application is in a different package for your system, contact the author with the name of the library or application, the name of its package and your Linux OS so that information can be checked and added here.
  • Delayed sounds Some users have noted that OpenAL plays sounds from the viewer up to 20 seconds after they are triggered. There is no solution to this via the viewer, but there may be some solutions on the Internet
  • Voice Won't Connect It was observed in testing that voice would not connect and no devices could be selected in Preferences ⇒ Sound & Media ⇒ Voice ⇒ Audio Device Settings. This was resolved by replacing Firestorm/lib/libvivoxal.so.1 with a copy from release.

fs_compiling_firestorm_64bit_ubuntu_16

$
0
0

Building Firestorm in 64-bit Ubuntu 16.04

There is no official support for compiling or operating self-compiled viewers. Unofficial support options are listed at the bottom of this page.

This procedure is used for building a non-standalone viewer on 64-bit Ubuntu 16.04 LTS systems and was tested on a fresh installation within a virtual guest. This procedure assumes that your Ubuntu system has been properly updated, and also assumes any derivative system (eg.: Mint) includes all the standard Ubuntu libraries.

Establish your programming environment

This is needed for compiling any viewer based on the LL open source code and only needs to be done once.

Install Required Tools

The required tools are:

bison bzip2 cmake curl flex g++ 4.7 m4 (for make) mercurial (for hg) python newer than 2.4.3 but not 3.0 python development pip llbase
sudo apt-get update # to make sure the repository list is current
sudo apt-get upgrade # to make sure all installed packages are current
sudo apt-get install --install-recommends bison bzip2 cmake curl flex g++-4.7 m4 mercurial python python-dev python-pip
sudo pip install --upgrade pip # The version in the repository is not the latest version
sudo pip install llbase

(the –install-recommends flag tells apt-get to install all packages recommended by each named package.)

In case you have multiple versions of g++ installed, which is possible, we need to identify 4.7.x as the default version.

update-alternatives --remove-all gcc 
update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.7 47 --slave /usr/bin/g++ g++ /usr/bin/g++-4.7 --slave /usr/bin/gcov gcov /usr/bin/gcov-4.7
update-alternatives --config gcc

It doesn't hurt to run those commands if you only have one g++ version installed.

Install Required Libraries

These libraries may be included with your distribution, and some may be automatically installed as dependencies for the tools you just installed:

libc.so (libc6-dev) libGL.so (libgl1-mesa-dev) LibGLU.so (libglu1-mesa-dev) libstdc++.so.6 (libstdc++6)
libx11.so (libx11-dev) libxinerama.so (libxinerama-dev ) libxml2.so (libxml2-dev) libXrender.so (libxrender-dev)
sudo apt-get install --install-recommends libc6-dev libgl1-mesa-dev libglu1-mesa-dev libstdc++6 \
  libx11-dev libxinerama-dev libxml2-dev libxrender-dev 

You can optionally install doxygen to eliminate related errors, but it is not needed to build Firestorm

sudo apt-get install --install-recommends doxygen

Install Autobuild

Autobuild is a Linden Lab resource that does all the hard work. For Firestorm, you will need a modified version of autobuild from one of our Developers.

sudo hg clone https://bitbucket.org/NickyD/autobuild-1.0 /opt/autobuild
ln -s /opt/autobuild/bin/autobuild /usr/bin/autobuild 

Set up your source code tree

Plan your directory structure ahead of time. If you are going to be producing changes or patches you will be cloning a copy of an unaltered source code tree for every change or patch you make, so you might want to have all this work stored in its own directory. If you are a casual compiler and won't be producing any changes, you can use one directory. This document will refer to src in your home directory, ~/src.

cd ~/src

There are several repositories but the one we are after is the development repository. You can grab all the sources if you wish, but but keep in mind that each FS source requires around 110MB initially and around 4.3GB after the binaries have been built, plus possible compiling overhead.

hg clone http://hg.phoenixviewer.com/phoenix-firestorm-lgpl

It will create a folder called phoenix-firestorm-lgpl. You can choose a different destination folder by adding that folder's name to the end of the command, such as:

hg clone http://hg.phoenixviewer.com/phoenix-firestorm-lgpl firestorm-source

The rest of this document will assume the default directory, phoenix-firestorm-lgpl

Cloning the Firestorm repository can take a bit, it's a rather large download. On a slow network, it may fail, and this script can help:

pull_in_chunks.sh
#!/bin/bash
 
cd ~/src
hg clone -r 10000 http://hg.phoenixviewer.com/phoenix-firestorm-lgpl
cd phoenix-firestorm-lgpl
for i in {15000..40000..5000}
do
	echo "Grabbing to change $i"
	hg pull -u -r $i
done
echo "Grabbing to tip"
hg pull -u
cd ~/src

Configuring the Viewer

cd ~/src/phoenix-firestorm-lgpl
autobuild configure -c ReleaseFS_open

This will set up to compile with all defaults and without third party libraries. It will fetch any additional necessary libraries.

Configuration Switches

There are a number of switches you can use to modify the configuration process. The name of each switch is followed by its type and then by the value you want to set.

  • LL_TESTS (bool) controls if the tests are compiled and run. There are quite a lot of them so excluding them is recommended unless you have some reason to need one or
    more of them.
  • clean will cause autobuild to remove any previously compiled objects and fetched packages. It can be useful if you need to force a reload of all packages
  • package will result in a bzip2 archive of the completed viewer. Enabled by default, you would have to use -DPACKAGE:BOOL=Off to disable it

TIP: OFF and NO are the same as FALSE; anything else is considered to be TRUE

Examples:

autobuild -m64 configure -c ReleaseFS_open -- --clean -DLL_TESTS:BOOL=FALSE
autobuild -m64 configure -c ReleaseFS_open -- --clean

The first time you configure, several additional files will be downloaded from Firestorm and Second Life sources. These are mostly binary packages maintained outside the viewer development itself. And if you use the –clean switch, you will re-download them all.

Compiling the Viewer

autobuild -m64 build -c ReleaseFS_open

Now, sit back, read War and Peace, calculate PI to 50 places, tour the country, whatever you desire. Compiling can take quite a bit of time depending on your computer's processing power.

NOTE: It is possible to use autobuild to do both the configure step (only needed once) and the build step with one command (autobuild -m64 build -c ReleaseFS_open [– switches] . For clarity, they are mentioned separately.</WRAP>

Running your newly built viewer

Running from a menu item

Create the desktop launcher

cd ~/src/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged/etc
./refresh_desktop_app_entry.sh

Then open your applications menu and look in the Internet or Network branch for the Firestorm launcher.

Running from command line or file browser

cd ~/src/phoenix-firestorm-lgpl/build-linux-i686/newview/packaged
./firestorm

"Installing" the viewer

You can copy or move the contents of ~/src/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged to another location if you choose, and then launch firestorm from there. Example:

mkdir ~/Firestorm64
cp -a ~/src/phoenix-firestorm-lgpl/build-linux-x86_64/newview/packaged/* ~/Firestorm64
cd ~/Firestorm64
./firestorm # or etc/refresh_desktop_app_entry.sh to create a desktop launcher

Troubleshooting

Handling problems

If you encounter errors or run into problems, please first double check that you followed the steps correctly. One typo can break it. Then, check whether someone else already had the same issue. A solution might be known already.

  • IRC:The #phoenixviewer-dev channel is the best place to look for solutions.
    A lot of self-compilers and project developers hang out there and are ready to help you.
  • Jira:JIRA may contain resolved tickets.
    Search using the error you encountered.
  • Included documentation: In the Firestorm root folder are several “README” documents. You should make yourself familiar with their content, even if they appear to be out of date.

If you found a procedural error in this document, please let us know in as much detail as you can, either contact the author (preferred) or discuss on IRC.

Common Issues/Bugs/Glitches And Solutions

  • Missing libraries/applications/packages This may occur if you did not or could not install the listed packages. The packages do exist in the default Ubuntu repositories, so make sure you did not disable those. If you find that a library or application is in a different package for your system, contact the author with the name of the library or application, the name of its package and your Linux OS so that information can be checked and added here.
  • Delayed sounds Some users have noted that OpenAL plays sounds from the viewer up to 20 seconds after they are triggered. There is no solution to this via the viewer, but there may be some solutions on the Internet
  • Voice Won't Connect It was observed in testing that voice would not connect and no devices could be selected in Preferences ⇒ Sound & Media ⇒ Voice ⇒ Audio Device Settings. This was resolved by replacing Firestorm/lib/libvivoxal.so.1 with a copy from release.

fs_voice - [Known Issues]

$
0
0

Voice Issues

Please note: Viewers play a minor part in voice functionality. The bulk of voice support is given by the external application called SLVoice, which is made by the SL voice provider, Vivox. Voice failures are almost always due to one of the following reasons:

  • Your ISP is throttling or blocking the voice service;
  • failure of the Vivox service;
  • voice issues on the region you are on;
  • voice being throttled by bandwidth set incorrectly - please check it by following the instructions here;
  • voice hardware (mic, headset) not configured correctly in your operating system settings;
  • voice hardware not configured correctly in the viewer;
  • another application has your voice hardware in use (example, Skype);
  • your anti virus software has “mangled” the voice application; see here.
  • your firewall is blocking slvoice. Add slvoice to your firewall's exclusion/allow list.

Please go to Voice Echo Canyon when trying to get voice to work. If voice is working correctly for you, anything you say there will be echoed back to you. Once there, relog to last location.

Known Issues

Since 4.7.9, voice has not always connected to the voice servers. This is due to some coding issues that we inherited from the official SL viewer and that code's interaction with the latest voice files. The issue is documented on LL's Jira. A workaround is to disable and then re-enable voice. But if you're presented with the voice connection failure message that tells you “Voice communications will not be available”, you may need to disable voice and then relog before voice will try to reconnect.

Check Voice Settings in your Operating System

Due to the many different versions of each operating system (Windows, linux distros, Mac OSx's), it is very difficult to give specifics for each one. Nonetheless, make sure that your operating system is correctly configured for voice: that voice is going to your headset (or speakers, as you prefer), and that your mic is enabled and configured.

Check Voice Settings in the Viewer

  • Go to PreferencesSound & Media -> Sounds. Find the Voice Chat slider and make sure it is not all to the left. Try increasing the volume.
  • Make sure that Voice chat is enabled on that preferences tab.
  • go to PreferencesSound & Media -> Voice. Click on Audio Device Settings. For Input and Output, use the dropdowns to select your voice devices (headset, microphone, whatever you use). It is best not to leave these at Default.
  • Close Preferences and locate the Mic button on the button bar. Click the Lock checkbox then the actual button, and try speaking (hopefully, you went to Voice Echo Canyon so you can test).

If voice still does not work, then continue working through this page.

Voice is Intermittent

If you find that voice cuts in and out, particularly right after a TP, and at the same time, you notice that things are not rezzing in for you very well (avatars, objects, etc), then the likely cause is that your router is being “overwhelmed” with texture transfers. So reboot your router/modem, and then your computer, and see if the problem is solved.

You can also try adjusting your bandwidth as explained here.

If that does not help, then proceed with the section below.

Voice Worked Fine but Suddenly Doesn't Work

Chances are good that the problem lies with the SL servers or the voice provider, Vivox. Still, there are things you can try:

  • Open Preferences, and go to Sound & Media → Voice, and click Reset (circular arrow).
  • Shut down all applications that use, or can use, voice - like Skype, etc. Then relog.
  • What sometimes helps to get voice working is disabling voice in PreferencesSound & Media -> Voice, hitting apply, waiting a minute and then enabling voice and hitting apply. When these methods fail (assuming voice usually works for you) it is usually the Vivox voice servers that are the problem.
  • If this does not work at your current location, go to a region where other people are able to use voice at this time. One possibility is Firestorm Social, but any region where voice is known to be functioning is fine. Disable voice in PreferencesSound & Media -> Voice. Relog, using the last location selection on your login screen. Wait a couple of minutes. Reenable voice. Wait another couple of minutes (in other words, give the connection time to be established). If voice comes on, then the problem may have been the region you were in before. Was voice disabled there? If not, a region restart might solve the problem.
  • Go to Preferences → Network & Files -> Connection and reduce your bandwidth setting to 500 (if it is not already set there). Repeat the above step to toggle voice off and back on. See here for more information on setting your bandwidth properly, but bear in mind that lower levels than those calculated there may be necessary for troubleshooting purposes.
  • Try a relog, or even a reboot of the computer.
  • Sometimes device settings can reset, so check in PreferencesSound & Media -> Voice→ Audio Device Settings, to be sure that the input and output are set correctly.
  • HTTP fetching may be overloading your router; please try the suggestions given here; if they do not help, revert the changes made then return to this page and continue.

Never Been Able to Get Voice to Work

  • Does your headset/microphone work outside of SL? ie when using Skype, Yahoo or MSN
  • Is your voice chat volume turned up and not muted?
  • Is the SLVoice.exe (simply SLVoice on Mac) that is in the Firestorm folder in the exceptions/allowed list for your firewall? If your firewall is turned off, turn it on and add the SLVoice.exe (or SLVoice) anyway.
  • Check the bandwidth you are actually getting and what you have set in Preferences → Network & Files → Connection. Please refer to this page for specifics.
  • Go to Advanced → Debug Settings, and in the window that opens, type: Cmdlinedisablevoice - then ensure this is set to FALSE.

Windows-specific


Don't do this section if using Firestorm 4.6.5.40833.

Some have issues with voice on Firestorm - specifically, “stuttering”, or SLVoice crashing when you unplug a USB device. The only work-around currently is to swap out the voice files.

  • Method One:
    To this end, download this file; save it to your hard drive. Make sure you do not have Firestorm running. Then extract the files to your Firestorm install folder. (For Firestorm 32-bit viewer, this is typically located at C:\Program Files\Firestorm on 32 bit Windows, and C:\Program Files (x86)\Firestorm on Windows 64-bit. For Firestorm 64-bit Viewer, this is typically located at C:\Program Files\Firestorm.) When prompted, allow the replacement of existing files.
  • Method 2 - Firestorm 4.7.3 Only:
    Download Firestorm 4.6.9 from here. If you current have FS 64-bit, get FS 4.6.9 32-bit - and vice versa. Go into your “computer” and find the the 4.6.9 Version Firestorm you downloaded.
    Copy the files below and replace them in your 4.7.3 Firestorm install folder:
    ca-bundle.crt
    ortp.dll
    SLVoice.exe
    vivoxoal.dll
    vivoxplatform.dll
    vivoxsdk.dll
Windows Vista and Windows 7

Try disabling compatibility mode, if enabled:

  • Locate your desktop shortcut for Firestorm
  • Right click on the icon and select Properties
  • Select the Compatibility tab
  • Find “Run this program in compatibility mode for:” if it is set then disable this
  • Make sure “Run as Administrator” is enabled (if this is greyed out, then you're probably already running as administrator, so you can ignore this step).
  • Click Apply.
  • Now log back into the viewer, and see if voice works (do you have the white dot over your head?). If not, go to PreferencesSound & Media -> Voice and disable voice; wait a few moments, then re-enable. 1)

On Windows 7, if you find yourself being able to talk but not hear what others say, then a possible solution is to use the sound drivers from Vista. (This needs further confirmation.)

Check that slvoice.exe is not muted in the speaker/headphones icon (located in the notification area) → mixer.

Linux-specific

Every linux distro is different; and each distro may have more than one window manager to further complicate things. So tips can't be “absolute”; you will need to experiment and see what works for you. The following have been suggested by some as effective. But first….

In the Firestorm install directory, there's a text file (originally from LL) with tips on getting voice to work in linux. If you haven't read that, then you can try to see if it helps.

  • Make sure you have ALSA and/or FMODEX available. FMODEX is supplied with Firestorm, normally. If you look at Help → About Firestorm, you should see a line that resembles this:
    Audio Driver Version: OpenAL, version 1.1 ALSOFT 1.11.753 / OpenAL Community / OpenAL Soft: PulseAudio Software
    If that says “none” then you have no audio driver available to Firestorm and need to install one.
  • Edit the firestorm shell script and remove the #. That will force LL to use FMOD rather than ALSA. Some say this is how to get voice working.
#export LL_BAD_OPENAL_DRIVER=x
  • Some swear that the problem is PulseAudio, so you can try to remove that from your system. Be warned, however, that this could cause more problems than it solves. Make sure you remove only Pulse and not half the OS.
  • Be sure to have the correct devices select in Firestorm for voice:

    Preferences → Sound & Media → Voice → Audio Device Settings (button) … input and output may not work if left at default; they may need to go to a specific device like “ALSA Capture on [device name]”.

Below are results for selected linux distros, based on input from Phoenix and Firestorm users. This will be updated as more information becomes available.

  • ubuntu 16.04 64 bit + FS64: The following command installs a few 32-bit libs and voice works after. Maybe you need fewer 32-bit libs but that needs further investigation.
    Apparently, arch requires these as well - or some of them - though the exact lib name may be different.
sudo apt-get install gstreamer0.10-pulseaudio:i386 libidn11:i386 libuuid1:i386 libstdc++6:i386
  • A new option in Firestorm 4.7.9 is a debug setting, FSLinuxEnableWin32VoiceProxy, which when enabled will cause Firestorm to launch the Windows version of SLVoice.exe via WINE. To use this, you need to ensure that WINE is installed; install WINE with your package manager. An existing WINE profile/prefix is not needed, but will be used if present. Depending on your system, it may take several seconds before voice comes up.
    NOTE: if you disable voice and then re-enable too quickly, it may fail to re-enable. If you get the warning that there was a problem connecting, you will need to relog before voice will re-enable. Thirty seconds between disable and enable should be enough.
    Also note that there is a known related issue here

Mac-specific

All Mac Operating Systems

If you are unable to connect to voice and you are also having problems with teleporting and/or loading your friends list, perhaps along with other things, then see the “Mac-specific” section of this page for instructions and more explanation.

Mountain Lion (10.8.x) Only

Some Mountain Lion users experience a problem with voice output, while input works fine (that is, you can hear but you can't speak). To fix this, open the voice preferences for your viewer (PreferencesSound & Media -> Voice in Firestorm). Click the device settings button and select “built-in microph” as the audio input device and click OK. (OK is important, Apply doesn't work.) Reopen Preferences and go back to the device settings button to ensure you're getting sound in on the mic.



See this page for documentation on Firestorm 4.6.9 (42969) and earlier.

1) Incorporates suggestions from user Maverick Buccaneer.

fs_run_crash - Added All Else Fails section

$
0
0

Crashing While Running Firestorm

If you find that you are crashing frequently, then perhaps the suggestions here will be helpful. Please don't skim the page - read it carefully.

It is important to distinguish between two things….

Being logged out or disconnected

If a small window appears, saying that you have been logged out of SL, this isn't a crash. Rather, SL is disconnecting you, for one of a number of reasons, including:

  • The region you are in is going down;
  • During teleport, the SL servers may fail to hand you over to your destination and so log you out; help on that is given here.
  • Your network connection has gone down;
  • Your network connection has become poor or unreliable and SL has lost contact with your avatar.

Things to try - in order:

  • reboot your router/modem, then your computer;
  • make sure your bandwidth is set correctly - follow the instructions hereexactly as given;
  • shut down any other programs that are making heavy use of your network connection, such as torrents;
  • If you use Mac with Yosemite, see if this might be your case.
  • If the problems persist still, try changing your DNS to Google, as explained here.

Being Logged Out While Editing Appearance

If you are being logged out when you edit appearance, or edit shape, or use the Appearance toolbar button, did you drop items into the Outfits folder that were not created via the Outfits/Appearance window? If so, remove those items.

Crash

Firestorm itself has crashed. The remainder of this page offers possible solutions.

  • Update your Operating System. See the advice from LL, and the reasons behind it, here.
  • (Windows-only)
    • If you are using an ATI (AMD) graphics card, then please refer here for known problems with these cards.
    • For nVidia users, please refer to this page.
    • Also for nVidia: if you recently updated your drivers and are experiencing crashes, try reverting to an older driver that worked for you.
  • In Preferences → Graphics → General, reduce Draw Distance by at least half (or more). Also reduce Max # non-impostor avatars.
  • Disable VBO: Run Firestorm and before logging in, press Ctrl-P to bring up the Preferences window. Then click on Graphics → Hardware Settings tab. Make sure that “Enable OpenGL Vertex Buffer Objects” is not checked.
  • Several creators recommend specific settings in order for you to be able to better see their products. Sadly, some of these recommendations will lead to many people crashing more. For example:
    • RenderVolumeLODFactor should never be set over 4; a good value is between 2 and 3.
    • TextureLoadFullRes should never be enabled.
  • (Grids other than SL only!) Disable HTTP Get Textures: Open the preferences window, then click on Graphics → Rendering tab. Make sure “Use HTTP Textures” is not checked. Please clear your cache if you change this setting.
  • It is possible that your graphics settings are set higher than your computer can handle. To see if this is the case, go to Preferences → Graphics, and click on Reset (the circular arrow to the right of the quality slider). After doing this, you may still need to reduce Draw Distance and Max # non-impostor avatars, as mentioned above.
  • If you have Shadows turned on, try turning them off. See this page for more side effects of shadows.
  • Another thing you can try is: Develop → World → Dump Region Object Cache, then relog. (The Develop menu is revealed with Ctrl-Alt-Q, if you cannot see it.) This sometimes also helps deal with odd texture issues; it may need to be done several times.
  • If clicking on a link or SLURL in Firestorm causes an instant crash: do you have AVG 2011 installed? If so, it probably flagged SLPlugin as malware. See here for more on this.
  • If you are crashing when you try to upload a texture, please try disabling VBO, as described above. Also, if you are on Windows and running Microsoft SkyDrive, prefer refer here. If you are on a Mac, this workaround may fix the problem.

If All Else Fails

If you have eliminated all the possible causes for the crash and you are still crashing, it's time to submit a Support Request on our jira. In that request, you can include screenshots or videos, if they will help clarify your description, as well as your sysinfo and viewer event logs. Follow the steps in this link to create the request and add your logs.

huds_not_working

$
0
0

HUDs Are Not Working

Things to try:

  • Check for location issues:
    • Make sure you are in a region that has scripts enabled.
    • Go to other regions and test the HUDs there. This will rule out technical problems with the original region.

Stay in a script-enabled region to do all of the following:

  • Attempt to get scripts running:1)
    • Try removing and reattaching the HUDs.
    • If the HUDs are modifiable, try resetting them or setting their scripts to running: Inventory, right-click the item → Edit, and while it is in Edit, go to Build menu → Scripts → Reset Scripts, or Build menu → Scripts→ Set Scripts to Running).
  • Identify broken HUDs:
    • Try removing all the HUDs and testing them one at a time: test each one, then remove it, then test another.
    • If you have original copies of the HUDs, try detaching the ones you are currently wearing and using a fresh copy from the original.
    • If a HUD is no-mod and you can't get it to start running again, and you don't have another copy, you will need to request a new copy from the creator.
  • Check for interference:
    • Look in Inventory > Current Outfit folder, and see if you are wearing any HUDs you were not aware of. (Note: HUDS do not necessarily have “HUD” in the name.) This could include temporary “Experience” HUDS that you may not be aware were attached.2)
    • Check that HUDs are not overlapping each other on the screen (and so preventing you from clicking).
  • Check for issues with attachment points:
    • If any HUDs are sharing the same HUD attachment point, try moving them to separate HUD attachment points:
      Inventory → Right-click → Detach from Yourself, then Inventory → Right-click → Attach to HUD, and choose an unused point.
    • Even if they are not sharing attachment points, try moving them to different attachment points.
  • Test basic functionality:
    1. Rez a fresh cube
    2. Add the default script to it
    3. Take it into inventory
    4. Attach it to a HUD point
    5. Touch the HUD and see if there is script output
1) There are griefing objects that can be rezzed on a region; anyone who goes there will have their HUDs and all other scripted attachments put into a non-running state. For instance: a HUD for a mesh body, and all the mesh body parts you are wearing, may be broken at the same time.
2) Temp HUDS have been known to freeze other HUDs on the same attachment point.
Viewing all 5258 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>