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

fs_inspect_511.png - created


fs59_edit_features.png - created

fs511_edit_object_mesh.png - created

fsg_gateway_team

$
0
0

fs_compiling_firestorm

phoenix:phoenix_restrained_love_support_rlva - old revision restored (2014/06/18 22:58)

$
0
0

Phoenix Viewer: How to set up Restrained Love (RLVa)

Phoenix Enable RLVa Preferences

To use the Restrained Love features built in to Phoenix, you need to follow a few simple steps:

  • Press CTRL-P to open the Preferences panel.
  • Go to Phoenix
  • Move on to Page 1
  • Click on Misc
  • Check on “Enable Restrained Love [RLVa] features”

After this you have to restart Phoenix to get RLVa working. Additionally you usually need to get a so-called Relay. This is an attachment you wear that enables objects in-world to interact with your viewer. These Relays are usually free of charge and come as HUDs or pieces of jewelry you wear. It's recommended to get a “Multi Relay”, so you can be controlled by more than one device at the same time.

If you also want to enable traps and toys to put folders into your inventory, you need go through a few additional steps:

  • Click on the Phoenix menu
  • Check on Show Advanced
  • Click on the Advanced menu
  • Select RLVa
  • UncheckForbid Give to #RLV
  • Open your Inventory (CTRL-I)
  • Right click on My Inventory
  • Select New Folder
  • Rename the new folder to #RLV (be sure to use uppercase letters, exactly as shown here)

Now you should be able to accept inventory from traps and toys, which will automatically be moved into the #RLV folder tree.

Note that the latest Phoenix supports 2.2.0 of the RLV spec.

See also

fs_compiling_firestorm_alexivy_debian_9

$
0
0

Under Construction! This page is very experimental. Don't rely on it unless you want to do a lot of pioneering yourself.

Building Firestorm 5.1 in 64-bit Debian Stretch

There is no official support for compiling or operating self-compiled viewers. There may be unofficial support as listed at the bottom of this page.

These instructions only apply to Firestorm version 5.1 and above. For older versions, please see this page.

This procedure is used for building a 64-bit version of Firestorm 5.1 on 64-bit Debian systems. It was tested and verified on Debian 9.3. This procedure assumes that your system has been properly updated.

This procedure may not work on older versions of Debian, nor has it been tested on any other version of Debian or any other distribution/variant/derivative.

The build process requires at least 4GB RAM with swap, a modern dual-core CPU and 32GB available HDD space. Recommded 8GB or more RAM, quad-core CPU and 32GB available HDD space.

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.

Add Jessie Repo

Firestorm requires version 4.9 or 4.8 of the gcc/g++ compiler. This is not available in Debian 9's default repositories, so we need to add a Jessie repo.

sudo add-apt-repository "deb http://ftp.us.debian.org/debian/ jessie main"
sudo apt update

Install Required Tools

The required tools, some of which may already be installed, are:

bison bzip2 cmake curl doxygen flex g++ gdb m4 (for make) mercurial (for hg) moreutils (for additional build tools pkg-config python python-dev python-pip
sudo apt upgrade # to make sure all installed packages are current
sudo apt install --install-recommends moreutils bison bzip2 cmake curl doxygen flex g++-4.9 gdb m4 mercurial pkg-config python python-pip

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

The build environment need to know to use gcc 4.9:

sudo update-alternatives --remove-all gcc
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.9 49 \
--slave /usr/bin/g++ g++ /usr/bin/g++-4.9 \
--slave /usr/bin/gcov gcov /usr/bin/gcov-4.9
sudo update-alternatives --config gcc

Note that this will “hide” the current gcc from the build environment, so you will want to add it as an alternative, then use the “update-alternatives –config gcc” command to switch versions as needed.

Install Required Libraries

Firestorm 5.1, like the AlexIvy release of the Linden Lab viewer, is built with the USESYSTEMLIBS flag set, so that the libraries are installed on the user's system as needed and not shipped with - or maintained by - the viewer. This means that a large number of development libraries must be installed on the build system.

These libraries may be included with your distribution, and some may already be installed:

libalut-dev libapr1-dev libaprutil1-dev libatk1.0-dev libboostall-dev libcairo2-dev libcollada-dom2.4-dp-dev libcurl4-openssl-dev libdbus-glib-1-dev libfreetype6-dev
libGL.so (libgl1-mesa-dev) LibGLU.so (libglu1-mesa-dev) libgtk2.0-dev libjpeg-dev libjsoncpp-dev libnghttp2-dev } libogg-dev libopenal-dev libpangox-1.0-dev libpng-dev libsdl1.2-dev
libssl-dev libstdc++.so.6 (libstdc++6) liburiparser-dev libvorbis-dev libX11.so (libx11-dev) libxinerama-dev libxml2.so (libxml2-dev) libxmlrpc-epi-dev libXrender.so (libxrender-dev)
sudo apt install --install-recommends libalut-dev libapr1-dev libaprutil1-dev libatk1.0-dev libcairo2-dev \
libcollada-dom2.4-dp-dev libcurl4-openssl-dev libdbus-glib-1-dev libfreetype6-dev libgl1-mesa-dev \
libglu1-mesa-dev libgtk2.0-dev libjpeg-dev libjsoncpp-dev libnghttp2-dev libogg-dev libopenal-dev \
libpangox-1.0-dev libpng-dev libsdl1.2-dev libssl-dev libstdc++6 liburiparser-dev libvorbis-dev libx11-dev \
libxinerama-dev libxml2-dev libxmlrpc-epi-dev libxrender-dev zlib-dev

Install Autobuild

Autobuild is a Linden Lab resource that does all the hard work. Firestorm 5.1 uses a stock, unmodified version of autobuild form Linden Lab, version 1.1 or above.

pip install --upgrade pip
pip install autobuild

This will install autobuild and add a link in the exec path.

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. For this document, I will assume ~/src.

cd ~/src

There are several repositories but the one wea re 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 optionally add a folder name to the end of the hg clone command and it will use that as the destination directory name:

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

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

This can take a bit, it's a rather large download. On a slow network, it may fail, and this script can help mitigate the issue:

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..50000..5000}
do
	echo "Grabbing to change $i"
	hg pull -u -r $i
done
echo "Grabbing to tip"
hg pull -u
cd ~/src

Set up autobuild build variables

Autobuild 1.1 uses a separate file to control compiler options, switches, and the like for different configurations. Ansariel Hiller maintains a Firestorm-specific version of this file and an associated convenience script. You will want to put this near your source code tree. The rest of these instructions will assume you put it in the source tree at the same level as your main source repository, using the default name.

cd ~src
hg clone https://bitbucket.org/Ansariel/fs-build-variables

Preparing to configure and build

Autobuild 1.1 uses a series of environment variables to control the build process. The fs-build-variables reposirory includes a convenience script to set them. You will need to perform this step in any new shell window that you are going to run autobuild in.

cd ~/src/phoenix-firestorm-lgpl
source ../fs-build-variables/convenience Release
export AUTOBUILD_VARIABLES_FILE=~/src/fs-build-variables/variables

Configuring the Viewer

Unlike previous versions of autobuild, version 1.1 requires the address size switch after the command, not before it. If you want a 32-bit build, you must specify that; there is no default any longer.

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

