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

fs_script_recovery - added some specifics on cleanup

$
0
0

Script Recovery

How many times have you crashed while editing a script, and lost unsaved changes? If it has happened even once, then you will love this. And it is fully automated, no settings, no fuss.

Open scripts are auto-saved locally every 60 seconds. In event of a viewer crash, scripts are presented to you at login, and you may optionally select one or more to recover; they will be placed in the Lost and Found folder of your inventory.

Backups are only saved if the script has been modified. Backups are removed when a script is successfully saved back to inventory, or the script window is closed.

Removing unwanted backups

Occasionally you may find that backups get stuck for some reason. The following dialogue will appear, and frequently it will appear for all alts (as the viewer doesn't know who “owned” the script)

The first solution is to “restore” and then simply expunge the unwanted ones from your lost+found however if this does not work and the dialogue continues to appear afterwards then manually removing the backups (possibly as an admin) is required.

The files are stored in the temporary file directory for your operating system and are named with an extension *.lslbackup

On Windows: The GetTempPath function checks for the existence of environment variables in the following order and uses the first path found: The path specified by the TMP environment variable. The path specified by the TEMP environment variable. The path specified by the USERPROFILE environment variable. The Windows directory. The simplest way to check/verify is by examining the environment variables

On both Mac and Linux: FS uses the TMPDIR environment variable

char *env = getenv("TMPDIR");

removing all files matching '*.lslbackup' in the above directories will stop any further nagging.


preferences_firestorm_tab_new

$
0
0

Preferences - Firestorm

Extras Tab

  • Allow Remote Scripted Viewer Controls (aka RLVa or RestrainedLove API): Enables RLVa (Requires restart).
    Documentation on RLV is available here and here.
  • Always rez objects under the land group if possible: Many regions are set to only let objects be rezzed by group. When creating an object, the viewer will attempt to set the group of the object if the avatar is in the same group as set for the land.
  • Create particle effects when scripts communicate: If this is enabled, when a script “chats”, the object containing the script will appear to generate swirling particles. Disable this option to turn that effect off.
  • Deactivate tracking beacon when reaching the targetted avatar (⇐ 3m): Normally, a tracking becon (such as one set via map will vanish once get get within 3m of it; with this disabled, the beacon will remain visible until clicked.
  • Disable Login Progress Screens: Disables the black login progress screen.
  • Disable Logout Progress Screens: Disables the black logout progress screen.
  • Enable progressive draw distance stepping: Enables PDD; the slider allows you to adjust the time in seconds between each draw distance increment.
  • Enable LSL-Client Bridge: Enables the Firestorm bridge. See this page for more on what the bridge is and what it does.
  • Flight Assist drop-down: The bridge can offer flight assist functionality, if this is enabled. Note that you should not wear any other scripted flight assist if you turn this on, as they will conflict. (Requires the bridge to be enabled.)
    Flight speed can be boosted; you can select by how much.
    Note that the SL flight height limit is now 5000m; below this, a flight assist is not required.

Protection Tab

  • Block left-click sitting on objects: Some objects are set such that a left click will result in sitting on them rather than touching; enable this if you want to avoid accidentally sitting on such objects. But note that this will prevent all left-click sitting; you will need to explicitly right click and select sit from the menu.
  • Allow scripts to show map UI (llMapDestination): Certain teleport systems open the map for teleporting when clicked. Enable this if you wish to allow this feature.
    If you find the world map unexpectedly opening for you at some locations, and re-opening if you shut it, disable this setting temporarily, until you leave that location.
  • Revoke Permissions: Removes an object's permission to animate or control your input. If this is not done, the object retains permission to animate your avatar indefinitely1):
    • Never (original behaviour): Objects will retain permission to always animate your avatar.
    • Revoke on SIT: Revokes permission when you sit on the object.
    • Revoke on STAND: Revokes permission when you stand up from sitting on the object.
    • Revoke on SIT and STAND: Revokes permission when you either sit or stand.
  • Texture Lag Protection:
    • Automatically hide large objects with high texture area: Enabling this will cause objects with large texture area to not be rendered. This can be used to combat griefing done via specific objects.
    • Threshold: Sets the threshold area to use; prims over this value will not be rendered. This may cause some normal objects to not display either.
  • Enable Spam Protection: These items allow you to protect yourself against various forms of spam, such as might be used in griefing attacks:
    • Max lines in a single message: this is the limit where the spam protection will start blocking messages from that source. ie. anything over this number of lines will be clocked.
    • Max events from same source: indicates the maximum number of events that can be recieved from a single source in 2 seconds before the source is blocked.
    • Sound play requests multiplier:
    • Sound preload requests multiplier:
    • Unblock all spam sources: will unblock anything that was blocked by the spam protection.
  • Confirm before paying. Threshold: Shows a confirmation dialog before paying sums over this value. To always show a confirmation, set the value to 0 (zero).

Avatar Tab

  • Amount that Avatar's head follows Mouse: Set both these sliders to zero if you do not want your avatar's head following the mouse cursor for unfocused mouse movement. They do not affect whether your head moves to look at something your camera is focused on.
    • Vertical range that avatar's head follows mouse: Controls how far or how little your head moves up and down to follow the movement of your mouse cursor.
    • Horizontal range that avatar's head follows mouse: Controls how far or how little your head moves left and right to follow the movement of your mouse cursor.
    • Disable random avatar eye movements: As the title suggests.
  • Selection beam particle effects:
    • Beam updates/sec: Controls how many particles the stream uses
    • Scale: Width of beam particle effect
  • Enable selection beam: Disable/enable the display of the particle beam
  • Send selection data to chat: (Formerly called SL Particle Chat). If enabled, selection start/stop information, and global position of an object being selected (edited) are sent on chat channel 9000.
  • LSL-Client Bridge external protocol integration:2)
    • Allow OpenCollar protocol to enable or disable the built in AO
    • Allow LockMeister protocol to enable or disable the built in AO

Windlight Tab

  • Automatically change environment to use region/parcel settings: If enabled, your WL settings will change if you TP into a region that has windlight region-level windlight settings. This is the same as top menu bar→ World → Environment Editor → Environment Settings→ Always use parcel/region settings.
  • Crossfade region environment sky presets changes made from quick prefs: Dynamically transitions sky settings.
  • Crossfade region environment water presets changes made from quick prefs: Dynamically changes water settings.

Firestorm WL Share

  • Use Firestorm Parcel Windlight sharing: Enables parcel level windlight sharing.
    • Auto apply WL settings from friend's land: If enabled the viewer will automatically see the windlight settings (no prompt) on a friends land if set.
    • Auto apply WL settings from my groups' land: If enabled the viewer will automatically see the windlight settings (no prompt) on group land if they are set.
    • Auto apply WL settings from any parcel: If enabled the viewer will automatically see the windlight settings (no prompt)on all parcels with it set by the owner.
    • Crossfade region environment changes for Parcel WL: Allows for dynamic changes between WL settings when a region with WL settings has parcels with their own, different, settings.
  • Crossfading duration: You can indicate how long the above crossfade transition effect should last.
  • Cloud Texture: You can select a different texture to be used to create Windlight clouds. Select from the drop down list. A relog is mostly likely required after changing.

Please refer to this page for more information on using Windlight with Firestorm.

Build 1 Tab

NOTE: For a video tutorial on setting custom default prim parameters, see here.

Default Object Size

Allows you to change parameters of your prim when it is first rezzed.

  • x/y/z Size: Sets the size, in meters, of the prim.

Settings

Default settings to use for newly created objects.

  • Phantom
  • Physical
  • Temporary
  • Material: Lets you choose the default material

Texture

Set default texture parameters for newly created objects.

  • Texture: Select the default texture to apply to newly created prims. Click to open the texture picker window.
  • Color: Click to open the color picker window, to select a default color.
  • Alpha: default transparency value.
  • Glow: Default value for glow.
  • Full Bright: whether full bright should be on by default or not.
  • Shiny: A drop down from which you can select the default shiny value.

Item Embedding

It is possible to automatically include an item into newly created prims.

  • Embed an item into new prims: Enable this to embed items.
    Then drag the desired item (for example, a landmark) into the space marked Drop an inventory item here. Once dropped, the space below will show the name of the item.

Default Creation Permissions Opens a window which allows you to select permissions to be applied, by default, to newly created items of different types. (Same as top menu, Build → Options → Set Default Permissions.))