This will set up to compile with all defaults and without non-default 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 -A 64 -c ReleaseFS_open -- --clean -DLL_TESTS:BOOL=FALSE
autobuild configure -A 64 -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 outisde the viewer development itself. And if you use the –clean switch, you will re-download them all.

Compiling the Viewer

autobuild build -A 64 -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 -A 64 -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-x86_64/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-x86_64/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 team (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 team 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
  • No Sounds The viewer will try to use whatever sound service you have running, but might need a little coaxing. Read through the firestorm script inside the program folder, you will find various commended options. Uncommenting one or more may help restore sound.
  • Voice Won't Connect It was observed in testing that voice would not connect unless “No Device” was chosen for the Input device (Preferences ⇒ Sound & Media ⇒ Voice ⇒ Audio Device Settings). This was resolved by replacing Firestorm/lib/libvivoxal.so.1 with a copy from release.
  • Voice Won't Connect pt 2 The current version of the voice files do not function correctly in the Linux viewer, so you will see the red indicator on the Nearby Chat tab, and you may or may not get an error message. This is a known issue and is being addressed. Hopefully we can soon remove this as an issue.

inventory_fs511.png - created


fs_inspect_511.png - created

firestorm_troubleshooting

$
0
0

Troubleshooting and Quick Fixes - Firestorm Viewer

For basic information on how to get help, click here.
This page covers issues and problems which you might encounter with Firestorm; for topics concerning how to use the viewer, you are instead directed to the main Firestorm documentation page.
The topics here are divided into issues which are directly related to the viewer, and those which are really SL issues or bugs.
Should this not be helpful, then please contact support. The best place to get fast help is in one of the in-world groups. Otherwise, you may contact any of our support team. We will do our best to assist you.
If you believe you have found a genuine bug - or have a feature request, then you can file a JIRA.

Introduction

For an introduction to the basics of troubleshooting, please refer to this page.

Tutorials

Phoenix has some video tutorials on YouTube; you may want to visit and bookmark the Phoenix Viewer channel.

Crash/Login Issues

Web Feed, Audio, Video and Voice

Other

General

Lag and Network

Hardware

Operating System / Software

Windows
Mac
linux

Griefing, Scams, Phishing

Other

fs59_edit_features.png - created

fs511_edit_object_mesh.png - created

fs_513_prerelease

$
0
0

**Firestorm 5.1.3 Prerelease**

Changed Wiki Pages

The pages below have been updated to reflect changes since Firestorm 5.0.11. Please do not bookmark them, as they will disappear once 5.1.3 goes to public release.

  • Avatar Menu: Favorite Wearables. A window to hold frequently used items such as HUDs and items for quick attach/detach using double click to add. Creates a protected subfolder of links #Wearable Favorites inside #Firestorm folder. See also Toolbar Buttons.
  • Avatar Menu: Show User Interface. Unchecking hides the user interface. Use Alt+Shift+U to show user interface again. Chiclets and script dialogs will remain visible. Navigation and Favorite bars will be hidden in next update.

Avatar Complexity

  • Avatar Menu - Appearance (Ctrl+O) - Wearing tab: Shows the rendering weight of each worn attachment. Avatar Complexity

Preferences

  • Firestorm - Build 1: Script Editor Font. Allows you to select the name and size of the font used in the LSL script editor.

Other changes and updates

AlexIvy 64bit - Fully merged up to LL's AlexIvy viewer https://community.secondlife.com/blogs/entry/2290-64-bit-viewers-for-all/ for Windows and Mac. As a result of this update, there is no Linux viewer available. The Linux community is working to resolve this and accordingly, there is no way to anticipate when a Linux viewer will be available for testing.

Chromium Embedded Framework (CEF) Dullahan updated Dullahan: 1.1.820 / CEF: 3.3071.1634.g9cc59c8 / Chrome: 59

FMOD Studio 1.10.04

KDU updated to v7.10.4. KDU updates force a texture cache clear on first run. You may wish to do this manually if you have a slow system or network.

Voice Update: Vivox Version 4.9.0002.27586

JIRA

BUG

FIRE-6155 - Previewing an animation to upload while walking/sitting/flying results in the avatar getting stuck in that animation

FIRE-9070 - build window xyz colors not changing for rotate and size

FIRE-12249 - Develop - Render Metadata - Avatar Hitboxes makes eyes disappear

FIRE-13474 - Saving .dae with brackets in filename fails

FIRE-17518 - [CEF] Opening Preferences from the login screen breaks the login page layout.

FIRE-19704 - [Mac] Crash when upload Mesh 50499 - Calculate Weights and Fees (Mac El Capitan) - LLModelgetJointInfluences(LLVector3 const&)

FIRE-21974 - recovered script after crash is empty

FIRE-22175 - [Mac] [BUG-202965] [MAINT-8208] Firestorm crashes when I use a cube as physic when uploading a mesh model

FIRE-22179 - Preprocessor warning when last line in lsl include is a comment: generic lexer warning: Unterminated C++ style comment

FIRE-22214 - Script Editor - Missing Line numbers, Vintage Skin

FIRE-22241 - Copy paste inserting timestamps unexpectedly

FIRE-22268 - Firestorm crashing when deleting items

FIRE-22281 - [BUG-214575] [MAINT-8289] Deleting inventory directory while keeping [Delete] key preesed

FIRE-22288 - [Mac] [BUG-214585] [MAINT-8287] Creating an admin group role is back. While creating a role, in a new group, once you tick the manage ban list you crash.

FIRE-22297 - [Mac and Linux only?] FPS limiter not working (do not move to Support)

FIRE-22330 - Crash when taking photos

FIRE-22346 - [Opensim] Remove Avination from Grid Manager

FIRE-4963 - using animation upload window disables physics wearables

FIRE-5686 - undocked IM window does not stays at his place after relog and undock again

FIRE-16651 - Animation upload/preview breaks eye movement

FIRE-20866 - @stopim returns The other party is not under a @startim restriction when they are

FIRE-21719 - Copy-Paste a Folder doesnt copy the links to the new folder

FIRE-22148 - Group profile icons unload when Group Titles is opened

FIRE-22164 - Black Text against very dark background Firestorm Skin Dark Scheme Experience Edit WIndow.

FIRE-22167 - Show in Main View fail in 2nd Inventory Window

FIRE-22187 - Typo in Prefs - Chat - Visuals

FIRE-8784 - Align tool not working on some prims

FIRE-9561 - Items worn from Marketplace Tab do not show up as worn items

FIRE-21425 - [CEF] Problem with drop-down menus in internal web browser.

FIRE-21579 - [BUG-202634] [MAINT-8023] Missing support for internationalized domain names.

FIRE-22383 - Links in 1st life profile tab disappear after second save

IMPROVEMENT

FIRE-15266 - Toolbar Button for Beacons

FIRE-20959 - Update in-world browser cipher suites

FIRE-22331 - [Opensim] Mesh uploaded with Analyze likely to render invisible

FIRE-22334 - Reset All Settings button misleading

FIRE-4595 - Paste as Link - in system generated folders like outfits

FIRE-16207 - [Starlight CUI] Contact Sets Panel text

FIRE-22116 - Pennys Windlight Presets

FIRE-5974 - Allow SEARCH to include Received Items Folder

FIRE-22354 - Beyond chat range diminish factor slider is confusing

NEW FEATURE

FIRE-19520 - Add per-item render-weight display to Appearance window

FIRE-20809 - HUD Management, Favorite Wearables Folder (protected) and Toolbar Button

FIRE-20818 - Option to adjust font size in script editor

FIRE-21078 - Show Rendering Cost per attachment

FIRE-22115 - Jeans Windlight Presets

fs_compiling_firestorm_alexivy_ubuntu_16

$
0
0

Under Construction! This page is very experimental. Don't rely on it unless you want to do a lot of pioneering yourself.

Building Firestorm 5.1 (AlexIvy) in 64-bit Ubuntu 16.04

There is no official support for compiling or operating self-compiled viewers. There may be unofficial support as listed at the bottom of this page.

These instructions only apply to Firestorm version 5.1 and above. For older versions, please see this page.

This procedure is used for building a 64-bit version of Firestorm 5.1 on 64-bit Ubuntu 16.04 LTS systems. It was tested and verified on Ubuntu 16.04.4. This procedure assumes that your system has been properly updated.

This procedure may not work on older versions of Linux, nor has it been tested on any other current or LTS version of Linux/Ubuntu or any other distribution/variant/derivative.

The build process requires at least 6GB RAM (8GB recommended) with swap, a modern quad-core CPU and at least 24GB available disk space.

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, some of which may already be installed, are:

bison bzip2 cmake curl doxygen flex g++ gdb m4 (for make) mercurial (for hg)
moreutils (for additional build tools pkg-config python python-dev python-pip
sudo apt upgrade # to make sure all installed packages are current
sudo apt install --install-recommends bison bzip2 cmake curl doxygen flex g++-4.9 gdb m4 \
mercurial moreutils pkg-config python python-dev python-pip

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

The build environment needs to know to use gcc 4.9:

sudo update-alternatives --remove-all gcc
sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-4.9 49 \
--slave /usr/bin/g++ g++ /usr/bin/g++-4.9 \
--slave /usr/bin/gcov gcov /usr/bin/gcov-4.9
sudo update-alternatives --config gcc

Note that this will “hide” the current gcc from the build environment, so you will want to add it as an alternative, then use the “update-alternatives –config gcc” command to switch versions as needed.

Install Required Libraries

Firestorm 5.1, like the AlexIvy release of the Linden Lab viewer, is built with the USESYSTEMLIBS flag set, so that the libraries are installed on the user's system as needed and not shipped with - or maintained by - the viewer. This means that a large number of development libraries must be installed on the build system.

These libraries may be included with your distribution, and some may already be installed:

libalut-dev libapr1-dev libaprutil1-dev libatk1.0-dev libboostall-dev libcairo2-dev libcollada-dom2.4-dp-dev libcurl4-openssl-dev libdbus-glib-1-dev
libfreetype6-dev libGL.so (libgl1-mesa-dev) LibGLU.so (libglu1-mesa-dev) libgtk2.0-dev libjpeg-dev libjsoncpp-dev libnghttp2-dev } libogg-dev libopenal-dev libpangox-1.0-dev
libpng-dev libsdl1.2-dev libssl-dev libstdc++.so.6 (libstdc++6) liburiparser-dev libvorbis-dev libX11.so (libx11-dev) libxinerama-dev libxml2.so (libxml2-dev)
libxmlrpc-epi-dev libXrender.so (libxrender-dev) zlib1g-dev
sudo apt install --install-recommends libalut-dev libapr1-dev libaprutil1-dev libatk1.0-dev \
libcairo2-dev libcollada-dom2.4-dp-dev libcurl4-openssl-dev libdbus-glib-1-dev libfreetype6-dev \
libgl1-mesa-dev libglu1-mesa-dev libjpeg-dev libjsoncpp-dev libnghttp2-dev libogg-dev \
libopenal-dev libpangox-1.0-dev libpng-dev libsdl1.2-dev libssl-dev libstdc++6 liburiparser-dev \
libvorbis-dev libx11-dev libxinerama-dev libxml2-dev libxmlrpc-epi-dev libxrender-dev zlib1g-dev

Install Autobuild

Autobuild is a Linden Lab resource that does all the hard work. Firestorm 5.1 uses a stock, unmodified version of autobuild form Linden Lab, version 1.1 or above.

sudo pip install --upgrade pip
sudo pip install autobuild

This will install autobuild and add a link in the exec path.

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. For this document, I will assume ~/src.

cd ~/src

There are several repositories but the one wea re 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 1.1GB initially and around 12.4GB 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 optionally add a folder name to the end of the hg clone command and it will use that as the destination directory name:

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

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

This can take a bit, it's a rather large download. On a slow network, it may fail, and this script can help mitigate the issue:

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..55000..5000}
do
	echo "Grabbing to change $i"
	hg pull -u -r $i