Pivot Point

Allows you to change the pivot point of an object.

  • Show axis arrow on root prim position: Moves the axis from the center of the object to the center of the root.
  • Values are percent: When enabled the values are percentages.

LSL Preprocessor

  • Enable LSL Preprocessor: Enables the functionality offered by the LSL Preprocessor. This has a few additional options, if enabled:

Build 2 Tab

  • Enable highlighting of selected prims: Shows the yellow highlight on prims you select. Deselecting this can increase viewer performance when several prims are selected.
  • Highlight boundary of currently selected parcel: When editing an object, this will outline the containing parcel.
    • Show boundary up to maximum build height: When this is enabled, the highlight will be extended up to the max build height (currently 4096m).
  • Limit Select distance: Enable this is you wish to limit the distance at which you may select (edit) objects. To the right, you can specify the maximum distance, if this option is enabled.
  • Limit drag distance: If enabled, you won't be able to move objects over a distance greater than the limit set to the right. Disable to remove limits.
  • Constrain rotations to multiples of: Manual rotations will always “snap” to this number of degrees - when “snap to grid” is disabled.
  • Show unlink confirmation dialog if linkset has minimum: When unlinking a linkset, you will be asked for confirmation if there are this many, or more, linked items.
  • Use old “Set Object For Sale” behavior: Uses the old style for setting objects for sale. The new behavior safeguards against an object being purchased for the default 10L$ while you are setting the correct price. You click “For sale”, specify the price, then click Apply.
  • Save scripts edited from inventory as Mono: Allows you to set that scripts edited in inventory, will compile with Mono rather than LSL2.
  • Save textures from inventory to disk as PNG instead of TGA by default: Changes the default image save format, to save you having to change it manually.
  • Use Ctrl+mouse to grab and manipulate objects: If this is enabled, pressing Control while left clicking an object, will allow you to move it in-world.
  • Allow click-drag or click-scale (together with caps lock) of a texture face in build mode: If this is enabled, you will be able to click and drag - or scale- textures on a prim face. To do this, you need to be in Edit mode on the prim, enable Select Texture then click the prim face that you wish to modify.
  • Preview animations on own avatar during upload: If enabled, animations will be played in preview on your avatar when uploading them.

Uploads

This tab shows default Inventory folders for various types of uploads. In order to change a default upload folder, right click the desired folder in your Inventory window, and select Use as default for, then pick the upload type.



See this page for documentation on Firestorm 5.0.1 (52150) and earlier.

1)
If you have either of the SIT options enabled, then sitting on a scripted item will result in a script error being generated as the script will not be able to animate you.
2)
See this page for more information.

outfits_outfits_501.png - created

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*

Sunday June 11 3:00PM – Odds & Ends 1
This class covers some of Firestorm's handiest features, like Inventory, Radar, and some hard-to-find gems.
JU
Monday June 12 1:00PM – Introduction to Firestorm and the Wiki (TEXT ONLY)
This class gives you an overview of the Firestorm Viewer and of our greatest informational resource, our Wiki, including search tips.
FS
5:00PM – Menus 2
We will cover the Advanced and Develop menus in the top bar.
FS
Tuesday June 13 11:00AM – Preferences Set 1
We will cover some of the Firestorm preferences (General, Chat, Privacy), based on our current release.
FS
Wednesday June 14 7:00PM – Firestorm Skins
This class covers the differences among Firestorm's many skin options, including the Vintage Classic and Colorable User Interface skins.
FS
Thursday June 15 1:00PM – Menus 1 (TEXT ONLY)
We will be covering the menus on the top bar, from Avatar through Help.
FS
5:00PM – 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
Friday June 16 8:00AM – Contact Sets
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
Saturday June 17 6:00PM – Clean Install
Learn how to correctly and quickly perform this most fundamental and important of tasks. Recommended to take Settings Backup class first.
FS
Sunday June 18 9:00AM – 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
3: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.
JU
Monday June 19 1:00PM – Basic Troubleshooting (TEXT ONLY)
An introduction to basic methods to start locating problems. Focused on Firestorm but some parts are non-viewer-specific.
FS
5: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
Tuesday June 20 4:00PM — Avatar Complexity and Graphics Presets
Learn how to boost performance with av complexity and improve usability with the presets.
FS
Wednesday June 21 8:00AM – Menus 2
We will cover the Advanced and Develop menus in the top bar.
FS
Thursday June 22 1:00PM – Preferences Set 2 (TEXT ONLY)
We will cover some of the Firestorm preferences (Graphics, Network & Cache), based on our current release.
FS
4:00PM – Odds & Ends 1
This class covers some of Firestorm's handiest features, like Inventory, Radar, and some hard-to-find gems.
FS
Friday June 23 9:00AM – Preferences Set 3
We will cover some of the Firestorm preferences (Move & View, Advanced, Firestorm), based on our current release.
FS
Saturday June 24 11:00AM – Preferences Set 4
We will cover some of the Firestorm preferences (Colors, Skins, Notifications, User Interface, Sounds and Media).
FS
Sunday June 25 3:00PM – Reporting Bugs, Requesting Features
Learn how to communicate effectively with our devs to make the changes to Firestorm you want or need.
JU

firestorm_change_log_5.0.7.52912 - [Change Log Since 4.7.9.50527 Release]

$
0
0


IN PROGRESS…

Firestorm Release Notes 5.0.7 (52912) Release


Firestorm Release 5.0.7.52912 Downloads can be found HERE


New Features And Improvements In This Release

This page shows all changes since the 5.0.1.52150 Release.
If you are updating from an earlier version then 5.0.1, see HERE for previous release notes.

For a summary of all the major new features and improvements in this release, please
see Inara Pey's Firestorm 5.0.7 blog post.
FIXME


Linden Lab New Features and Improvements


  • Lots and lots of Maintenance fixes
    Too many to list them all here.
    See the full change log for details.
    Highlighted fixes are listed below.
    FIXME


Firestorm New Features and Improvements


  • Merge up to Linden Lab viewer 5.0.5 codebase
    Firestorm 5.0.7 is fully merged up to the 5.0.5 Linden codebase, plus some cherry picked fixes from upstream.
    Ansariel Hiller FIXME


RLVa Fixes and Improvements


Skinning And Translations


  • Translation updates and improvements
    German - Ansariel Hiller
    Polish - PanteraPolnocy
    Japanese - Hiroshi KumakiFIXME


For Photographers



For Builders And Scripters



Audio / Voice



Communications





Groups



Inventory, Appearance, Avatar



User Interface



General



Performance and Stability Improvements


  • Many MANY crash fixes and general performance improvements
    Big thanks to everyone who submitted their crash reports last release
    Nicky Dasmijn


OpenSim New Features and Improvements



Known Issues

FIXME