done
echo "Grabbing to tip"
hg pull -u
cd ~/src

Set up autobuild build variables

Autobuild 1.1 uses a separate file to control compiler options, switches, and the like for different configurations. Ansariel Hiller maintains a Firestorm-specific version of this file and an associated convenience script. You will want to put this near your source code tree. The rest of these instructions will assume you put it in the source tree at the same level as your main source repository, using the default name.

cd ~src
hg clone https://bitbucket.org/Ansariel/fs-build-variables

Preparing to configure and build

Autobuild 1.1 uses a series of environment variables to control the build process. The fs-build-variables reposirory includes a convenience script to set them. You will need to perform this step in any new shell window that you are going to run autobuild in.

cd ~/src/phoenix-firestorm-lgpl
source ../fs-build-variables/convenience Release
export AUTOBUILD_VARIABLES_FILE=~/src/fs-build-variables/variables

Configuring the Viewer

Unlike previous versions of autobuild, version 1.1 requires the address size switch after the command, not before it. If you want a 32-bit build, you must specify that; there is no default any longer.

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

This will set up to compile with all defaults and without non-default 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
  • chan will append a string to “Firestorm-”, customizing the viewer name

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

Examples:

autobuild configure -A 64 -c ReleaseFS_open -- --clean -DLL_TESTS:BOOL=FALSE
autobuild configure -A 64 -c ReleaseFS_open -- --clean
autobuild configure -A 64 -c ReleaseFS_open -- --chan="My-Build" # sets the viewer name to "Firestorm-My-Build"

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

Compiling the Viewer

autobuild build -A 64 -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 -A 64 -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-x86_64/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-x86_64/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 team (preferred) or discuss on IRC.

Common Issues/Bugs/Glitches And Solutions

Voice

At present, voice does not work. There are two workarounds:

Windows-based

Download this tarball and extract the contents to your Nightly or Tip's /bin folder. It is in a win32 folder because that's what the viewer is looking for.

Launch the viewer but don't log in. Open the Debug menu (if you don't see it, Preferences > Advanced, enable Show Advanced Menu), and select Show Debug Settings. In there, search for FSLinuxEnableWin32VoiceProxy and set that to TRUE. Close Debug Settings.

Note that you can change FSLinuxEnableWin32VoiceProxy while logged in, but make sure voice is disabled first.

Native

In Release, in its /lib folder, locate “libvivoxoal.so.1” and copy that to your Nightly or Tip's /lib folder.

Make sure you set the FSLinuxEnableWin32VoiceProxy debug setting to FALSE for this workaround.