Firestorm JIRA Link Details Official viewer bug?1) New on 5.0.7?
FIRE-19704 Viewer crashes uploading mesh that uses a cube as the physics file Mac Only No No
FIRE-19333 Legacy Profile 2nd Life Pic sometimes blurry and opens at 32×32 instead of full size N/A No
FIRE-18160 [CEF] Media volume control has no effect on media volume. Mac & Linux onlyBUG-11821 No
FIRE-18045 [CEF] SLPlugin crahes frequently on Vista Vista Only Yes but no bug report No
FIRE-17838 [CEF] NHC TV's will not play media on any CEF enabled viewer.
This problem can only be fixed by the TV creator.
BUG-11485 No
FIRE-17868 Viewer crashes in nvwgf2umx.dll when Nvidia Shadow Play is enabled when opening Help → Report bug, Help → About, & sometimes when detecting hardware during launch. BUG-11530 No
FIRE-17392 Counts of individual Roles are reported wrong in the Group info BUG-10804 No
FIRE-17101 Unable to see group members belonging to any group role in the Roles tab until you switch to the Members tab and back to Roles tab. BUG-10447 No
FIRE-16745 Standing up from Groundsit triggers walk/run BUG-10122 No
FIRE-16672 [Linux 64bit] Media plugin gstreamer fail - linux x64
Linux 64bit Only
N/A No
FIRE-16496 [BigBird-merge] Using Wear to replace attachments sometimes incorrectly adds BUG-9454 No
FIRE-15854 Camming is broken in freeze frame mode once snapshot is refreshed since the STORM-2040 changes BUG-9021 No
FIRE-15967 Avatar moved underground when adding accessories to worn items while in edit mode. While wearing deformer skeleton. BUG-8616 No
FIRE-15852 Some rigged mesh avatars are deformed on post-attachment fix viewers for self and all observers BUG-9010 No
FIRE-12520 Highlight transparent no longer highlights particles that use a texture containing alpha BUG-4731 No
FIRE-12496 On Materials enabled viewers, textures containing alpha display as full bright if basic shaders are disabled BUG-4709 No
FIRE-12249“Develop → Render Metadata → Avatar Hitboxes” makes eyes disappear No No
FIRE-12213 Enabling Advanced Lighting Model in graphics preferences causes horizon to invert BUG-4430 No
FIRE-12115 Hairbase renders incorrectly in edit appearance mode when ALM is enabled BUG-4367 No
FIRE-12072 Alpha masking is broken again on avatar clothing when ALM is enabled BUG-4357 No
FIRE-11929 Some prims have black moire-like patterns when ALM is enabled MAINT-3302 No
FIRE-11740 Mesh clothing with solid/sheer clothing combo pixelated
Mac only
MAINT-3238 No
FIRE-10041 Rotating Objects flicker from a distance MAINT-2648 No
FIRE-10104 Camera won't follow objects when you paste new location using edit MAINT-2586 No
FIRE-7979 Changing from Ultra to Low with basic shaders disabled breaks much of the UI MAINT-3363 No
FIRE-6825 Show info - Show memory (usage) doesn't work
Mac and Linux only
MAINT-1421 No
FIRE-4963 using animation upload window disables physics wearables No No

Change Log Since 5.0.1.52150 Release

FIXME

1)
Only publicly viewable issues are given as links

firestorm_change_log

$
0
0

fs_avatar_complexity_settings - Replaced the complexity changes debug with alert

$
0
0

Avatar Complexity Settings

“Jellydolls” are a new anti-lag feature created by Linden Labs. You can use this feature to reduce your lag and to protect yourself against graphics-crashing devices worn by others.

For general information about Avatar Complexity (“jellydolls”), please see:

  • Torley Linden's short video tutorial:

This will give you a good overview of how jellydolls work and how they can help you. Don't try to find the settings the way Torley describes, since those are the official SL viewer settings! See the rest of this page for the Firestorm settings.

Please note: the official Second Life pages (above) describe how to find the settings in the official SL viewer. See the descriptions below for how to find them in Firestorm.

How to Adjust Who You See as Jellydolls

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.

To review avatars for whom you changed render settings

Go to the top menu bar> World menu and select Avatar Render Settings. Here you can change how avatars render for you. Refer to this page for details.

How to Adjust What Complexity Information You See on Screen

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 top right of your screen when you change clothes/accessories.
  • Go to Preferences → Notifications → Alerts, and move “Warn me about my avatar complexity changes” to the “Always show” box or to the “Never show” box, as you prefer.

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.

To see your own avatar complexity at any time

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

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



See this page for documentation on Firestorm 4.7.9 (50527) and earlier.

archive:fs_install_crash_fs501 - created

$
0
0

Crashing During Install or Startup

General

Firestorm Won't Start Up after a Recent Nvidia Update

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.

Startup Crash with "Must Supply A Comment For Control ..."

This indicates that a debug setting (a control) is missing a comment. It is unclear which comment is missing, but the fix is to reinstall Firestorm using the Clean Install procedures.

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. Be sure to use a fresh download of the viewer; either clear your browser cache or use a different browser for the download.

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.


archive:fs_intel_issues_fs501 - created

$
0
0

Graphics Issues After Win10 Update

If you start experiencing graphics issues after a Win10 update, such as driver crashes, or simply very poor performance, the first thing to try is a full computer reboot.

If that doesn't help, reinstall your graphics card driver from the card maker's website, not from Windows. That is, from nVidia, AMD, or Intel.

If you have Intel HD 2000 or 3000 graphics, refer to this page.

Laptop dual graphics issues

If your laptop has an Intel CPU and also has either an AMD or Nvidia graphics system, it may have the ability to switch between the Integrated Intel graphics or power savings, or the AMD/Nvidia for performance. But sometimes Firestorm isn't automatically configured to use the high performance graphics.

You can confirm this issue by looking at Help → About Firestorm and checking the name of the graphics card listed. If it says Intel, please follow the steps on this page.

Intel 500 Series & Flickering

Screen is Flashing on certain Graphics Settings

This mysterious flashing problem has been reported numerous times now and after some investigation we believe we finally have a repro for what's causing the issue. We do not yet know the specifics of exactly which systems are affected.

Typically the issue arises when Worn Rigged Mesh is in view and has at least one texture containing alpha and set to alpha blend mode. Alpha masking and emissive mask do not reproduce the problem.

We have also verified that this reproduces using the Official LL Viewer.

The Following Table shows which systems and drivers we have tested and whether they reproduce the Flashing Issue.

Graphics CardDriverOperating SystemRepoduced
Intel(R) HD Graphics 530 10.18.0015.4271 Windows 10 64-bit (Build 10240) Yes
Intel(R) HD Graphics 530 10.18.0015.4279 Microsoft Windows 10 64-bit (Build 10240) Yes
Intel(R) HD Graphics 520 10.18.0015.4293 Microsoft Windows 10 64-bit (Build 10586) Yes
Intel(R) HD Graphics 520 10.18.0015.4248 Microsoft Windows 10 64-bit (Build 10240) Yes
Intel(R) HD Graphics 520 10.18.0015.4279 Microsoft Windows 10 64-bit (Build 10240) Yes
Intel(R) HD Graphics 520 20.19.0015.4300 Microsoft Windows 10 64-bit (Build 10586) Yes
Intel(R) HD Graphics 530 20.19.0015.4352Microsoft Windows 10 64-bit (Build 10586) NO This Driver does NOT reproduce the issue

The Driver Version linked in the above table (DRIVER VERSION: 15.40.14.64.4352 & 15.40.14.32.4352) Has not reproduced the issue for us and is the Driver we recommend that you download direct from Intel.

If you receive the following Message when installing the Intel Driver:

The driver being installed is not validated for this computer. Please obtain the appropriate driver from the computer manufacturer.

This is an indication that you have an OEM Driver installed by the manufacturer. This Leaves you with two options:

  • Check the website (or contact support) of your specific PC manufacturer and check for updates.
  • Uninstall the OEM Driver and install the Intel Driver direct from Intel. This method is carried out At Your Own Risk

Temporary Work Around

If decide to wait fro an update from your computer manufacturer, or are simply uncertain about removing an installed driver, the following steps may help to make things more tolerable for you until your drivers are updated.

  • If ALM is disabled the flashing will always reproduce unless Hardware skinning is disabled.
  • If ALM is enabled the flashing will only reproduce when the avatar wearing the alpha blended rigged mesh is standing in Linden water.
    • If Hardware Skinning is disabled, the flashing stops in this case too.

Note: If you install the recommended driver above and still experience issues please read the related jira FIRE-17290 and add your details to the comments. Instructions for using the Jira can be found HERE

fs_intel_issues_new

$
0
0

Intel Issues

Windows 10 and Intel Stuck at Initializing VFS