Openjpeg

Autobuild.xml refers to a newer – and broken – version of openjpeg for 64-bit Linux. The workaround is to modify autobuild.xml as follows:

Locate autobuild in the Firestorm source folder and open it with a text editor. Search for openjpeg-1.5.1.180841553-linux64-180841553.tar.bz2 and replace it with http://downloads.phoenixviewer.com/openjpeg-1.4.201505150222-r26-linux-x64-201505150222-r26.tar.bz2 Just above that line is the hash 6098e555296583336b02f1a78b41b93a, replace that with f8a5ed12a0b45e0c48e04642ee736426 Save the file, then configure with the –clean option.

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 team 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

=== No Sounds === The viewer will try to use whatever sound service you have running, but might need a little coaxing. Read through the firestorm script inside the program folder, you will find various commended options. Uncommenting one or more may help restore sound.

fs59_edit_features.png - created


fs_error_message_list

$
0
0

Error Messages

This is a collection of error messages seen in SL. Some are system messages; some are viewer-generated. The list is by no means complete. If you get an error message that is not on this page, please report it in Firestorm Support English (in-world support group) or File a Jira alerting us to it (please provide the complete, exact wording of the message; a screenshot is also helpful).

Messages Mentioning Animations

Error Remedy
“PERMISSION_TRIGGER_ANIMATION permission not set” This message usually comes from an AO or other scripted item, dropped in world. It can also come from a badly scripted object that doesn't check it has perms before animating, such as a badly written poseball.

Messages Mentioning Attachments, Clothing, Body Parts, or Other Wearables

Error Remedy
“You can't attach multiple objects to one spot” message when detaching from avatar. That will happen if the user somehow has a coalesced object in their current outfit folder. Delete it.
“The outfit folder contains no clothing, body parts, or attachments.” See Empty Outfits

Messages Mentioning Certificates

Error Remedy
“Unable to find a valid certificate” See Second Life: Unable_to_find_a_valid_certificate.

Messages Mentioning Credentials or Passwords

Error Remedy
“We were unable to decode the file storing your saved login credentials” (or) “Failed to decode login credentials” See Failed to Decode Login Credentials

Messages Mentioning Clock or Time

Error Remedy
“Unable to connect to Second Life.
Often this means that your computer's clock is set incorrectly.
Please go to Control Panels and make sure the time and date are set correctly.”
See Second Life: Clock is set incorrectly.

Messages Mentioning Connections or Networks

Error Remedy
“Unable to establish a secure connection to the login server” See Second Life: Unable to establish a secure connection to the login server .
“Second Life has detected corruption in either your network transmissions or the files it's attempting to read on your hard drive. You might also be logging in from an invalid location.” See Second Life: Mangled network data.

Messages Mentioning Regions

Error Remedy
“Unable to create item that has caused problems on this region.” 1) Have the region restarted; this will usually fix it.
2) If a region restart doesn't clear it up, the sim owner may need to ask LL to move the sim to another server channel.
“We are sorry, Linden Lab has discovered degraded performance on your connection to the region you are on. You will need to restart Second Life and log into a new region for the next 30 minutes to an hour. We apologize for the inconvenience.” Delete landmarks, especially favorite landmarks. If they point to an invalid location, it can cause this message.
This may also mean exactly what it says; follow the instructions.

Messages Mentioning SLVoice, SLPlugin, or LLCefLib

Error Remedy
“Do you want the application 'SLVoice' to accept incoming network connections?” Mac – This is a message from your computer's firewall. You should choose “Allow” for voice to work.

Messages Mentioning Teleports

Error Remedy
Sorry, you do not have access to that teleport destination.

Messages Mentioning Textures

Error Remedy
“# of textures discarded” message usually followed by a crash See Textures Discarded.

Messages Mentioning Video Cards, Drivers, or Hardware

Error Remedy
“Firestorm is unable to run because your video card drivers did not install properly or are out of date, or are for unsupported hardware. Please make sure you have the latest video card drivers, and even if you do have the latest, try reinstalling them. If you continue to receive this message, contact the Second Life Support Portal” See Intel Fix 32-Bit

Unclassified Messages

Error Remedy
“Index out of range: 34 not in [ 0, 11]” From the login screen, open the Debug Menu - Show Debug Settings - RenderDebugGL. Set to FALSE. Relaunch the viewer and login.
“newview/llappviewer.cpp(1838): Unhandled exception caught in bool”
_cded LLAppViewer::frame(void): No diagnostic information available
If the error happens in only one region, clear cache
“Must supply a comment for control content” The installation is corrupt. Uninstall Firestorm, delete the installer, clear your web browser's cache (or use a different browser) and download a fresh installer from http://www.firestormviewer.org/downloads/ and install that.

start

$
0
0

Firestorm Documentation

Downloads

Getting Help

Support

Classes

Firestorm User Guide

Basic Functions

Advanced Topics

Tutorials and Other Info

Firestorm Tutorial Videos

Firestorm Colour Scheme Tutorial

For Developers

Gateway Gateway Events

Other

Contact and Policies

motd

$
0
0

Firestorm Message of the Day.

If you're looking for how to get your own event in the Firestorm Message of the Day, click here.
If you're looking for a missed MotD or more information on the current MotD rotation, keep reading!

I missed it! Make it come back!

Oh hi! I didn't see you come in! You're probably here because you missed the message of the day. It went by to fast, it was to long, or you clicked a link in a goofy motd set up to get you here!

Anyway, if you missed the message of the day and would like to see it again;
At the top of your screen find the “Content” menu and click it.
In the menu that drops down, way down at the bottom select, “Message of the Day”.

There it is, in your local chat as a system message.

[11:28:02] [Firestorm Tip! Did you know you ca… Stop… Wait… Go back… I didn't get to read it all! Grrrr! Clickies! http://wiki.phoenixviewer.com/motd]


You can also scroll down this page and see ALL the current messages of the day in the “events, tips, help and gateway” message of the day rotation. (I keep this page bookmarked as a fast reference to important wiki pages.)


About the Message of the Day.

The Firestorm Message of the Day is currently running on a rotation of thirty eight preset tips, help, gateway and fun messages and/or a varying amount of event messages of the day. All of which are displayed at random when you log in depending on which “MotD Cartridge” is loaded. Go ahead, try it, relog, and unless the message of the day is promoting a special event1) you'll see something different.

The preset messages of the day are split between tips to make your Firestorm Viewer experience more efficient and enjoyable, help topics to help resolve common Firestorm Viewer issues, gateway to spread information about the Firestorm Gateway and fun just because.

I'll list the message of the day presets below so you can see what's in the rotation.


Event Messages of the Day.

These are the current messages of the day for events which are currently running and have been approved for a Firestorm message of the day;

MOTD: EVENT: 2018 SciFi Expo Registration
The SciFi Expo in support of The American Cancer Society's RFL of SL is now accepting applications for their event running May 12 to 20! Click to sign up! https://slscifiexpo.wordpress.com

MOTD: EVENT: 2018 Rock Your Rack Registration
Rock Your Rack 2018 supporting the National Breast Cancer Foundation is now taking designer registrations for their October event! Click for more! https://rockyourrack.wordpress.com/about/designers/


Preset Messages of the Day.

These are displayed randomly and are broken down into three groups;

Tips: Which provide tips on how to get the most out of the Firestorm Viewer and are meant to improve your Second Life experience in some way.

Help: Which provide assistance on self resolving common Firestorm problems which are seen the most in the Firestorm Viewer help groups. These may have also been requested by the Firestorm Support Team at some point.

Gateway: Coming soon! These provide information on what's going on at the Firestorm Gateway, events, event spaces, classes and more.

I'll break them into the same groups below;


Firestorm Message of the Day, Firestorm Tips!

MOTD: TIP: Firestorm Classes 1Temporarily removed from the rotation.
Did you know Firestorm has classes on how to use the Firestorm viewer? We even have an open question and answer session after each class! http://wiki.phoenixviewer.com/firestorm_classes

MOTD: TIP: Firestorm Classes 2Temporarily removed from the rotation.
Did you know Firestorm offers classes on how to get the most out of the Firestorm viewer? Click to find out more about these classes and when they are! http://wiki.phoenixviewer.com/firestorm_classes

MOTD: TIP: Avatar Complexity
Firestorm tip! Why is my friend a colored shape? What is this complexity popup thingy? Click here to find out more about this lag reducing feature! http://wiki.phoenixviewer.com/fs_avatar_complexity_settings

MOTD: TIP: Complexity and the Slideshow
Firestorm tip! Are you at a busy club or event and Firestorm is running like a slide show? Try lowering your avatar complexity setting! http://wiki.phoenixviewer.com/fs_avatar_complexity_settings

MOTD: TIP: FS Bridge, Trolls Not Included
Firestorm Tip! The Firestorm BRIDGE is enhancing your SL experience and you may not even know it! Click here to find out how! http://wiki.phoenixviewer.com/fs_bridge

MOTD: TIP: Can Not Log in to SL
Firestorm Tip! Can't log into Second Life? STOP! DO NOT reinstall firestorm! Save yourself a lot of trouble and check here first for possible grid issues https://status.secondlifegrid.net/

MOTD: TIP: Contact Sets
Firestorm Tip! Contact Sets allow you to organize friends and non friends into manageable groups and categories! Learn more about them at http://wiki.phoenixviewer.com/fs_contact_sets

MOTD: TIP: IM Tab Sorting
Firestorm tip! Did you know you can click and drag your IM tabs in the conversations window to sort them to your liking. For more chat tricks see http://wiki.phoenixviewer.com/fs_chat

MOTD: TIP: Customizable Quickprefs
Firestorm tip! Did you know you can add your most commonly used settings to the Quick Prefs? http://wiki.phoenixviewer.com/fs_quick_preferences

MOTD: TIP: Missed the MotD
Firestorm Tip! Did you know you ca… Stop… Wait… Go back… I didn't get to read it all! Grrrr! Clickies! http://wiki.phoenixviewer.com/motd

MOTD: TIP: Outfits
Firestorm tip! Did you know the Outfits feature can help you quickly change what you&apos;re wearing without digging around in your inventory? http://wiki.phoenixviewer.com/my_outfits_tab

MOTD: TIP: Camera Controls
Firestorm tip! Something catching your eye? Hold down your ALT key and click it, then roll your mouse wheel! Interested in more? See http://wiki.phoenixviewer.com/fs_movement_and_camera#view

MOTD: TIP: Toolbars
Firestorm tip! Did you know you can add many of your commonly used Firestorm windows and floaters to the toolbars? http://wiki.phoenixviewer.com/toybox

MOTD: TIP: SL World Search
Firestorm tip! Looking for something in world but, can't find it? Try a search! http://wiki.phoenixviewer.com/floater_search

MOTD: TIP: Replace Links
Firestorm tip! Gah my inventory links are borkened! Have no fear, Replace Links are here! Fix those broken links, http://wiki.phoenixviewer.com/fs_linkreplace

MOTD: TIP: Skins
Firestorm tip! Wanna change the way firestorm looks? Then change it! http://wiki.phoenixviewer.com/preferences_skins_tab

MOTD: TIP: Settings Backup
Firestorm tip! Better safe than… NOOOOOOO! You should regularly back up your Firestorm settings. You never know when…. http://wiki.phoenixviewer.com/backup_settings

MOTD: TIP: Auto Replace
Firestrom tip! Firestone? Firestorm! If only Firestorm had an auto replace… Oh wait! It does! http://wiki.phoenixviewer.com/fs_auto_correct

MOTD: TIP: Preference Search
Firestorm tip! Is a Firestorm setting playing hide and seek and causing you to pull out your hair? Find it fast with preference search! http://wiki.phoenixviewer.com/fs_preferences

MOTD: TIP: Chat Shortcuts
Firestorm tip! Did you know when chatting you can hold down your ctrl key when you press enter to shout and the shift key to whisper? http://wiki.phoenixviewer.com/keyboard_shortcuts

MOTD: TIP: Keyword Alerts
Firestorm tip! Did you miss a message in chat? Did someone say your name while you were doing something else? Check out Keyword Alerts! http://wiki.phoenixviewer.com/preferences_chat_tab#keyword_alerts_tab

MOTD: TIP: FS Wiki
Firestorm Tip! Did you know Firestorm has its own wiki? Find out how features work, how to fix common viewer issues and more! Check it out, bookmark it, study it! http://wiki.phoenixviewer.com/

MOTD: TIP: Inventory Count
Firestorm Tip! Do you have more inventory than you thought you had? Inventory count now includes folders! Click for more http://wiki.phoenixviewer.com/my_inventory_tab

MOTD: TIP: Elements
Firestorm Tip! Elements? What is this, chemistry class? No silly, Elements is the count of Items/Folders in that folder! Click for more http://wiki.phoenixviewer.com/my_inventory_tab


Firestorm Message of the Day, Firestorm Help!

MOTD: HELP: Bakefail Badness
Firestorm Help! Are you feeling overly misty as an orange cloud? Are you missing your avatar? Are you thinking, clouds belong in the sky, not on me! Click here to fix the cloud http://wiki.phoenixviewer.com/fs_bake_fail

MOTD: HELP: Camera Messed Up
Firestorm Help! HALP! I know my head looks awesome but I'm stuck staring down at the top of it! Why am I staring at my butt? What is wrong with my camera?! click click clickie! http://wiki.phoenixviewer.com/fs_camera

MOTD: HELP: Teleporting Woes
Firestorm Help! What is up with these teleport fails? Disconnected?! OMG again! Click here to help prevent TP issues! http://wiki.phoenixviewer.com/fs_tp_fail

MOTD: HELP: Slow Rezzing
Firestorm Help! Did you know many common rezzing problems can be solved by you? Clickies! http://wiki.phoenixviewer.com/slow_rez

MOTD: HELP: Slow Rezzing Mesh
Firestorm Help! Did you know many common mesh rezzing problems can be solved by you? Clickies! http://wiki.phoenixviewer.com/mesh_issues

MOTD: HELP: Getting Help NAO
Firestorm Help! HALP! My Firestorm is broken and I need help NAO! Have no fear, click here! http://wiki.phoenixviewer.com/getting_help

MOTD: HELP: Getting Help Dont Panic
Firestorm Help! Sudden viewer problems? Not sure what to do? Don't panic! check out our wiki: http://wiki.phoenixviewer.com/getting_help