If you have Intel Graphics HD, Intel Graphics HD2500 and Intel Graphics HD4000, and are using the 64bit version of Firestorm 5.0.7 or later, on Windows 10, refer to this page.

Graphics Issues After Win10 Update

If you start experiencing graphics issues after a Win10 update, such as driver crashes, or simply very poor performance, the first thing to try is a full computer reboot.

If that doesn't help, reinstall your graphics card driver from the card maker's website, not from Windows. That is, from nVidia, AMD, or Intel.

If you have Intel HD 2000 or 3000 graphics, refer to this page.

Laptop dual graphics issues

If your laptop has an Intel CPU and also has either an AMD or Nvidia graphics system, it may have the ability to switch between the Integrated Intel graphics or power savings, or the AMD/Nvidia for performance. But sometimes Firestorm isn't automatically configured to use the high performance graphics.

You can confirm this issue by looking at Help → About Firestorm and checking the name of the graphics card listed. If it says Intel, please follow the steps on this page.

Intel 500 Series & Flickering

Screen is Flashing on certain Graphics Settings

This mysterious flashing problem has been reported numerous times now and after some investigation we believe we finally have a repro for what's causing the issue. We do not yet know the specifics of exactly which systems are affected.

Typically the issue arises when Worn Rigged Mesh is in view and has at least one texture containing alpha and set to alpha blend mode. Alpha masking and emissive mask do not reproduce the problem.

We have also verified that this reproduces using the Official LL Viewer.

The Following Table shows which systems and drivers we have tested and whether they reproduce the Flashing Issue.

Graphics CardDriverOperating SystemRepoduced
Intel(R) HD Graphics 530 10.18.0015.4271 Windows 10 64-bit (Build 10240) Yes
Intel(R) HD Graphics 530 10.18.0015.4279 Microsoft Windows 10 64-bit (Build 10240) Yes
Intel(R) HD Graphics 520 10.18.0015.4293 Microsoft Windows 10 64-bit (Build 10586) Yes
Intel(R) HD Graphics 520 10.18.0015.4248 Microsoft Windows 10 64-bit (Build 10240) Yes
Intel(R) HD Graphics 520 10.18.0015.4279 Microsoft Windows 10 64-bit (Build 10240) Yes
Intel(R) HD Graphics 520 20.19.0015.4300 Microsoft Windows 10 64-bit (Build 10586) Yes
Intel(R) HD Graphics 530 20.19.0015.4352Microsoft Windows 10 64-bit (Build 10586) NO This Driver does NOT reproduce the issue

The Driver Version linked in the above table (DRIVER VERSION: 15.40.14.64.4352 & 15.40.14.32.4352) Has not reproduced the issue for us and is the Driver we recommend that you download direct from Intel.

If you receive the following Message when installing the Intel Driver:

The driver being installed is not validated for this computer. Please obtain the appropriate driver from the computer manufacturer.

This is an indication that you have an OEM Driver installed by the manufacturer. This Leaves you with two options:

  • Check the website (or contact support) of your specific PC manufacturer and check for updates.
  • Uninstall the OEM Driver and install the Intel Driver direct from Intel. This method is carried out At Your Own Risk
Temporary Work Around

If decide to wait fro an update from your computer manufacturer, or are simply uncertain about removing an installed driver, the following steps may help to make things more tolerable for you until your drivers are updated.

  • If ALM is disabled the flashing will always reproduce unless Hardware skinning is disabled.
  • If ALM is enabled the flashing will only reproduce when the avatar wearing the alpha blended rigged mesh is standing in Linden water.
    • If Hardware Skinning is disabled, the flashing stops in this case too.

Note: If you install the recommended driver above and still experience issues please read the related jira FIRE-17290 and add your details to the comments. Instructions for using the Jira can be found HERE



See this page for documentation on Firestorm 5.0.1 (52150) and earlier.

fs_install_crash_new

$
0
0

Crashing During Install or Startup

General

Firestorm Won't Start Up after a Recent Nvidia Update

Firestorm "Locks Up" on "Initializing VFS"

If you have Intel Graphics HD, Intel Graphics HD2500 and Intel Graphics HD4000, and are using the 64bit version of Firestorm 5.0.7 or later, on Windows 10, refer to this page.

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.

Startup Crash with "Must Supply A Comment For Control ..."

This indicates that a debug setting (a control) is missing a comment. It is unclear which comment is missing, but the fix is to reinstall Firestorm using the Clean Install procedures.

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. Be sure to use a fresh download of the viewer; either clear your browser cache or use a different browser for the download.

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 5.0.1 (52150) and earlier.

fs_intel_fix_32bit - [Downloads - Firestorm 4.7.5]

$
0
0

How to Replace Your Firestorm.exe in Windows 10

If you have certain Intel HD graphics, and have upgraded your PC to Windows 10, your graphics card will not be fully supported by Intel. If you have this issue, you will be unable to log in. You will get the following error dialog box:

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

This is not a function of the viewer, but instead is a function of the drivers provided by Intel for your computer. However we have developed a workaround that should help most users with this issue continue to have the ability to use the Firestorm viewer.

Note: This fix is only available for 32 bit versions of Firestorm. Even if you have a 64 bit version of Windows 10, and usually use the 64 bit version of Firestorm, you will need to use the 32 bit for 4.7.9 (4.7.7 and 4.7.5) as we do not have a fix that will work with the 64bit version