MOTD: HELP: Voice Issues
Firestorm Help! Have you lost your voice? Firestorm voice not working for you? Why not drink a tall glass of http://wiki.phoenixviewer.com/fs_voice

MOTD: HELP: Rick and Morty Lost Login Info
Oh geez, Rick, Firestorm lost my login info again! Well, Morty, try starting here to fix it, http://wiki.phoenixviewer.com/fs_stored_passwords#failed_to_decode_login_credentials

MOTD: HELP: Help Help Help You
Firestorm Help! Need help? Help us help you! Learn how to use the Firestorm support group to get the best help! http://www.firestormviewer.org/firestorm-help-groups-tips-rules-and-guidelines/

MOTD: HELP: Second Life Account Questions
Firestorm Help! Need help with your Second Life account matters? Go to Avatar Menu - Account, or login to your Dashboard at https://secondlife.com/my/account/

MOTD: HELP: Dont Clear Your Cache
Firestorm Help! Having viewer problems? Please don't clear your cache or reinstall the viewer as the first thing you try. Instead, see this page for how to get help http://wiki.phoenixviewer.com/getting_help

MOTD: HELP: Missing Inventory
Firestorm Help! Ummmm, I know I had more things in my inventory than this! Help! I'm missing inventory! what can I do? http://wiki.phoenixviewer.com/fs_missing_inventory


Firestorm Message of the Day, Firestorm Gateway! Coming soon!

MOTD: GATEWAY:
Keep an eye here for upcoming information regarding the Firestorm Gateway!


Firestorm Message of the Day, Firestorm Fun!

MOTD: FUN: Rhubarb Pie
Firestorm fun! Feeling hungry? try a Rhubarb Pie, Firestorm style! http://wiki.phoenixviewer.com/rhubarb_pie


Notes

This section is changing as we speak!

* if a main MOTD is set, that one is always shown
* if random MOTDs are set and no main MOTD is set, they will be randomly shown at login and during TP
* if an event MOTD is set, that is always shown at login and then, during TP either the main MOTD or one of the random MOTDs

1)
A 1 - 7 in the MotD priority list.

preferences_chat_tab - fixed incorrect ref to enabling nearby chat logging

$
0
0

Preferences - Chat

Visuals Tab

  • Onscreen console font size: Choose Small, Medium, Large or Huge
  • Play avatar animations (such as shouting): Animates your avatar for some standard actions.
  • Wrap system chat messages in brackets: makes system messages distinct by enclosing them in brackets.
  • Show “You” in chat transcripts instead of your name: Replace your name in transcripts.
  • Emotes use italic font: Makes emotes show in italics.
  • Bold Shouting, Italicize whispering: If enabled, emphasises shouting and whispering, as the option indicates.
  • Mark objects with (no name) when they speak to avoid spoofing: This allows object names in chat to be clicked, so that you can get information about them (creator, owner, etc). Useful in griefing situations.
  • Route llOwnerSay to script debug window:llOwnerSay script output is sent to the script debug window rather than being shown in console, on screen.
  • Show chat in bubbles above avatars: puts local chat in bubbles above users heads.
    • Don't show chat in Nearby Chat console and toasts: Prevents chat from showing in console and toasts (only available if the above option is enabled; greyed out otherwise).
  • Show typing indicator in bubbles above avatars: This will show something like a chat bubble but only when another avatar is typing; it gives a visual indication that someone is typing. The text itself will appear according to your settings.
  • Show typing indicator in nametag above avatars: Similar to the above, but the indicator appears in the nametag instead.
  • Show seconds in timestamps: adds seconds to the timestamps.
  • Show timestamps in: You can select whether to show timestamps in…
    • Nearby chat
    • IMs
    • Transcript
  • Use classic draw mode for console: Changes the chat console 1) background to surround all visible text instead of displaying separate backgrounds per line of chat.
  • Use full screen width for console: Will allow the chat to be the full width of the screen (requires restart).
  • Fade chat after _seconds __ # lines: Allows you to choose how long, and how many lines show in the chat console.

Chat Windows Tab

  • Chat window font size: Choose Small, Medium, Large or Huge
  • Show names in direct IMs: If this is disabled, user names are not shown on each line in IMs.
  • Use V1 style chat headers: Makes chat look like V1 style chat. With this unchecked, chat headers will appear as horizontal bars across chat windows, with text underneath. With it checked, timestamp and name will precede text on the same line.
  • When using V3 style chat headers, show mini icons: shows the icon in the IM/group chat next to the name. If Remove chat headers is enabled this will not show even if enabled.
  • Show the end of the last conversation: If enabled, the last few lines of the last conversation will be shown in IM windows. This requires that chat transcripts be enabled in Preferences→ Privacy → Logs & Transcripts.
  • Add additional chevron (>) as typing indicator to IM sessions: This depends on the other person having enabled Send typing notifications to other avatars during IM sessions. If they have, then you will see a chevron when they are typing.
  • Show new message notification for: If you have scrolled up in a chat window, and a new message has arrived, you can be informed of this, by enabling one or both of:
    • Nearby chat
    • Instant and group messages.
  • Show IMs in: (requires restart)
    • Separate windows
    • Tabs
  • Chat tab orientation: (requires restart)
    • Horizontal (along the bottom of the Conversations window)
    • Vertical (down the left side of the Conversations window)
  • Name format for IM tabs: If you have both display names and user names enabled in Preferences -> General, then you can select what names you want display in IM chat tabs:
    • Display name
    • Username
    • Display Name (Username)
    • Username (Display Name).
  • Enable group moderator message highlighting: This option will make text posted by group moderators stand out in group chat, so you can easily tell which poster has moderator rights. Two options may be combined (you may enable either one, or both):
    • Name Style: You can opt to have moderator names highlighted in one of several text styles, such as bold, italic, etc.
    • Text Style: You can also specify a style for the etxt that apepars in chat after the moderator name.
  • Disable ALL group chats: Prevents group chats from opening automatically when another user IMs the group.
    Note: The viewer will still receive group chat with this option turned on when an IM/Group Chat tab is open for the group in the Conversations window. What the option does is prevent the automatic creation of a tab when a group message is received.
  • When “receive group notices” is disabled, disable group chat as well: Turns off group chat from any group from which you are not receiving group notices.
    Note: Group text chat may now be disabled independantly of group notices, in the groups profile window.
    Note: The viewer will receive group chat with this option turned on when an IM/Group Chat tab is open for the group in the Conversations window. What the option does is prevent the automatic creation of a tab when a group message is received.
  • Automatically ignore and leave all conference (ad-hoc) chats: Shuts down any conference chats in which you are included.
    • Report ignored conference chats in nearby chat: Informs you that a conference chat was ignored.
      The name of the person is shown, and may be clicked in nearby chat to bring up their profile.
    • Don't ignore conference chats invitations from my friends: overrides the automatically ignore settings for conferences started by those on your friends list.
  • Group Chat Snooze Duration: Length of time a group chat will be muted when clicking the Snooze button. Setting this to zero will simply close the group window until the next group message arrives.
    Note that any chat which occurs during the “snooze” period will not be logged - should you have logging enabled.
  • Set group chat snooze duration individually per group: If enabled, when you snooze a group chat, a window will open asking how long to snooze the chat for.

Typing Tab

  • Auto-Replace: Opens the Auto-Replace Settings window where you can define word replacement. Useful as an auto correct feature, for example.
  • Spell Checking: Opens the Spell Checker Settings window.
  • Translation (button): Opens the Chat Translation Settings window, where you can specify if you want chat to be translated, and which service to use.
  • Play typing animation when chatting: Your avatar will play the typing animation when chatting in local with this enabled.
    • Play typing animation also when emoting: If the above is enabled, then this option will have your avatar play a typing animation when using emotes.
  • Hear typing sound when people type in local chat: If enabled, you will hear the sound of typing
  • Send typing notifications to other avatars during IM sessions: If enabled, this will show “xxx is typing” in IMs. It can also trigger the other person's IM to open before you actually send the IM text. (See Announce incoming IMs as soon as the sender starts typing below.)
  • Enable auto-completion of gestures in nearby chat bar: If this is enabled, then typed gestures will auto-complete as typed.
  • Enable automatic name prediction in nearby chat bar: When this is enabled, the viewer will attempt to autocomplete a name based on the names of those near you.
  • ”:” as a synonym for ”/me”: Used in Role Playing. Allows use of ”:” instead of ”/me” to indicate an action, instead of a statement. For example; ”:nods in agreement” appears as “John Doe nods in agreement”. (NOTE: No space after the ':'.)
  • Auto-close ((OOC)) parentheses: Used in Role Playing. When entering message in RP mode, it is assumed they are speaking as their character. To communicate something outside of their character, they enclose their message with “((” and “)) ”.
    When checked, the viewer automatically appends a ”))” to a message if it isn't present. For Example ((This is OOC“ results in ”((This is OOC)) “.
  • Show send chat button in the chat bar for IM sessions: Adds a “Send” button at the right end of the chat bar in IM and group chat windows.
  • Add a chatbar in the Nearby Chat window: As the name implies.
    • Show channel selection in chat bar: Enables the channel selector in the nearby chat bar.
    • Show chat type / send chat button in chat bar: Adds a button to the right of the nearby chat bar; you can click this to send chat, and you can select whether to say, whisper or shout.
  • Autohide Main chatbar: If this is enabled, then the chat bar at the bottom if the screen will close after you have typed something. Starting to type anything again will cause it to reopen.
    Note that if both the WASD selection in Pressing Letter Keys (above) and Autohide are enabled, you will need to hit Enter/Return before you begin typing in an autohidden chat bar.
  • Deselect Chat after sending Messages: Will move the cursor out of the chatbar after you send a message.
    • De-focus chat history as well: Will also remove focus from the nearby chat history window.

Use Keyboard Shortcuts

Here, you can enable/disable three special shortcuts:

  • Ctrl-Enter - Shout
  • Shift-Enter - Whisper
  • Alt-Enter - OOC

Notices Tab

  • Enable incoming chat popups: Allows Group and/or IM chats to appear onscreen, in either console or toasts, whichever is set below.
    • Group Chats
    • IM Chats
  • Use console for chat popups instead of floating toasts (Viewer 1.x style): Displays chat in the onscreen left-hand console rather than in bottom-right toasts
    • Show IMs in chat console: Will show IMs in the chat console; this is on the lower left of the screen, not in the communication window.
    • Show group chat in chat console: Will show group chat in the chat console; as noted above, this is on the screen, not in the communication window.
    • Length of group name to be printed in chat transcripts:
      • Setting '0' turns it off.
      • Setting '-1' shows the full group name.
      • Setting '1 or higher' shows the group name truncated to how ever many characters are set here, the '[' and ']' aren't counted.
  • Open Conversations when an offline mesage has been received: Normally, any offline messages you get will be shown as chiclets when you log in. If you enable this, the Conversations window will also open to show the text of the messages.
  • Email me IMs when I'm offline: will send any offline IMs to your email that you have on file with LL
  • Show IMs in nearby chat window: Shows the text of received IMs in the nearby chat window.
    • Save IMs in nearby chat: Enable logging of IMs along with local chat; requires that local chat be logged, which can be enabled in the Privacy -> Logs & Transcripts tab.
    • Fade IM text into the background of the chat transcript window: 0.25 for most faded, 1 for no fade.
  • Show number of unread IMs in Firestorm's window title: Displays a count of unread messages in the window title bar.
  • Announce incoming IMs as soon as the sender starts typing: If enabled, your IM window will open and beep as soon as someone starts typing a message to you, rather than after they complete and send the message.
    Note that this will not work if the person IMing you has disabled Send typing notifications to other avatars (above).
  • Flash IM tabs when friends come online or go offline: visually notifies you when friends log in or out; most useful during IM conversations.
  • Flash chat toolbar button if new nearby chat arrives: The nearby chat window must be docked to the conversations window, and this must be closed for the button to flash.
  • Flash chat toolbar button if new IM arrives: The IM window must be docked to the conversations window, and this must be closed for the button to flash. also, this option is only available if IMs are shown in tabs, rather than separate windows; see the setting in PreferencesChat -> Chat Windows.
  • Report muted group chat in nearby chat: If chat starts in a group which you have “muted”, a message to that effect will be displayed in nearby chat.
    Group chat can be “muted” (disabled) in the groups profile window.
  • Show group notices in group chats, in addition to toasts: If enabled, the text of group notices is displayed in the group chat window.
    • Show their subjects and authors as well: Also shows the title and sender of notices in group chat.

Radar Tab

  • Radar reports when avatars enter/leave chat range: Will show in nearby chat when an avatar enters or leaves chat range.
  • Radar reports when avatars enter/leave draw distance: Will show in nearby chat when an avatar enters or leaves your draw distance.
  • Radar reports when avatars enter/leave the region: Will show in nearby chat when an avatar enters or leaves the region.

Each of the above can, optionally, play an alert sound, which you can change by specifying your own sound clip UUID. You an hear the sound by clicking the button labelled 'P', or revert the sound to the default by clicking the 'D'.

Note that the names shown by radar, in the nearby chat window, can be clicked to open a profile.

  • Report enter/exit alters to scripts: This is the same function that is available from the People panel gear menu. It will output radar information to user scripts. For more information, refer to this page.
  • Enhance radar with LSL-Client Bridge: If this is enabled, radar functions responsible for determining avatar locations at high altitudes are assisted by the LSL bridge, particularly when they are beyond draw distance.
  • Age Alert: You can also be alerted to avatars who are “younger” than a certain number of days.
    • Threshold: Set the age in days.
    • Radar reports avatars younger than the specified age: Enable to be alerted.
      again, you can specify your own alert sound by giving a valid sound UUID.

Keyword Alerts Tab

  • Enable Keyword Alerts: Enables using Keyword Alerts.
  • Look for Keywords in Local Chat: When checked, the alert system monitors Local Chat for the presence of these keywords.
  • Look for Keywords in IMs and Group Chat: When checked, the alert system monitors the IM and Group Chat areas for presence of these keywords.
  • Check sender's name for keywords: Look for keywords in the names of speakers or objects as well.
  • All keywords are case-sensitive: Enable this if you want (for example) Apple to be treated differently from apple.
  • Only match whole words: Enabling this will prevent an alert from being generated on partial matches. For example, if you have an alert on the word frank, you will not be alerted if someone types frankly.