Important: Do NOT run in Compatibility mode.
Do NOT uninstall Firestom; you will be replacing one or more files, not the enitre install.

  1. Verify that your graphics card is one of the affected versions. You can find a table of affected versions here: Graphics Drivers Supported Operating Systems but most frequently we have seen Intel HD 2000 and Intel HD 3000. You should be able to verify your graphics in the system info of your computer.
  2. Below, select the zip file that is correct for your download, either the 32 bit Havok version or the 32 bit OpenSim version, download it to your computer. You will need to unzip the file and save it on your computer in a location you will remember.
  3. On your computer, open File Explorer. (If it isn't on your taskbar you may need to use the search to find it). When you open it, select the View tab at the top of the page and check the box on the right had side that says File Name Extensions.
  4. In File Explorer, navigate to This PC then Local Disk (C:) (or the location you normally download Firestorm if it differs) and then navigate to Program Files (x86). Open Program Files (x86), locate the Firestorm folder, and open it. In the Firestorm folder, locate the Firestorm-Release.exe file and delete it.
  5. Replace it with the Firestorm.exe file that was in the zipped folder you downloaded from the website.

You should now be able to run Firestorm on your PC.

Downloads - Firestorm 5.0.1

Downloads - Firestorm 4.7.9

Downloads - Firestorm 4.7.7

Other Information

Click here to update your graphic drivers: Intel Downloads

Click here to contact Intel Support: Intel Support

Note: When using this workaround your Help–> About Firestorm panel will show your OS as Windows 8 rather than Windows 10.

archive:win10_fs501 - created

$
0
0

Windows 10 Issues

Massive FPS Drop after Viewer Window Loses Focus

This issue is the result of recent updates of Win10, specifically KB3176938, KB3189866, KB3193494 and KB3194496.

Many users have reported that updating their graphics drivers has fixed the problem:

Should you not be able to upgrade the driver, read on.

  • To uninstall these Windows updates, go to Programs & features > view updates > click and uninstall. Please be advised that uninstalling any update marked as a security update is done at your own risk.
  • To keep windows from downloading the update again download this tool and run it to “hide” the update: https://support.microsoft.com/en-us/kb/3073930?utm_source=twitter#bookmark-1607.
  • Note: “Hiding” one update will not prevent other, later updates. The FPS problem may return as other updates are installed and until Microsoft fixes this issue.

Please refer to this LL JIRA and this FS JIRA page for details and other suggestions.

Voice Is Distorted

If you suddenly sound like a man (and you aren't), or your friend suddenly sounds like a demon (and isn't), or you are hearing other forms of distorted voice, try this:

  1. Right click the Speakers icon on your system tray and select Recording Devices.
  2. Right click the Microphone and select Properties.
  3. Switch to the Advanced tab.
  4. Under Default Format drop down menu, select: 2 channel, 16 bit, 44100 Hz (CD quality).
  5. Untick “Enable Audio Enhancements”
  6. Press OK and OK.
  7. Relog if needed.

Sounds Don't Play

If you suddenly find that sounds do not play, things like button sounds or in-world object sounds, the possible cause is your default output format. Try this:

  1. Right click the Speakers icon on your system tray and select Playback Devices.
  2. Right click the Speakers (or your chosen audio output) and select Properties.
  3. Switch to the Advanced tab.
  4. Under Default Format drop down menu, select: 16 bit, 44100 Hz (CD quality).
  5. Click Apply and OK.
  6. Relog if needed.

Missing Characters

If some characters now display as boxes, you will need to reinstall Windows font packs. Some of the more common font packs are Chinese, Japanese and Korean, though if you installed those and still see boxes, you will want to ask the person using those characters to tell you what language (or symbol set) they are so that you can install the appropriate font pack.

  1. Log out of Firestorm.
  2. Go to the Windows Start menu and choose Settings.
  3. In the window that opens, click in the search field at the top right and type in “language”
  4. Select Add a language from the search results.
  5. Click the + Add a language option and select the language from the list. The contents of the window scrolls left and right.
  6. Back in the Add a language section, click the newly added language and choose Options.
  7. Click the top Download button. The language will download and install, and it may take some time.
  8. Repeat this for each language pack you wish to install.
  9. Now log into Firestorm, you should see the missing characters correctly rendered.

Error 0xc000007b

Error 0xc000007b when launching 64 bit Firestorm:

Try following these steps to get the Firestorm installer to reinstall the Visual C++ redistributables that come packaged with it:

  1. First make sure you have the Firestorm installer handy in a place where you can easily access it when you get to the step where it's needed below. (You can download it from here, or from here if you need an older version than the current release.)
  2. Go to the Windows Start Menu and choose Settings.
  3. In the window that opens, click on “System Display, notifications, apps, power.”
  4. In the next window go down to “Apps & features.”
  5. Scroll down to the entry for “Microsoft Visual C++ 2010 x86 Redistributable.” Click on it and choose “Uninstall” (the list won't necessarily update to show that it is uninstalled, but it is).
  6. Click on “Microsoft Visual C++ 2010 x64 Redistributable” and once again choose “Uninstall.”
  7. Close that window.
  8. Re-run the Firstorm installer. The installer window will now say “Modify Setup” (since FS is already installed) and will give you 3 options: “Repair”, “Uninstall” and “Close.” Click on “Repair.” Firestorm will reinstall the Microsoft Visual C++ 2010 Redistributables that it ships with.
  9. Restart your computer. You should be able to launch Firestorm without getting the error message now.

Graphics Issues After Win10 Update

If you start experiencing graphics issues after a Win10 update, such as driver crashes, or simply very poor performance, the first thing to try is a full computer reboot.

If that doesn't help, reinstall your graphics card driver from the card maker's website, not from Windows. That is, from nVidia, AMD, or Intel.

If you have Intel HD graphics, refer to this page.

Camera Spinning or Mouse Wandering in Mouselook

The most common cause for this is a non-default DPI value, or screen scaling. Refer to this page for tips on setting DPI/scaling to default.

Unable to install current version of Quicktime

Some Windows 10 users have experienced difficulty installing current versions of Apple's Quicktime software on their systems. Version 7.7.6 of Quicktime has been confirmed to install correctly on Windows 10 systems. You can download version 7.7.6 from the link below:

Quicktime 7.7.6 (link will take you to the 7.7.6 download page on Apple's website)

**Unfortunately the above link seems to no longer be valid as a source for Quicktime 7.7.6, as such the recommended alternative to allow playback of media streams that were previously handled by Quicktime is to upgrade to a newer version of Firestorm (version 5.0.1.52150 or newer), as these newer versions of Firestorm no longer depend on Quicktime to handle stream playback.

Text and User Interface Too Small

First try increasing Preferences → User Interface → 2D Overlay → UI Scaling. Another possibility is Preferencess → User Interface → Font → Font size adjustment.

Viewer Window Larger Than Expected

This is most often caused by a high DPI scaling setting, usually 125% on most 2k displays. A viewer set to the same width as the display resolution (1920, for example), would extend beyond the display border. To correct this:

  • Log out of Firestorm
  • Right click the Firestorm shortcut and choose Properties
  • In Properties, click the Compatibility tab
  • Near the bottom, find and check “Disable display scaling on high DPI settings”
  • Click OK and Apply

When you launch Firestorm, it should display at the default DPI scale, 100%

Failed to Decode Login Credentials

Some Windows 10 updates change the machine ID used to create login credentials, resulting in Firestorm reporting “Failed to Decode Login Credentials”. The best way to deal with this is to wipe the stored credentials file, as explained here. Naturally, you will then have to retype the user name and password for all your accounts, when first logging in after deleting the credentials file.



See this page for documentation on Firestorm 4.7.9 (50527) and earlier.

win10_new

$
0
0

Windows 10 Issues

Windows 10 and Intel stuck at initializing VFS

If you have Intel Graphics HD, Intel Graphics HD2500 and Intel Graphics HD4000, and are using the 64bit version of Firestorm 5.0.7 or later, on Windows 10, refer to this page.

Massive FPS Drop after Viewer Window Loses Focus

This issue is the result of recent updates of Win10, specifically KB3176938, KB3189866, KB3193494 and KB3194496.

Many users have reported that updating their graphics drivers has fixed the problem:

Should you not be able to upgrade the driver, read on.

  • To uninstall these Windows updates, go to Programs & features > view updates > click and uninstall. Please be advised that uninstalling any update marked as a security update is done at your own risk.
  • To keep windows from downloading the update again download this tool and run it to “hide” the update: https://support.microsoft.com/en-us/kb/3073930?utm_source=twitter#bookmark-1607.
  • Note: “Hiding” one update will not prevent other, later updates. The FPS problem may return as other updates are installed and until Microsoft fixes this issue.

Please refer to this LL JIRA and this FS JIRA page for details and other suggestions.

Voice Is Distorted

If you suddenly sound like a man (and you aren't), or your friend suddenly sounds like a demon (and isn't), or you are hearing other forms of distorted voice, try this:

  1. Right click the Speakers icon on your system tray and select Recording Devices.
  2. Right click the Microphone and select Properties.
  3. Switch to the Advanced tab.
  4. Under Default Format drop down menu, select: 2 channel, 16 bit, 44100 Hz (CD quality).
  5. Untick “Enable Audio Enhancements”
  6. Press OK and OK.
  7. Relog if needed.

Sounds Don't Play

If you suddenly find that sounds do not play, things like button sounds or in-world object sounds, the possible cause is your default output format. Try this:

  1. Right click the Speakers icon on your system tray and select Playback Devices.
  2. Right click the Speakers (or your chosen audio output) and select Properties.
  3. Switch to the Advanced tab.
  4. Under Default Format drop down menu, select: 16 bit, 44100 Hz (CD quality).
  5. Click Apply and OK.
  6. Relog if needed.

Missing Characters

If some characters now display as boxes, you will need to reinstall Windows font packs. Some of the more common font packs are Chinese, Japanese and Korean, though if you installed those and still see boxes, you will want to ask the person using those characters to tell you what language (or symbol set) they are so that you can install the appropriate font pack.

  1. Log out of Firestorm.
  2. Go to the Windows Start menu and choose Settings.
  3. In the window that opens, click in the search field at the top right and type in “language”
  4. Select Add a language from the search results.
  5. Click the + Add a language option and select the language from the list. The contents of the window scrolls left and right.
  6. Back in the Add a language section, click the newly added language and choose Options.
  7. Click the top Download button. The language will download and install, and it may take some time.
  8. Repeat this for each language pack you wish to install.
  9. Now log into Firestorm, you should see the missing characters correctly rendered.

Error 0xc000007b

Error 0xc000007b when launching 64 bit Firestorm:

Try following these steps to get the Firestorm installer to reinstall the Visual C++ redistributables that come packaged with it:

  1. First make sure you have the Firestorm installer handy in a place where you can easily access it when you get to the step where it's needed below. (You can download it from here, or from here if you need an older version than the current release.)
  2. Go to the Windows Start Menu and choose Settings.
  3. In the window that opens, click on “System Display, notifications, apps, power.”
  4. In the next window go down to “Apps & features.”
  5. Scroll down to the entry for “Microsoft Visual C++ 2010 x86 Redistributable.” Click on it and choose “Uninstall” (the list won't necessarily update to show that it is uninstalled, but it is).
  6. Click on “Microsoft Visual C++ 2010 x64 Redistributable” and once again choose “Uninstall.”
  7. Close that window.
  8. Re-run the Firstorm installer. The installer window will now say “Modify Setup” (since FS is already installed) and will give you 3 options: “Repair”, “Uninstall” and “Close.” Click on “Repair.” Firestorm will reinstall the Microsoft Visual C++ 2010 Redistributables that it ships with.
  9. Restart your computer. You should be able to launch Firestorm without getting the error message now.

Graphics Issues After Win10 Update

If you start experiencing graphics issues after a Win10 update, such as driver crashes, or simply very poor performance, the first thing to try is a full computer reboot.

If that doesn't help, reinstall your graphics card driver from the card maker's website, not from Windows. That is, from nVidia, AMD, or Intel.

If you have Intel HD graphics, refer to this page.

Camera Spinning or Mouse Wandering in Mouselook

The most common cause for this is a non-default DPI value, or screen scaling. Refer to this page for tips on setting DPI/scaling to default.

Unable to install current version of Quicktime

Some Windows 10 users have experienced difficulty installing current versions of Apple's Quicktime software on their systems. Version 7.7.6 of Quicktime has been confirmed to install correctly on Windows 10 systems. You can download version 7.7.6 from the link below:

Quicktime 7.7.6 (link will take you to the 7.7.6 download page on Apple's website)

**Unfortunately the above link seems to no longer be valid as a source for Quicktime 7.7.6, as such the recommended alternative to allow playback of media streams that were previously handled by Quicktime is to upgrade to a newer version of Firestorm (version 5.0.1.52150 or newer), as these newer versions of Firestorm no longer depend on Quicktime to handle stream playback.

Text and User Interface Too Small

First try increasing Preferences → User Interface → 2D Overlay → UI Scaling. Another possibility is Preferencess → User Interface → Font → Font size adjustment.

Viewer Window Larger Than Expected

This is most often caused by a high DPI scaling setting, usually 125% on most 2k displays. A viewer set to the same width as the display resolution (1920, for example), would extend beyond the display border. To correct this:

  • Log out of Firestorm
  • Right click the Firestorm shortcut and choose Properties
  • In Properties, click the Compatibility tab
  • Near the bottom, find and check “Disable display scaling on high DPI settings”
  • Click OK and Apply

When you launch Firestorm, it should display at the default DPI scale, 100%

Failed to Decode Login Credentials

Some Windows 10 updates change the machine ID used to create login credentials, resulting in Firestorm reporting “Failed to Decode Login Credentials”. The best way to deal with this is to wipe the stored credentials file, as explained here. Naturally, you will then have to retype the user name and password for all your accounts, when first logging in after deleting the credentials file.



See this page for documentation on Firestorm 5.0.1 (52150) and earlier.

intel_vfs

$
0
0

Windows 10 and Intel stuck at initializing VFS

These instructions apply specifically to:

  • Windows 10 Operating System
  • Intel Graphics HD, Intel Graphics HD2500 and Intel Graphics HD4000
  • 64bit version of Firestorm only

Windows 10 updates since March 2017 have resulted in users experiencing stalling or crashing at “initializing VFS”.

Firestorm Release 5.0.7.52912 addresses this issue, but you must do this additional step once you have installed the 64bit version:

1. While logged out of Firestorm.
2. Right click the desktop shortcut for the 64bit Firestorm → Properties → Shortcut tab.
3. In the “Target” text box, go to the end of the text, *add a space* and then add this exact text to the end: --noprobe.

"C:\Program Files\FirestormOS-Releasex64\FirestormOS-Releasex64.exe" --set InstallLanguage en --noprobe 

4. Click “OK” to apply to save changes and launch Firestorm as normal.

For reference, see: https://jira.phoenixviewer.com/browse/FIRE-21109
[Windows 64bit] Windows 10 - Stuck on “Initializing VFS” after KB4015217 on Intel HD, Intel HD 2500 & Intel HD 4000 cards on 64bit viewers only.

Reminder to check directly with the Intel website for the most up to date drivers. https://downloadcenter.intel.com/


animation_overrider - [Special Note Concerning Bento Animations]

$
0
0


Video tutorials are available here.

Firestorm Client AO

The Firestorm viewer has a built-in AO (Animation Overrider). This makes the use of scripted AOs unnecessary, which in turn reduces the amount of scripts you wear, and so server-side lag.

Introduction

The AO is accessed via a button on the bottom button bar.

The AO is activated by clicking the button labeled AO; it will show pressed down, as in the image above. To disable it, press the button again, and it will appear released.

To the right of this is an up arrow. Clicking that pops up a small window, the mini AO view, which gives quick and easy access to a few basic functions, such as moving from one stand animation to another, toggling sit overrides and loading a new set of animations. Clicking this same button again will close the window.

This small window has a screwdriver-wrench icon; clicking that opens the AO window to its largest size, allowing full control of the AO.

Terms Used

A brief glossary of terms as they are used here.

  • AO: Animation Override or Animation Overrider. Generally, a scripted attachment worn as an HUD, containing animations and notecards which, along with the scripts, animate the avatars while it is in certain states, such as standing, walking, flying, etc. Absent an AO, the avatar will use basic default Linden-defined animations. The Firestorm client AO replaces the usual scripted AO by duplicating its functions, without the script overhead.
  • Animation Set: The collection of animations which, taken together, make up any given AO.
  • Animation Group: One or more animations which serve to replace a single animation state. Examples of animation groups include stands, sits, walks, etc. All of the animation groups, together, make up an animation set.

Using the AO

There are Firestorm AO videos are available for you to watch, we strongly suggest watching them; see here. See also the Firestorm Class Recording.

Basic functions of the AO can be accomplished via the mini AO view shown below.

  • Currently loaded animation set: Referring to the image above, the currently loaded set is named “! Default”. By clicking the small down arrow, you can easily select another set (if others are available, of course).
  • Screwdriver-Wrench icon expands the mini window to full size for greater control; see below for more.
  • Left/Right Arrows switch to the previous and next animation in the current group, respectively.
  • “Sit” checkbox indicates whether the AO should override sits animations that are part of scripted furniture. If this is enabled, the AO will try to force the use of whatever sit animation you have in the animation set 1) ; if disabled, then the animation in the furniture will be used.

For greater control over the AO, click the Screwdriver-Wrench icon; this will open the AO window to maximum size. It looks like this.

  • The Current animation set is shown in the top drop-down. Clicking the down arrow beside it allows for the selection of an alternate animation set (if you have others available, of course). You can rename your AO set right here. Just click the name and change it to what you want it to be.
  • The check mark to the right of the animation set name will activate the animation set. click this if you have picked a new one.
  • Default: check this if you wish to make the current animation set the default when you start Firestorm.
  • Override sits: Does the same thing as the Sits checkbox described above.
  • Be Smart: If this is enabled, the AO will try to determine whether the furniture being sat on has an animation; if it determines that it does, it will disable the sit in the AO, so the one in the furniture will be used instead.
  • Disable Stands in Mouselook: If this is checked, the AO will disable stand animations when mouselook is entered. This is useful for combat situations, for example.
  • + Button: Click this button to manually define a new animation set.
  • Trash: To delete the current animation set, click this button.
  • Animation Group: With this drop down you can select an animation group, such as Standing, Walking, Running, etc. Having selected one, you can then change the order in which animations are played, by using ….
  • Up/Down Arrows: moves the currently selected animation up or down in the list, thus changing the order in which the animations are played in the animation group.
  • Trash: Clicking this will delete the currently selected animation from the animation group. This will NOT delete the animation itself; just the reference to it, from the group.
  • Cycle: Enabling this will cause a different animation to be played, from the selected group, at each “cycle time” interval (see below).
  • Randomize order: Enabling this causes the animations in the selected group to be played in random order.
  • Cycle time: Indicates how long an animation should play before the next one begins. Set this to zero to disable.
  • Reload: Forces the AO to reload the configuration of the current animation set.
  • Left/Right Arrows: skips to the previous/next animation in the current animation group. These are the same arrows seen in the mini AO view, described previously.
  • Down Arrow: The arrow in the bottom right corner collapses the full AO window into the mini view, which was described above.

Loading a Prepared AO Notecard

If you own a scripted AO, the type worn as an HUD attachment, you can transfer it to the client AO quite easily. You may follows these steps to do so. Multiple AOs can be loaded, and you can switch from one to another simply by selecting the set within the Firestorm AO.

NOTE: The notecard must be in standard ZHAO II format, or in Oracul format. Most AO creators support ZHAO II so you should not run into issues. However, it must be noted that some major vendors have extended the ZHAO II format, and thus their AO notecard will need to be edited before they can be used in the Firestorm AO. Similarly, older AOs which use the old ZHAO format will have to be converted.

NOTE: Unlike Phoenix, the animations and notecard do not need to be placed in a special predefined folder. However, they do need to be together in the same place. Once imported, the Firestorm client AO creates a new special folder: #Firestorm → #AO. This folder is protected - meaning, it cannot be deleted, nor items removed from it 2) . Inside that are several more folders, containing links to the original animations. So do not delete the original animations used or the AO will “break”.

Method 1

Follow these steps if you are in a location where you can build; if requires the ability to rez out.

  • Rez a cube on the ground.
  • If you are wearing the scripted AO, detach it.
  • Cam into the cube you made, then drag the AO onto it. HUDs are normally very small when rezzed in-world, and can be hard to see if you are not cammed in.
  • Right click AO you rezzed out and select Open. A window opens which will list the contents of the AO; once this has fully populated, click Ok.
    This will result in the creation of a folder in your inventory, containing everything in the AO: scripts, animations and notecards.
  • If the AO is copyable, you can now delete it; otherwise, take it back into your inventory. Then delete the cube.
  • Locate the folder that was created in the step above. This folder can be dragged to another folder where it is out of the way but still available, like the Animations folder, for example.
  • Inside the folder, locate the notecard which defines the AO. An example is shown below.
  • Open the Firestorm AO to maximum, then drag the AO notecard onto the Firestorm AO window.
  • The notecard is parsed and if all goes well, you have finished transferring the AO.
  • Select options to apply, like whether this will be the default animation set, whether to override sits, etc.

Method 2

You can follow these steps if you are unable to rez the AO out in-world, for whatever reason.

  • Location the Animations folder in your inventory - it is at the top. Right Click the folder name, and select New Folder.
  • Type in a name for the folder - for example, give it the name of the AO you are transferring.
  • Make sure the AO HUD is worn; right click it and select Edit.
  • Click on the Content tab.
  • Once the AO contents are all displayed, select all items: click on the top one, then use the scroller to scroll to the bottom, press and hold Shift, and click on the last item.
  • Drag all the items into the folder you created.
  • Close the edit window.
  • Inside the folder, locate the notecard which defines the AO. An example is shown below.
  • Open the Firestorm AO to maximum, then drag the AO notecard onto the Firestorm AO window.
  • The notecard is parsed and if all goes well, you have finished transferring the AO.
  • Select options to apply, like whether this will be the default animation set, whether to override sits, etc.

Example AO Notecard

As noted above, the Firestorm AO supports notecards in the standard ZHAO II format. Here is an example of what such a notecard looks like:

[ Standing ]vAStand01DANGER|VAStand05_DANGER_F|VAStand02_DANGER|VAStand06_DANGERe
[ Standing ]VAStand04_DANGER|VAStand06_iDANGER|VAStand07_DANGER3|VAStand08_DANGER30
[ Standing ]VAStand09_DANGER|vAStand11_DANGER|VAStand12_DANGER|VAStand13_DANGER|VAStand14_DANGER
[ Walking ]08WALKDANGER|DANGERMIXWALK1|DANGERMIXWALK2.3
[ Sitting ]sit01DANGER|sit02DANGER|sit03DANGER|sit04DANGER|sit00DANGER
[ Sitting On Ground ]sitgDANGER01|SitGDANGER2|sitgDANGER3
[ Crouching ]crounch02DANGER|VAmocCROUNCH3
[ Crouch Walking ]vAFLIPWALK2
[ Landing ]landing2DANGER|Landing_Jump03_AN
[ Standing Up ]vA_boxerlanding1
[ Falling ]fall_VA_fly3
[ Flying Down ]vA_DangerFlyDown
[ Flying Up ]vA_DANGERflyUp
[ Flying ]vA_DangerFly|VAmocFLIGHT2
[ Flying Slow ]vAmocFSLOW
[ Hovering ]vA_DANGERhover_v02
[ Jumping ]jump02DANGER|jump_Jump03_AN
[ Pre Jumping ] v3_VA_Prejump|preJump_Jump03_SL
[ Running ]vISTARUN
[ Turning Right ]vATURNR
[ Turning Left ]vATURNL
[ Floating ]fLOAT
[ Swimming Forward ]vA.DIVE
[ Swimming Up ]
[ Swimming Down ]
[ Typing ]typex

Notice how the animation state is in brackets, followed by each name of the animation separated with a pipe character “|”. Lines should not be longer than 255 characters, and in the example above, the animations in the Standing group have been broken up into several lines so they are shorter and easier to read.

NOTE: It is best to delete any/all lines containing comments, before loading into the client AO. Comment lines usually start with a # character.

Creating an AO Manually

There is no need to have a prepared AO with a notecard to create an AO in Firestorm; you can “roll your own” if you have animations to use.

You should have the AO window at maximum size, as shown above.

  • Click the + button near the top right corner to create a new animation set. You will be prompted to supply a name for it.
  • A new, blank animation set is created; make sure it is showing in the list of animation sets. You can now begin to fill. It starts with the Standing group selected.
  • In your inventory, select the animation(s) to be used as stands. Drag them from your inventory onto the AO window. (Note that it is faster to drag them all in at once rather than one by one.) The AO processes, then you can continue.
  • Once you have dropped all the stands in, you can switch to another animation group, like Walking. Again, select and drag the animations from your inventory onto the AO.
  • Repeat this for all groups for which you have animations.
  • Select options to apply, like whether this will be the default animation set, whether to override sits, etc.
  • Do not delete the original animations used or the AO will “break”.

Special Note Concerning Bento Animations

The Firestorm AO was designed before bento came onto the scene. Therefore, while it fully supports bento animations that affect the entire avatar, it doesn't necessarily support partial animations. This because it wasn't designed to handle multiple animations running at the same time.

Specifically, it seems to work very well when used with animation HUDs for bento heads and hands, but it may cause the avatar to lock up when used with HUDs for bento wings or tails. If you do find that you lock up, you will need to revert to using a scripted AO for all animations.

Other options related to the Firestorm AO.

  • Turn avatar around when walking backward: in Preferences→ Move & View → Firestorm. If enabled, when you press the down arrow to walk backward, your avatar will turn to face the camera. If disabled, then your avatar will walk backward.

The AO may also be controlled by scripts. This can be very handy for those who wear collars, for example. For more information on how to implement this, see this page.

1)
Note: Animation priority will always have precedence; if the animation in the furniture has higher priority than the one in your animation set, it will be used regardless of how you have this checkbox set. Animation priority is set at upload and cannot be changed afterward, not even by the creator - unless the creator uploads again, and sets a different priority.
2)
Therefore, avoid dragging items into it. Should you do so by mistake, please refer to this page to see how to fix this.

lag

$
0
0

Lag - What Is It?

People use the term a great deal, but usually without really understanding what it means, what causes it or how to deal with it. Some of the things commonly suggested to reduce lag actually have little or no effect.

First off, “lag” is a catch-all word that actually covers three very different things, and it is important to distinguish between them. Most lag reduction methods only deal with one of these three aspects.

You can use the Statistics Bar to get detailed information of what might be causing lag.

Network Lag

This is when you have connectivity issues. There are problems somewhere in the network between your computer and the LL servers. This usually can be noticed when you start to experience packet loss. Press Shift-Ctrl-1 (or Advanced1)→ Performance Tools → Statistics Bar) and look at the top, packet loss; ideally this should be 0%; if it isn't, you have a connectivity issue and are losing data. Also, check Ping SIM. Ideally, this should be under 200.

Symptoms of a poor connection include (but are not limited to):

  • failure of your avatar or textures to rez;
  • object information not displaying in hover tips when you mouse over the object;
  • teleport failure;
  • random disconnections.

You can try to mitigate network lag by playing with your bandwidth. Too high, or too low, a value will result in network lag. For information on how to determine your optimal bandwidth, refer to this page.

Aside from the network issues mentioned above, some programs may inhibit or interfere with a good connection. Some firewall software and anti-virus programs are known to do this. You may want to temporarily disable them and see if the situation improves.

Client Side

Everything you see has to be drawn by your graphics card. When there is too much to draw, when your computer cannot keep up, you experience client-side lag. Avatar Render Weight (formerly known as ARC - Avatar Rendering Cost) is part of client-side lag, as the name itself says.

Symptoms of client-side lag include jerky or sluggish movement.

There are many things you can do to reduce this, without having to ask people to adapt to you:

  • reduce your draw distance (do you really need to see 512m away?);
  • turn on avatar impostors (this makes drawing of distant avatars much faster);
  • disable atmospheric shaders (which serves to drastically reduce how much your computer has to render, as the sky alone is very graphics-intensive);
  • if need be, inhibit the rendering of other avatars: Advanced → Rendering Types → Avatar - or derender them.
  • try reducing your level of detail settings for everyday use or to improve performance: Preferences → Graphics → Objects and Sculpts LOD; you can always adjust this setting again temporarily if something specific fails to render for you.

Client side lag is local to you. It is a direct result of how powerful your computer is. It is no one else's fault if your computer cannot handle a specific situation. So if you're in a high-lag setting, adapt temporarily as described above.

It must also be pointed out that client side lag does NOT affect things like scripts, at all. It has next to zero impact on a SIM's performance.

Particles

Contrary to popular belief, particles do not “lag a SIM'. Their effect on a SIM, on the servers, is in fact close to zero. Particles are almost entirely client-side. They are rendered on your computer, by your graphics card, and in fact, do NOT require a script to keep them going. They need a script to initiate the effect, yes, but afterward the script may be removed and the particle effect will keep going forever - until another script is dropped in to turn them off, or the object is taken or deleted.

If you find that particles are “lagging you”, it is wrong to ask that the effect be stopped. Instead, stop it yourself, on your own computer. That way others who are less affected may continue to enjoy them.

You can disable particles in a number of ways:

  • Advanced → Rendering Types → Particles
  • Preferences → Graphics → Max. particle count - set to 0

Doing any of these things will stop particles “lagging you”. There is no need to ask others to degrade their SL experience on your behalf. Also, again, particles do NOT cause server-side or script lag. Even if the scripts are not removed, a single one uses 0.02ms script time.

Owners of venues that have a “no particles” policy may mean well, but are misinformed. Again, particles do not lag a SIM, and are very easily dealt with client-side as described previously. Those venue owners are aiming at the wrong target in trying to reduce lag: particles aren't it, scripts are - and even more so, moving avatars (see below). You can't remove the avatars, of course, but you can request that they not show up with heavily scripted attachments.

(Having said that, every little bit helps when it comes to reducing script lag, so if you have a particle effect that does not require the script to be in it at all times, remove it.)

Server Side

Server-side lag is caused by several things, independently. There are two major causes; all others are secondary and negligible. They are, in order of impact on a SIM:

  • Physics. People, even wearing nothing at all, with an Avatar Render Weight of 1, and no scripts, will lag a SIM. The SIM needs to keep track of where each avatar is, to prevent them walking through one another, floors, walls, etc. Avatar movement is VERY high when it comes to server side lag. Sitting down reduces this lag significantly. Your avatar, in fact, becomes linked to the prim you're sitting on.
  • Scripts. This is common knowledge, compared to the previous point. If you know you're going to a busy event, then remove scripted attachments, as many as possible. An AO in and of itself is negligible when compared to hair that is resize-scripted. Keep the AO, and instead ensure that your hair, shoes and other attachments have no resize scripts in them. (There is no good reason whatsoever for anyone to be carrying around more than 200 scripts on a human avatar, even when in full RP attire, with combat HUDs.)

Contrary to popular belief, prims do not lag a SIM - or more precisely, their effect on lag is miniscule compared to the two things mentioned above. Scripted prims cause lag; unscripted ones do not - relatively speaking, of course.

So, if you're going to an event, before you leave for it, check your attachments (hair, shoes, etc.) to ensure that they are unscripted. To those running events, it is strongly suggested that you ask attendees to do these things; a badly lagged SIM affects everyone at the event.

NOTE: As stated earlier, lag caused by physics (primarily avatar movement) is the number one cause of region lag. If physics lag is bad enough, scripts simply will stop running; avatar movement is considered more important than scipts. If there are 40 people at an event, and many are moving about, it will be laggy even if none of those people are wearing scripts.

NOTE: Moving away from a scripted prim will not do anything to reduce the “lag” it may be causing you. Scripts all run on the region server, and therefore, they are “global” to the server. No matter where you are in the region, the effect of that script running - that is, the time taken to run it, and the memory it consumes - will be felt on the entire region.

It must be stated that the above is a simplification; the true situation is far more complex but the intent is to be brief, simple, yet sufficiently correct.


For further information on lag, please consult the following:

1)
If you do not see the Advanced menu, press Ctrl-Alt-D to enable it.