Note: Because Group Chats are prevented from appearing when either When Receive Group Notices is disabled, Disable Group Chat As Well or Disable All Group Chats are enabled (see above), no alerts are triggered.

  • Keywords (separated by commas): Specifies the list of words that will trigger an alert. They can be individual words or phrases and are separated by commas.
  • Enable Color Alert: When checked, any messages that are to be alerted will have their color changed to what is specified in the color selector.
  • Play alert sound: Enables playing a sound, identified by the UUID:
  • Alert Sound UUID: Supply the alert sound UUID here. A default is given. To get a new UUID, find a sound in your inventory with full permissions (you can view the item's properties to check this), then right-click the sound and select Copy Asset UUID from the menu. Then paste the value into the text box.

CmdLine Tab

See this page for a tutorial video.

  • Enable usage of chat bar as a command line: If this is enabled, all the commands given below (except where noted) will be available for use.

All of the commands below can be changed from the supplied defaults.

  • Calc. expressions (calc): Used to perform a calculation on the command line to figure out an answer quickly. Calculations adhere to precedence rules where multiplication/division occur before addition/subtraction. Therefore, example: “calc 1.3+2*5” results in “11.3” as the answer, because the multiply occurs before the addition.
  • Change Draw Distance (dd): Changes the draw distance of the rendered view to the specified number of meters. Example: “dd 32” sets the draw distance to 32 meters.
  • Max. Bandwidth (bw): Change your current maximum bandwidth. This is set in PreferencesNetwork & Files -> Connection.
  • Copy camera position to clipboard (cpcampos): Saves the current camea position in the clipboard, from which it can be pasted into a script, for example.
  • Turn AO on/off (cao): Turns the embedded AO system on/off. Example: “cao on” turns AO on, and “cao off” turns AO off.
  • Clear the chat transcript (clrchat): Clears the chat history from local chat. Example “clrchat”
  • Set the media url (/media): Sets the video media for the parcel as identified by the URL. Only the land owner can set the media URL. If the URL contains a space, use to identify the space. The type is one of: Audio, Image, Movie or Web.
  • Set the music stream url (/music): Sets the music stream for the parcel as identified by the URL. Only the land owner can set the music URL. Example: “/music http://scfire-dtc-aa04.stream.aol.com:80/stream/1010” sets a Smooth Jazz sound to the URL.
  • Rez a platform (rezplat): Assuming the avatar has build privileges in the simulator, this command rezzes a circular platform of the given diameter beneath the avatar. Example: “rezplat 25” rezzes a 25m diameter platform below the avatar.
  • Get avatar name from key (key2name): Looks up the specified avatar key and returns the name for the key. Example: “key2name” returns “Babbage Linden”.
  • Roll dice (rolld): For role play. Use by typing rolld <number of dice> <number of faces> in nearby chat. Examples:
    rolld is a regular dice with 6 faces.
    rolld 1 20 is a single dice with 20 faces.
    rolld 3 10 is 3 dice, each with 10 faces.
    Bonuses, penalties, successes and explosions modifiers can also be added to the command; for more, refer to this page.
  • Teleport within sim (gtp): Teleport to anywhere within the sim instantly according to the position specified. Example: “gtp 45 150 400” teleports to 45, 150, 400.
  • Teleport to ground (flr): Teleport to the current ground position for the avatar's current position.
  • Teleport to altitude (gth): Teleport to the specified height. Example: “gth 2800” teleports to a height of 2800 meters. It is also possible to teleport higher. Example: “gth 6500” teleports to 6500m above the sim.
  • Teleport to cam position (tp2cam): Teleports the avatar to the position the cursor is currently looking at. This is useful when walking into a store. After looking around and finding the item to purchase, this shortcut takes you to the position immediately, without having to walk. Example: “tp2cam”.
  • Offer teleport to avatar (offertp): Sends a teleport request to the avatar identified by the given key. Example: “offertp avatar-key”.
  • Teleport to avatar (tp2): Finds a given avatar within the simulator and teleports to them. Example: “tp2 John Doe” teleports to “John Doe” if they are in the simulator.
  • Teleport home (tph): Teleport home. Same as hitting Shift-Ctrl-H.
  • Teleport to sim x (mapto): Teleports to the sim you specified (defaults 128, 128, 0 if no landing point is specified on the sim). Must use the full sim name, with spaces and all.
    • Use same position between sims: When enabled, your entry point at the new sim will be the same coordinates you left the old sim, unless a landing point is specified in the new sim.

There are a few other commands which are not shown here (and therefore cannot be changed). These include:

  • /zoffset_up: Offset your avatar upward by 0.05.
  • /zoffset_down: Offset your avatar downward by 0.05.
    These can be used in gestures, perhaps assigned to the PgUp and PgDn keys respectively.
  • zdrop, ztake, mtake: Refer to this page.



See this page for documentation on Firestorm 5.0.7 (52912) and earlier.

1)
“Console” here refers to the lower left area of your screen, where chat (and optionally IMs) can be displayed.

mac_os_x_10.11_el_capitan - mac_el_capitan renamed to mac_os_x_10.11_el_capitan (Adding OS #)

$
0
0

Mac El Capitan (10.11) Issues

Nvidia Driver Crash

General Info

There is no real fix for this crash (the fix will need to come from Apple); however, switching over to using the Nvidia web drivers will stop the crashes. There is a chance of the viewer running with poorer performance.

(This crash has continued on Sierra.)

This problem affects other games, too; for example, see constant crashes - OS X 10.11 El Capitan and OSX El Capitan 10.11 Beta (15A21). The same workaround appears to fix the problem in other games also; that is, to switch over to using the Nvidia web drivers instead of the Nvidia driver that Apple provides.

Please note that this is not a viewer-specific crash. Refer to this Firestorm Jira: [BUG-10302] [Mac El Capitan] Firestorm crash/incompatibility with Mac OS 10.11 and this SL Jira: BUG-10302 Frequent Crashes in Mac OS X 10.11 El Capitan.

To install and use Nvidia web drivers

Missing Characters

If some characters now display as boxes, you can edit the fonts.xml file within Firestorm to cause the characters to load properly.

  • Log out of Firestorm.
  • In a Finder window, go to your Applications folder.
  • Right click on your Firestorm application and choose “Show Package Contents.”
  • Navigate to Contents/Resources/fonts/fonts.xml.
  • Open fonts.xml with Text Edit.
  • From there, scroll down to the section where it shows hiragana.
  • After the line <os name=“Mac”>, insert this line:
    <file>ヒラギノ角ゴシック W3.ttc</file>
    so that the page looks like this:
<os name="Mac">
<file>ヒラギノ角ゴシック W3.ttc</file> ///(only insert this line and leave everything else as is.)///
<file>ヒラギノ角ゴ Pro W3.otf</file>
<file>ヒラギノ角ゴ ProN W3.otf</file>
<file>AppleSDGothicNeo-Regular.otf</file>
<file>AppleGothic.dfont</file>
<file>AppleGothic.ttf</file>
<file>华文细黑.ttf</file>
</os>
  • Be sure to save and exit.
  • Open Firestorm and toggle to your Japanese keyboard or type in Japanese. It should now work as expected.

NOTE: This is only necessary for Firestorm versions 4.7.3 and older.

Viewing all 5258 articles
Browse latest View live


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