fs_link_replace_507.png - created

fs_linkreplace_new

$
0
0

Replace Inventory Links

For example, say you have a few links to a hair item. You then at some point rez out that hair item to edit it, then take it back into inventory. The item will have a new UUID, so all your links to that item will be broken. To fix those links, proceed as follows:

  • locate one of the links in your inventory
  • right click the link and select Replace Links
  • a window like the one to the right will open, showing the name of the link, and how many links like it are in your inventory
  • now locate in your inventory, the item you wish these to link to (using the example above, the hair item which you rezzed out)
  • drag this item into the box labeled New
  • click on Start.

NOTE: This function is handy if you also have broken links in inventory that you wish to repair.



See this page for documentation on Firestorm 5.0.1 (52150) and earlier.

archive:fs_linkreplace_fs501 - created

$
0
0

Replace Inventory Links

For example, say you have a few links to a hair item. You then at some point rez out that hair item to edit it, then take it back into inventory. The item will have a new UUID, so all your links to that item will be broken. To fix those links, proceed as follows:

  • locate one of the links in your inventory
  • right click the link and select Replace Links
  • a window like the one to the right will open, showing the name of the link, and how many links like it are in your inventory
  • now locate in your inventory, the item you wish these to link to (using the example above, the hair item which you rezzed out)
  • drag this item into the box labeled Target
  • click on Start.

NOTE: This function is handy if you also have broken links in inventory that you wish to repair.

Viewing all 5258 articles
Browse latest View live


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