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

fs_518_prerelease

$
0
0

Firestorm 5.1.8 Prerelease

Changed Wiki Pages

The pages below have been updated to reflect some of the changes since Firestorm 5.1.7. Please do not bookmark them, as they will disappear once 5.1.x goes to public release.

Preferences

RestrainedLove API: RLV v3.2.1 / RLVa v2.2.0

Other changes and updates

Merged up to Linden Lab Version 5.1.7.517973
Release Notes for v5.1.7 (517973) - Second Life Viewer Released on July 30, 2018. http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/5.1.7.517973

The Maintenance: Quinquina Release includes various sundry other bug fixes.

Chromium Embedded Framework (CEF) Dullahan updated:

  • Dullahan: 1.1.1080
  • CEF: 3.3325.1750.gaabe4c4.513446
  • Chrome: 65.0.3325.146
  • Page of test URLs for Dullahan that are more complete and more robust. With the Developer Menu enabled (Ctrl Alt Q) press Ctrl+Shift+Z then the Home page button.

FMOD Studio 1.10.04

KDU updated to v7.10.4.

Voice Update: Vivox Version 4.9.0002.27586 (Mac and Windows)
Voice Opensim not updated 4.6.0017.22050 (Mac and Windows)
Linux uses native voice files Version: Vivox 3.2.0002.10426

JIRA Bug Fixes

FIRE-22709 - [OpenSim] Local voice chat broken on OpenSim

JIRA Improvements

FIRE-22675 - Preference Setting - Sim Crossings - Bogus Avatar Movement

JIRA New Features

FIRE-5993 - timed land ban


archive:fs_517_prerelease - ↷ Page moved from fs_517_prerelease to archive:fs_517_prerelease

$
0
0

Firestorm 5.1.7 Prerelease

Changed Wiki Pages

The pages below have been updated to reflect some of the changes since Firestorm 5.0.11. Please do not bookmark them, as they will disappear once 5.1.7 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 remain visible.

Avatar Complexity

  • Avatar Menu - Appearance (Ctrl+O) - Wearing tab: Shows the rendering weight of each worn attachment. Avatar Complexity
  • Avatar Menu - Appearance (Ctrl+O) - Wearing tab: Added the ability to use double-click to remove wearables and temporary attachments.
  • Avatar Menu - Appearance (Ctrl+O) - Outfits tab: Added the ability to use double-click to add/remove.

Preferences

  • Firestorm - Build 1: Script Editor Font. Allows you to select the name and size of the font used in the LSL script editor.
  • Firestorm - Uploads: Reset default folders button resets all upload folders to default destinations.
  • User Interface - 2D Overlay: Prevent statistics window from gaining focus. If enabled, the statistics window will never receive focus when another window is closed. Actions such as changing graph layout for items are still possible when enabled.
  • Move & View - Movement: Allows you to select Predict or Stop behavior.
    This setting affects how the viewer will behave when approaching a region crossing. Two options are possible. The first, being “predict” (and the default behavior), will cause the viewer to try and predict movement into the region ahead whilst using bogus movement until the session with the region ahead has been setup. The second option here is “stop”. The “stop” option does what its name implies; movement at the region crossing will cease until the session with the region ahead is setup and data is received (such as a position update).
    In certain scenarios, some may prefer the “stop” behavior (e.g. some aviators, people who like to race land vehicles), whilst some may prefer the default behavior (predict).
    Note that the “stop” setting is experimental code and a workaround pending server side changes. It is not a fix. If you find yourself in a position where the experimental code is not ideal, simply revert the change back to “predict”. Setting this option does not require a viewer restart.
    For more information about how the experimental code works, see https://jira.phoenixviewer.com/browse/FIRE-21915.

People - Nearby (Radar)

  • Nearby (Radar): Render Settings. Right-click any avatar gives fly-out menu and offers options to Render Normally (default), Do Not Render, Render Fully.

About Land - Access Tab

  • About Land - Access: Timed ban: Added the ability to ban residents from a parcel for a specific amount of time (minimum 1 hour, maximum 8766 hours (approximately 1 year)). Select the number of hours when the window opens and press OK. Otherwise, leave it at 0 to permaban.

Alex Ivy for Linux

Firestorm Team is pleased to be able to offer Alex Ivy for Linux. All this penguin goodness is brought to you by the amazing efforts of the developers, QA and support team members. Awesome job! Testers are asked to give this an extra good workout. (see Other changes and updates below for backstory)

RestrainedLove API: RLV v3.2.1 / RLVa v2.2.0

Other changes and updates

Merged up to Linden Lab Version 5.1.6.516459
Release Notes for v5.1.6 (516459) - Second Life Viewer Released on June 15, 2018. http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/5.1.6.516459

The Maintenance: Palinka Release includes more effective group information, shutterbug solutions, various XUI and LOD cleanup work, URLS handled with care, more crash fixes and various sundry other bug fixes.

Merged up to Linden Lab Version 5.1.5.515811
Release Notes for v5.1.5 (515811) - Second Life Viewer Released on May 31, 2018. http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/5.1.5.515811

The Love Me Render Viewer Release represents a collection of work on the rendering pipeline, many in response to bugs and feature requests filed over the years. We always appreciate the diligent help of our residents in finding, filing, and sometimes fixing these - and following along with the development efforts.

Merged up to Linden Lab Version 5.1.4.515016
Release Notes for v5.1.4 (515016) - Second Life Viewer Released on May 07, 2018. http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/5.1.4.515016

Maintenance: Ouzo is here to quench your thirst.

  • Ouzo is a dry anise-flavoured aperitif that is widely consumed in Greece, Cyprus and Lebanon. Its taste is similar to other anise liquors like pastis and sambuca. Other spirits of the region may or may not include anise: arak, rakı, and mastika.
  • This bottle of Maintenance fixes brings you a large helping of crash fixes, a serious side of bug fixes, and a splash of improvements. Bottoms up!

Merged up to Linden Lab Version 5.1.3.513644
Release Notes for v5.1.3 (513644) - Second Life Viewer March 27, 2018
http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Release/5.1.3.513644

  • This release of the Viewer pulls in a raft of updates to the built in media support that were not quite ready to be integrated when the 64 bit Viewer (Alex Ivy) was released.
    It is comprised of various fixes, updates, security patches and improvements for CEF (Chromium Embedded Framework) that is the basis for the built in web browser and VLC that provides support for video media playback.
    In addition fixes are included to Dullahan (the third party library that uses CEF) as well as all the media plugin code itself.
    As per the Alex Ivy 64 bit viewer, there is no Linux version.
  • Cookies
    The option to not accept cookies has been removed due to complexities of not doing so in the in-viewer browser. For a more controlled cookie experience, an external full-featured browser may be better.

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.1080
  • CEF: 3.3325.1750.gaabe4c4.513446
  • Chrome: 65.0.3325.146
  • Page of test URLs for Dullahan that are more complete and more robust. With the Developer Menu enabled (Ctrl Alt Q) press Ctrl+Shift+Z then the Home page button.

FMOD Studio 1.10.04

KDU updated to v7.10.4.

Voice Update: Vivox Version 4.9.0002.27586 (Mac and Windows)
Voice Opensim not updated 4.6.0017.22050 (Mac and Windows)
Linux uses native voice files Version: Vivox 3.2.0002.10426

JIRA Bug Fixes

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

FIRE-22438 - tp2 <own name> crashes the viewer

FIRE-18130 - Setting llSetTextureAnim to FALSE while enabling llSetPrimMediaParams causes the animation to clear improperly

FIRE-20413 - [Windows 32bit] CEF Plugin error with certain videos

FIRE-22430 - SLVoice version 4.9 will not manually recycle

FIRE-22441 - Nearby Chat icons moved, vintage skin

FIRE-22478 - Inventory Elements Tooltip missing

FIRE-22483 - [BUG-216123] [MAINT-8552] Secure map links are not parsing https://maps.secondlife.com/secondlife/

FIRE-22522 - Dirty install error on mac OSStatus error -67062

FIRE-6825 - [MAINT-1421] [VWR-29484] [MAC] [LINUX] Show info - Show memory (usage) doesn't work on mac build 28570

FIRE-22204 - Firestorm Crash when enabling Physics view via eye icon for sub-mesh in OpenSim

FIRE-22278 - [OpenSim] Changing Skew or Revolutions of a Prim causes Prim to vanish or crash

FIRE-22509 - Received items shown in lower half of inventory window is empty

FIRE-22513 - Unable to add a local texture after commit 55111 - either silently fails or viewer crashes

FIRE-22514 - Metaharper skin chiclets too high

FIRE-22530 - Copy paste chat issue

FIRE-22564 - “Route llOwnerSay to scipt debug window” shows incorrect state at login screen

FIRE-22568 - Group Experiences tab seems to lack a correct help ID

FIRE-22578 - Italian System Info does not include viewer settings

FIRE-22579 - [Linux] Viewer window resizing failure

FIRE-20948 - [BUG-139124] [MAINT-7847] The presence of certain Avatars stops local specular textures from “sticking”. Yes really.

FIRE-22573 - No automatically Refreshing of the Windlight settings when someone else on the same Regions is changing them.

FIRE-22618 - Spanish System Info does not include RLVa setting

FIRE-9008 - [VINTAGE] Marketplace inventory tab scrollbar doesn't work properly

FIRE-20259 - [RLVa] @camtextures crashes viewer when cleared when webprims are active and visible

FIRE-20526 - Outfit snapshot upload closes inventory

FIRE-20669 - “Requires restart” text missing

FIRE-21571 - @camavdist rlv command is missing or broken

FIRE-21576 - Ability to get free from ANY locking restraint

FIRE-21863 - Circumventing RLVTP restrictions

FIRE-22379 - Firestorm crashes when “rebooting” nanite system controller.

FIRE-22414 - 3 crashes today when trying to close an inventory window

FIRE-22506 - [VINTAGE] Very slow typing in Inventory search field

FIRE-22577 - Textures corruption

FIRE-22625 - S32 debug settings and associated spinners glitch if value exceeds 16777216

FIRE-22640 - [BUG-216393] [MAINT-8724] Firestorm crashes on launch on MacOS 10.14 Beta

FIRE-22683 - Windlight Name Problems

FIRE-22709 - [OpenSim] Local voice chat broken on OpenSim

JIRA Improvements

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

FIRE-22484 - Appearance - Outfits - possible to add/remove attachments with double click?

FIRE-22507 - Windlight Submission - Water - Lassies Clearwater

FIRE-22521 - Offer the complexity render options (always/normal/never) in the nearby people/radar right click menu

FIRE-22538 - Add function to reset the upload folder to default

FIRE-22571 - Add chat feedback to Always Run shortcut

FIRE-13930 - Show growl notification when receiving tp offer

FIRE-14924 - [PATCH] [LINUX] Mesh Uploads, save last folder information.

FIRE-17898 - [PATCH] Prefs search doesn't find RLV immediately

FIRE-22136 - [PATCH] Improved Notification Colors for Starlight / Starlight CUI Skin

FIRE-22292 - Inspect Objects window - make columns optional, and all columns resizeable

FIRE-22372 - Debugs which should not persist

FIRE-22627 - Move the “teleport home” and “set home to here” buttons a little farther apart.

FIRE-22675 - Preference Setting - Sim Crossings - Bogus Avatar Movement

JIRA New Features

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

FIRE-5993 - timed land ban

archive:fs_511_prerelease - created

$
0
0

**Firestorm 5.0.11 Preview**

Changed Wiki Pages

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

Editing

  • Object tab: Preview menu and comparative table showing default values for the LL viewer, Firestorm, and then for your LOD setting.
  • Features tab: The eye icon. Use this to avoid the “can't rez here” simulator message. The physics shape view lets you see how the simulator sees the items when it is trying to work out where to place things, where you walk and how things collide (displays in blue).
  • Menus: Build Menu - Options - Show Physics Shape When Editing (same as eye icon on Features Tab).

Inventory

  • Inventory window: Explains the Elements information on currently selected folder. Elements includes the numbers of inventory items and folders. For example 12/4 Elements is 12 items and 4 folders.
    Additionally, for total inventory, hover your mouse over Elements for a breakdown of items and folders.
    Folder labels now update when item count changes. (update)
    Received Items folder now shows Elements count. (update)

Inspect

  • Inspect: Added Total Stats summary and additional column for VRAM.

Right Click Menu

  • Right Click Menu: Reset Mesh LOD. Added option to “reset” broken meshes worn on avatars due to stuck LOD.

Preferences

  • Chat tab: Report ignored conference chats in nearby chat now includes URI link to the inviter.
  • Privacy tab: Added option to show/hide invitations to already joined groups.
  • User Interface tab: Remap shortcuts already used by Linux. Shortcuts already used by Linux (Ctrl-Alt-Fn) will be remapped to use Ctrl-Shift instead.
  • Move & View tab: Added option to disable visual hints when editing shape. (update)
  • Chat Tab: Command Lines added: /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. (update)
  • User Interface tab: Celestia medium redux font added. Note: does not include bold and italics. (update)

People - Nearby (Radar)

  • People: Added same parcel indicator.

Avatar Physics

  • Avatar Physics: Avatar physics no longer bugs out at very low and very high FPS. A long awaited fix to have you wiggling and jiggling at your very best.

Updates and Resolved JIRA issues

Snapshot

Snapshot: Posting snapshot to Twitter. Increased total length of Twitter posts up to 280 characters and the photo no longer takes up characters.

OpenSim-specific

  • Added support for Gloebits currency (see https://www.gloebit.com/about-gloebit).
  • Added the new OpenSim OSSL functions to script library.
  • Fixed inventory fetching stalls on OpenSim.
  • Littlefield Grid crash fix. (update)

Translation

  • Translation updates for German, Polish and Japanese.

Other

64-bit Beta Viewer with Havok Libraries (Windows and Mac only)

Firestorm was the first viewer to bring you the extra stability and memory profile of the 64-bit viewer, but until now that has been at the expense of one feature, the Havok libraries supplied by Linden Lab. As a result of the work that the Lab are doing on their Alex Ivy 64-bit project, we are now able to bring you the long-anticipated, Havok-enabled 64-bit Firestorm, once again restoring all the functionality of the 32-bit viewer but keeping the stability and speed of the 64-bit viewer.

Many of you will not have noticed anything missing, but for builders and those using features such as pathfinding, the lack of Havok limited certain functions. The most notable area was mesh upload. Firestorm never lost the ability to upload mesh (contrary to many incorrect rumors) but what Havok does provide is a few special functions that allow a mesh creator to optimize the physics shape of their works. This has now been fully restored to the 64-bit viewer.

To celebrate this, one of our developers has created a special physics-shape–viewing extension to the edit dialog. For creators, this means that you can now see exactly how your mesh will react to people walking and colliding with it, while for other users, it means you can check whether a physics shape exists before trying to rez an object, saving those “cannot rez here” messages and lost inventory.

Firestorm Developer, Beq Janus - Beq's Other Blog http://beqsother.blogspot.ca/2017/10/coming-to-firestorm-soon-couple-of-new.html

Buy Beq's physics shape test pack (freebie) on Marketplace. https://marketplace.secondlife.com/p/Firestorm-Beta-Tester-kit/13140762

Physics Explained http://beqsother.blogspot.ca/2017/10/blue-sky-thinking-physics-view-explained.html

Resolved JIRAs - Fix Version 5.0.8+

Copy and paste this link in your external browser to see a complete list of the resolved JIRA issues since last release. https://jira.phoenixviewer.com/issues/?filter=14691

Summary of issues:

Bug

  • FIRE-21000 - Cannot upload meshes rigged to attach points in (works in 4.7.9)
  • FIRE-21071 - [Mac Only?] Group profile - Crashing when creating an admin role
  • FIRE-21236 - Help Menu - Check Grid Status doesn't open using external browser
  • FIRE-21261 - Brackets around system messages not shown when not using V1-style chat headers
  • FIRE-21273 - “MAINT-389 No way to wear an outfit from Library besides drag-n-drop” doesn't work on Firestorm
  • FIRE-21298 - Usernames in emotes of the V3 header of the chat window
  • FIRE-21301 - [OpenSim] Syntax highlight missing
  • FIRE-21306 - Firestorm 5.0.7 (52912) broken windlight using advanced lighting
  • FIRE-21308 - Firestorm Crashing 100% reproducable
  • FIRE-21318 - [BUG-100886] [MAINT-7541] We were unable to decode the file storing your saved login credentials…
  • FIRE-21321 - Option to disable use of built-in transcript viewer does not work
  • FIRE-21323 - Crashing Viewer while toggling LanguageIsPublic
  • FIRE-21330 - Build Animation: Cannot extend frame loop slider past 100 frames.
  • FIRE-21364 - Recent commits break Linux build process
  • FIRE-21369 - [BUG-134022] [MAINT-7607] [Crash] Appearance causes crashes in 52912
  • FIRE-21378 - Query status secondlifegrid.net for latest news at login reports “Invalid Message Format”
  • FIRE-21394 - [BUG-133986] [MAINT-7581] Closing the 'Replace links' floater crashes the viewer if a replace is in progress
  • FIRE-21396 - Area Search saving query
  • FIRE-21408 - FPS drop when opening the world map and zooming out
  • FIRE-21495 - Web Certificate for https://www.firestormviewer.org is expired
  • FIRE-21595 - [BUG-134193] [MAINT-7625] “Confirm before deleting filtered items” notification appears when deleting empty folder
  • FIRE-21632 - unwearing an item does not remove it from what is visible in the worn tab in one's inventory
  • FIRE-4276 - [BUG-9282] [MAINT-5226] All sounds, including UI sounds, stutter and repeat multiple times when on a region that has a large number of sound sources - “LLAudioData::load: Not able to allocate a new audio buffer, aborting.”
  • FIRE-5939 - Deleted gestures are not cleared from the desture panel
  • FIRE-6955 - Line numbers in script editor are not changing to semi-transparent, when window is unselected
  • FIRE-14101 - Intermittent broken LOD(MESH) on extreme zoom out/in
  • FIRE-16245 - [BUG-9367] [MAINT-5261] The “Ping Interpolate the object position” seems to no longer work
  • FIRE-16829 - [BUG-20057] MAINT-6512] [AMD] Visual Artifacts with ALM enabled on AMD graphics
  • FIRE-18014 - Inventory Window Stays auto of focus after object/folder drop
  • FIRE-20289 - [OpenSim] Unable to completely load inventory in OpenSimulator 0.8.2.1
  • FIRE-20441 - Skin Glitches Underwater
  • FIRE-20553 - Show received items folder in normal inventory bug
  • FIRE-21263 - Show Highlight option is not saved after closing Edit window REVERTED TO ORIGINAL BEHAVIOR (update)
  • FIRE-21292 - [MAC 10.12.5 and 10.13] Gives error message on Mac at quit “Firestorm quit unexpectedly”
  • FIRE-21375 - [Linux] Materials Textures do not synchronize!
  • FIRE-21376 - [Opensim] User reports unable to load inventory past 850 items
  • FIRE-21419 - [BUG-134021] [MAINT-7611] if a group name starts with a space then its not opening the transscript file on hard disk
  • FIRE-21489 - Hover Avatar height resets on every login or teleport
  • FIRE-21596 - helper-uri fails to update on HG teleport
  • FIRE-21630 - [BUG-202664] [MAINT-8033] Inventory trash can count is off
  • FIRE-21739 - [BUG-139222] [MAINT-7906] Inventory jumps when detaching worn items in appearance panel
  • FIRE-21754 - [BUG-139241] [MAINT-7910] MAINT-6770 regressed in Moonshine merge - Appearance floater's chosen tab is not remembered between sessions.
  • FIRE-21755 - Position, Size and Rotation changes don't affect prim
  • FIRE-21757 - Crash in specific regions, facing specific directions
  • FIRE-21772 - Unable to edit prim type after selecting someone else's mesh objects
  • FIRE-21781 - Experience_Events.xml excessively large causes login issues
  • FIRE-21785 - Taper does not stop when reaching 1.0 when using up arrow
  • FIRE-21787 - Reproducible crash on 5.0.9 beta
  • FIRE-21807 - When opening a voice call no sound plays to alert of the call
  • FIRE-21887 - when ever i want to make a payment to someone i search in the friends list, when i click on their name i get someone else profile and pay the wrong person this is serious
  • FIRE-22119 - [BUG-202858] 5.0.11.53579 Inventory Counts don't update until clicking the folder name (update)
  • FIRE-21948 - the new (Item/Folder) display doesn't work in the Received Items Display (update)
  • FIRE-19720 - Crash when teleporting on Littlefield grid - LLVOSurfacePatch dirtyGeom (update)

Improvement

  • FIRE-14599 - Inventory - Quick Jump from Recent or Worn to Inventory Folder
  • FIRE-17376 - Set a custom application name for FMOD
  • FIRE-21069 - New Graphic for Check Mark MetaHarper Modern (BlackGlass) (Graphic Preset Switcher)
  • FIRE-21241 - Profiles: Add the 'Copy URI' Gear Button to the Bottom of our Own Profiles
  • FIRE-21385 - Add inviter name/UUID to ad-hoc ignored messages
  • FIRE-21617 - Vignette not Saved in preset
  • FIRE-5913 - [PHOENIX] Selecting multiple active gestures with 1 or more inactive ones at the same time does not produce (De)activate right click option.
  • FIRE-20139 - Thai unicode chars are not displayed correctly (rectangles) on Win 10 even after installing Thai supplemental fonts and with Office 2016 installed.
  • FIRE-20385 - Can Join Group When Already In It
  • FIRE-21504 - [PATCH] Change the rezplat object type to Box
  • FIRE-21546 - Docked Windows Poof/minimize On New Group Session
  • FIRE-21625 - [LINUX] bad shortcuts Ctrl.+Alt+F1 and Ctrl.+Alt+T
  • FIRE-21803 - Add a check box under Preferences/Notifications/World/Notify me when I spend or get L$, that would say “allow payment messages”.
  • FIRE-22110 - Add chat command for “Hover height” setting (update)
  • FIRE-21936 - Option to remove preview thumbnail images of avatar in appearance mode (update)
  • FIRE-22130 - RenderVolumeLODFactor values and warnings (update)

New Feature

  • FIRE-21445 - Force display specific LOD
  • FIRE-21587 - [OpenSim] Use SimulatorFeaturesRequest OpenSimExtras map currency and currency-base-uri settings
  • FIRE-21745 - [OpenSim] Syntax Highlight missing osGetSimulatorMemoryKB

Translation

  • FIRE-21313 - Translation failure in german version in Vintage Skin
  • FIRE-21614 - Update Japanese translation

Support Request

  • FIRE-21529 - bin_conf.dat corrupts after first log in following clean install

fs_install_crash - [By Operating System]

$
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, chances are good that some part of 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 7, 8.1, and 10: press [Win] + [R] and type %localappdata%, then look for the Firestorm folder. (This method avoids having to un-hide folders.)
    • Mac: ~/Library/Caches/Firestorm
    • linux: ~/.firestorm/cache or ~/.firestorm_x64/cache
  • Delete the cache folder you located.
  • Log back into SL, to a quiet region (try Hippo Hollow, Aich or Hatton). Allow your inventory and cache 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

  • 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

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 | grep not\ found

This will spit out a list of libraries that are not found on your system. You will need to install these with your package manager.

Viewer wont start due to an error with libstdc++

On the odd occasion, some have reported an error like the one below:

bin/do-not-directly-run-firestorm-bin: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.22' not found (required by bin/do-not-directly-run-firestorm-bin)

If you see this error, it means your distributions libstdc++ library isn't compatible (possibly due to age of the library).

If the viewer will not start because of this specific error, try downloading this library, and place it in the lib directory under the viewer install directory.

Note, this solution is to be considered a workaround. Ideally, you should consider investigating matters such as being up to date with operating system updates for your distribution etc.

For popular distributions such as Ubuntu, please ensure you are using a current distribution release. For Ubuntu systems (Ubuntu, Kubuntu etc), please visit https://wiki.ubuntu.com/Releases to check the status of your distribution. If you are using a distribution that is end of life, or, on the verge of being end of life, please consider updating to a current release.

bluephoenixemperor - ↷ Page moved and renamed from sg_shared:bluephoenixemperor_aka_scc-9779 ...

$
0
0

bluephoenixemperor

2018-08-04

Person had been repeatedly (e.g, day after day) soliciting for his star wars group in the Firestorm Gateway Roleplay group. I let it pass the first few times but after it got to be a near-daily routine I IMed him that it wasn't ok. His response was to more or less accuse me of being a Star Wars hater and say he was leaving the group and to log mid IM so he wouldn't have to talk to me about it:

In Group chat:
[17:41] SCC-9779 (bluephoenixemperor): hey if anyone in here is interested in joining up with a star wars clone trooper group then i.m me
[17:49] SCC-9779 (bluephoenixemperor): in the 551st we provide armor, fatigues, and weapons. as well as free housing and rp locations

In IM:
[18:34] Teresa Firelight: you have repeatedly and directly been soliciting for a specific group in the firestorm roleplay group. The ONLY people who are allowed to “solicit” in there are Firestorm RP partners. I have let it go cuz I thought it was a once off thing.. but it seems to be something you are doing quite frequently
[18:34] Teresa Firelight: this must stop
[18:35] SCC-9779 (bluephoenixemperor): will do
[18:35] SCC-9779 (bluephoenixemperor): im leaving the group so it works
[18:35] SCC-9779 (bluephoenixemperor): to many star wars haters
[18:36] Teresa Firelight: if your only reason for being is the firestore RP group is to solicit for a specific group, then yea it is a good idea for you to leave because soliciting is not allowed here
[18:36] SCC-9779 (bluephoenixemperor): oh no my reason was to find fellow sci fi rpers who want free stuff
[18:37] Teresa Firelight: we encourage RP and such here.. but not the soliciting of people to a specific group at a specific site
[18:38] Teresa Firelight: if you wanted to have people join you in a RP somewhere on the scifi portal grounds, that would be fine. But asking them to join a specific group repeated rather than RPing with you on firestorm.. well that is a problem
[18:38] SCC-9779 (bluephoenixemperor): User not online - message will be stored and delivered later.

http_fetching_issues

$
0
0

Quite a number of issues are related to HTTP fetching, including some unexpected ones:

  • all avatars except your own appear grey
  • in-world objects remain grey, or they repeatedly go blurry and focus
  • mesh objects do not rez in
  • your avatar bakes, then goes blurry, then rebakes, etc
  • inventory is stubborn to load fully
  • problems with voice
  • music/video doesn't work or is intermittent

All of these issues can boil down to one common cause: problems successfully using HTTP to fetch textures and avatar bakes from SL servers.

Things to Try

Please try these things one at a time. If one fixes your problems, stop there, don't continue to the next.

  • If you are wearing any HUD, including Catwa, WowMeh, Toodledeedoo, The Shops/The Mesh Project/TMP, Maitreya or similar, detach it. These (and a few other high texture HUDs) are known to cause in-world textures to rez then blur repeatedly.
  • Preferences → Graphics -> Hardware Settings→ Viewer Texture Memory Buffer:
    • 32bit versions only. This setting is hard limited to a maximum of 512MB. Try with a setting of 384. If you reduced this yourself as a result of the "Textures Discarded" error, then be aware that increasing this value will likely cause that problem to return.
    • 64bit versions only. This setting is hard limited based on the VRAM available with your graphics card. It is recommended you increase the slider to use the maximum available to prevent texture thrashing.
      • GPU 1GB = up to 768MB
      • GPU 2GB+ = up to 1024MB
      • GPU 4GB+ = up to 2048MB
  • Other objects can also cause this problem.
    • Step 1: Go to an empty region such as Cyclops or Aich, and see if it stops. If it stops, then one or more objects at your previous location may be overloading your graphics.
    • Step 2: If it has continued, then also remove ALL attachments (everything in Inventory > Current Outfit folder with a box icon, except for the Firestorm bridge). If removing your attachments fixes the problem, one or more of them may be overloading your graphics.
  • Power down your router and/or modem. This generally means unplugging it from the power source and removing any batteries. Leave them disconnected for at least a full minute before reconnecting (and reinstalling batteries). Wait for them to complete the power up sequence, then reboot your computer.
  • If you don't have the Advanced menu enabled, enable it with Ctrl-Alt-D. Then, Advanced → Debug Settings. Type in TextureFetchConcurrency - set the value to 4, then close the Debug Settings window and relog.
  • Preferences → Graphics -> Hardware Settings→ Enable Lossy Texture Compression: Enabling this, and then restarting the viewer, will cause the viewer to compress textures while they are in Texture Memory, thus reducing the amount of memory each texture requires. This can help reduce or eliminate the constant re-blurring of textures. The caveat is that the compression is lossy, meaning some parts of the texture are simply lost, so overall texture quality might be reduced and may be noticeable especially along sharp edges.

Causes

As noted above, the problems are caused by the HTTP protocol - more specifically, it overwhelms some lower end routers. Many people find that HTTP makes rezzing MUCH faster; others instead, those with lower end routers, wireless ones in particular, have the issues described at the start.

If the fixes above work for you, then great. BUT we strongly recommend looking to upgrade to a better router. In particular, Belkin G series and the LinkSys WRT are two which are best avoided.

motd - [Event Messages of the Day.]

$
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 Rock Your Rack Registration
Rock Your Rack 2018 supporting the National Breast Cancer Foundation is now taking designer, Live Musicians, DJ's, Bloggers and Content Creator registrations for their October event! Click for more! https://rockyourrack.wordpress.com/about/designers/

MOTD: EVENT: Strides Parade of Homes in Second Life and Out Shop Cancer Registration
Calling all merchants and builders! Join with the American Cancer Society for the upcoming Parade of Homes and Out Shop Cancer events! Info at https://makingstridessecondlife.org/


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.

scripting_the_radar - capitalization

$
0
0

Scripting the Radar

The Firestorm radar can send information to scripted objects and/or attachements.

If you open the People panel (via the button, or the top menu bar→ Comm → People, then click the Gear icon, you can enable:

  • Report Enter Alerts to Scripts
  • Report Exit Alerts to Scripts

Tthese options are also in PreferencesChat -> Radar.

If either (or both) of these are enabled, the radar will send an avatar UUID to scripts, on chat channel -777777777, when an avatar enters the region you are currently in. If both options are enabled, then the behavior expands to include full radar range, 4096m.

The format of the string sent by the radar is:

number times called, avatar delta, [comma separated list of avatar UUIDs]
  • avatar delta indicates a change in the number of avatars with respect to the prior report - so 1 means an avatar entered the region, while -1 means one left.

Sample output (names and UUIDs replaced for obvious reasons):

[18:41] Avatar1 left the region.
[18:41] Test Radar: 10,-1,00000000-0000-0000-0000-000000000000
[18:41] Avatar2 entered the region (48.59 m).
[18:41] Test Radar: 11,1,00000000-0000-0000-0000-000000000000

It is also possible to have the radar output the current list of avatar by playing a very specific sound, the one with UUID: 76c78607-93f9-f55a-5238-e19b1a181389

Below is a very basic script that:

  • sets a listen on the radar chat channel, -777777777
  • listens for output on that channel, and reports anything received to the owner of the object containing the script
  • outputs the list of avatars in a region after a teleport
  • outputs the list of avatars in a region when the object is touched.

NOTE: when you use the sound trigger, the delta will report the total number of avatars, since the trigger does a full scan.

default
{
    state_entry()
    { 
        llListen(-777777777,"",NULL_KEY,"");
    }

    listen(integer channel, string name, key id, string message)
    {
        llOwnerSay(message);
    }

    changed(integer what)
    {
        if(what & CHANGED_REGION)
        {
            llTriggerSound("76c78607-93f9-f55a-5238-e19b1a181389", 1.0);
        }
    }
    
    touch_start(integer num_detected)
    {
        llTriggerSound("76c78607-93f9-f55a-5238-e19b1a181389", 1.0);
    }
}

fs_wearable_favorites

$
0
0

Favorite Wearables

<callout type="warning" icon="true">
include an image - taken using FS Grey skin \\ 
</callout>

The Favorite Wearables window allows you to list frequently used items, HUDs as an example, in an easily accessible location so that you can quickly attach and detach them as needed. This makes it more convenient to detach attachments you don't need or want to wear all the time due to script usage or increased texture memory usage, and saves you from digging around in your inventory when you want to add them.

To use the feature,

  • drag the toolbar button to your toolbar: Avatar Menu → Toolbar Buttons → Favorite Wearables, then click the button,
  • or open the window from Avatar Menu → Favorite Wearables.

Adding/deleting items from the window:

  • To add items, drag them from inventory into the window. Items added to this window create a link in the #Wearable Favorites folder in inventory.
  • To delete an item, select it and press the Trash icon. Note: this only deletes the link in the #Wearable Favorites folder, not the original item.

Use double-click to add or detach any item.

The window includes a search bar.

The menu options include:

  • Sort by name
  • Sort by date
  • Sort by type name (asset type)

firestorm_classes - old revision restored (2018/07/16 10:16)

$
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.

Unscheduled classes may also be held on an impromptu basis. If this happens, a notice will be sent in Firestorm Support English. secondlife:///app/group/3a1be8d4-01f3-bc1a-2703-442f0cc8f2dd/about

*All times SLT*

Monday 16th July 1pm – 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
Tuesday 17th July 10am – Introduction to Firestorm and the Wiki
This class gives you an overview of the Firestorm Viewer and of our greatest informational resource, our Wiki, including search tips.
FS
Wednesday 18th July 11am – Clean Install
Learn how to correctly and quickly perform this most fundamental and important of tasks. Recommended to take Settings Backup class first.
FS
Thursday 19th July 1pm – Menus 1 (TEXT ONLY)
We will be covering the menus on the top bar, from Avatar through Help.
FS
Friday 20th July 2pm – Menus 2
We will cover the Advanced and Develop menus in the top bar.
FS
Saturday 21st July 11am – Odds & Ends 1
This class covers some of Firestorm's handiest features, like Inventory, Radar, and some hard-to-find gems.
FS
Sunday 22nd July 3pm – Odds & Ends 2
Learn about fun and useful items like how to use Autocorrect, using the Command Line for a number of tools, and more.
FS
Monday 23rd July 1pm – Preferences Set 1 (TEXT ONLY)
We will cover some of the Firestorm preferences (General, Chat, Privacy), based on our current release.
FS
Tuesday 24th July 9am – Preferences Set 2
We will cover some of the Firestorm preferences (Graphics, Network & Cache), based on our current release.
FS
Wednesday 25th July 10am – Preferences Set 3
We will cover some of the Firestorm preferences (Move & View, Advanced, Firestorm), based on our current release.
FS
1pm – QuickPrefs Customization + Lag
Two mini-classes in one. One discusses the causes of lag in SL. The other explains how to customize your Quick Preferences.
FS
Thursday 26th July 1pm – Preferences Set 4 (TEXT ONLY)
We will cover some of the Firestorm preferences (Colors, Skins, Notifications, User Interface, Sounds and Media).
FS
Sunday 29th July 1pm – Reporting Bugs, Requesting Features
Learn how to communicate effectively with our devs to make the changes to Firestorm you want or need.
FS
3pm – Avatar Complexity and Graphics Presets
Learn how to boost performance with av complexity and improve usability with the presets.
FS
Monday 30th July 1pm – Firestorm Skins (TEXT ONLY)
This class covers the differences among Firestorm's many skin options, including the Vintage Classic and Colorable User Interface skins.
FS
Tuesday 31st July 11am – 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
Wednesday 1st Aug 1pm – Basic Troubleshooting
An introduction to basic methods to start locating problems. Focused on Firestorm but some parts are non-viewer-specific.
FS
Thursday 2nd Aug 1pm – Backing up Settings and Logs (TEXT ONLY)
This class covers how to save your settings and chat logs on your computer. Recommended to take this before the Clean Install class.
FS

start

$
0
0

Firestorm Documentation

Firestorm Gateway - For New Residents

Joining Second Life

You can join SecondLife via the web page given here:

If you want to invite friends to join, then please do share the link above with them.

The Firestorm Gateway

The Team

In-World Locations

We also offer classes on how to use the viewer. See this page for the schedule and in-world locations.

Getting Help

Please refer to this page for the many ways in which you can get help with using Firestorm.


support_locations

fs_clean_install - [Step 7: Install Firestorm]

$
0
0

Full Clean Install of Firestorm

If you are attempting to update from a blocked version of Firestorm, refer to this page.

The following explains how to do a proper clean install - which is more than simply removing the viewer and reinstalling it. You may need to follow this procedure if you have problems.

Before You Begin

Step 1: Get the Installer

For the current release, go to the Downloads page.
For any previous supported version, go to the Older Downloads page.

If you save chat transcripts, they are by default saved in your per-account settings folder (named for your avatar). Before you delete that folder (below), you will need to identify the chat files and move them. See here for steps to relocate your chat transcripts. This only needs to be done once if you then backup your settings. But you must log in on each account (i.e., alts) to save that account's chat files.

As a just-in-case measure for any situation, and to make upgrading or downgrading your viewer much easier, make a backup of your settings. It's a good idea to make a backup right before upgrading, downgrading or otherwise wiping settings so that the backup is current (teleport history, contact sets, etc. can change dynamically). You must log in on each account (i.e., alts) in order to back up that account's settings.

Remove Your Current Install

Step 5: Delete Settings

REMINDER: If you want to save chat transcripts and or settings, make sure you do Steps 1 and 2 before deleting your settings.

Firestorm settings can become corrupt, particularly if you recently crashed; the files may not save completely, so important information can become “scrambled”. And when installing a different version of the viewer, using settings from the previously installed version may cause undesirable behavior in the viewer.

Here is how to remove the old settings:

Method 1: If you are able to launch Firestorm

  • Launch the viewer but do not log in.
  • Click the Viewer menu at the top, choose Preferences, then Network & Files, then Directories.
  • Click the Open Settings Folder button.
  • Close the viewer.
  • In the file window, navigate up one folder, to the Firestorm* folder. If you see a folder called user_settings and one or more named for your avatars, you're in the right place.
  • Select everything in that Firestorm folder and delete it.

*Note that the Firestorm folder name may differ slightly.

Note also that if you have both a 32-bit and 64-bit version installed, you will only be deleting settings for the version that you launched at the beginning of this step. You would have to repeat this step if you want to delete settings for the other version that's still installed.

Method 2: If you are *unable* to launch Firestorm

You will need to use a file manager (like Windows Explorer for Windows system, Dolphin, the Mac Finder, or some such) to locate the settings folder. In its default location, the folder is hidden on most OSs. To find it, you will need to show hidden folders. Refer to this page to locate your settings folders.

Step 5: Clear Cache

Clearing cache should only be done when there is a problem with the cache, or when there is a significant change in the viewer that requires it (such as a change to the KDU render code). The viewer will automatically clear cache in such cases, but manual clearing may be quicker.

When downgrading, you should always clear the cache.

If you have to clear cache in order to use the viewer version you are about to install, please see this page.

Step 6: Remove Application

For Windows

Ideally, use the Programs & Features Control Panel [Win7, Win8.1, Win10], or Add/Remove Programs Control Panel to remove the Firestorm application. If you have a Firestorm folder in your Start Menu, there may be an Uninstall link there (32-bit Firestorm only).

For Mac

Navigate to Applications and trash the Firestorm App.

For linux

The Firestorm install directory will be wherever you extracted the download archive. Typically this will be in your home directory somewhere, such as ~/Phoenix-Firestorm_*. Delete this directory and everything inside it.

If you used the install script as root, look in your /opt directory. You will need to su root or sudo rm to delete the firestorm directory there.

Install the New Version

Step 7: Install Firestorm

Having done all those steps, you may now install Firestorm. Installing Firestorm is done in pretty much the same way as any other application on your computer.

For Windows

Run the downloaded installer.
The 32-bit installer will offer you the chance to change the destination directory.
The 64-bit installer shows the destination when you click the Options button.
The installer will create a shortcut icon on the desktop.

Note: Both installers offer you an option to start the viewer when it's done, and you should choose No.
Choosing Yes tends to cause problems for some people, especially if they restore during that session.
The shortcut is the preferred way to launch the viewer.

For Mac

Find the .dmg file you just downloaded and double-click it to mount it.
Then drag the Firestorm app icon into your Applications folder.
More detailed instructions can be found here

For linux

Extract the downloaded tar.bz2 or tar.xz into any directory and run the firestorm script inside that directory to launch it. You can optionally install by running the install script inside that directory. And you can optionally create a desktop launcher. Refer to the README files for more information.
If you are installing on a 64-bit Linux system, you will need to install some 32-bit libraries. Refer to this page for guidance on required compatibility libraries.
If you use the Nautilus File Manager and double clicking the firestorm launch script opens the script in an editor, you will need to modify how Nautilus handles scripts.

Flash Player

Go to Adobe Flash Player, select your operating system, then select the appropriate flash player.

Step 8: Log in

Once you have the viewer installed or reinstalled, you will want to make sure the viewer is operating correctly:

  • Log back into SL, to a quiet region (try Hippo Hollow, Aich or Hatton). Don't change any settings.
  • Test any functions that didn't work for you in the previous version that had been reported fixed.
  • If downgrading, test any functions that failed in the newer version.
  • If you needed to clear cache in Step 5 above, open your Inventory and wait for it to fully populate.

Step 9: Restore Settings

At this point, if the viewer is performing as it should, you can restore your settings and again relog. You must log in on each account (i.e., alts) to restore that account's settings.

Log back in to SL once again and confirm that the viewer is still performing as it should; then you can adjust any new or changed settings and then back those up.

Note that some settings are not restored, such as graphics. This is because the graphics settings could be incorrect and may cause problems.

fs_update_viewer - [Step 3: Install Firestorm] Added Gatekeeper note to Mac section.

$
0
0

Updating Your Viewer

If you are reverting to an earlier version than you currently have installed, or need to Clean Install as part of a Troubleshooting procedure, please click here.

Before continuing it is recommended that you Backup Settings. You may skip this step if you choose, however, if there is a problem during or after the update and you do not have a Back-Up then you could lose any changes you have made to your settings.

Updating your viewer need not be a daunting task. The Method explained below is for a straightforward Update. DO NOT follow this method if you are reverting to an earlier version.

Step 1: Get the Installer

For the current release, go to the Downloads page.

If you want to install a previous release, we recommend you use the steps in Clean Install

Step 2: Remove Application

For Windows

Ideally, use the Programs & Features Control Panel [Win7, Win8.1, Win10], or Add/Remove Programs Control Panel to remove the Firestorm application. If you have a Firestorm folder in your Start Menu, there may be an Uninstall link there (32-bit Firestorm only).

For Mac

Navigate to Applications and trash the Firestorm App.

For linux

The Firestorm install directory will be wherever you extracted the download archive. Typically this will be in your home directory somewhere, such as ~/Phoenix-Firestorm_*. Delete this directory and everything inside it.

If you used the install script as root, look in your /opt directory. You will need to su root or sudo rm to delete the firestorm directory there.

Step 3: Install Firestorm

Having done all those steps, you may now install Firestorm. Installing Firestorm is done in pretty much the same way as any other application on your computer.

For Windows

Run the downloaded installer. The 32-bit installer will offer you the chance to change the destination directory; the 64-bit installer shows the destination when you click the Options button.
The installer will create a shortcut icon on the desktop.

Note: The 32-bit installer offers you an option to start the viewer when it's done, and you should choose No. Choosing Yes tends to cause problems for some people, especially if they restore during that session. The shortcut is the preferred way to launch the viewer.

For Mac

Find the .dmg file you just downloaded and double-click it to mount it. Then drag the Firestorm app icon into your Applications folder. More detailed instructions can be found here

Note: Apple's Gatekeeper software may initially prevent your opening the viewer, depending on your Gatekeeper settings. If it does, there is a simple way to change it: See “How to open an app from a unidentified developer and exempt it from Gatekeeper” on this page. Once you have allowed Firestorm to open via this method, Gatekeeper will not flag it on subsequent launches (until you reinstall Firestorm again).

For linux

Extract the downloaded tar.bz2 or tar.xz into any directory and run the firestorm script inside that directory to launch it. You can optionally install by running the install script inside that directory. And you can optionally create a desktop launcher. Refer to the README files for more information.
If you are installing on a 64-bit Linux system, you will need to install some 32-bit libraries. Refer to this page for guidance on required compatibility libraries.
If you use the Nautilus File Manager and double clicking the firestorm launch script opens the script in an editor, you will need to modify how Nautilus handles scripts.

Flash Player

It must be noted that a different flash player is required for different versions of Firestorm. Version 4.7.7 and newer requires flash player for Opera and Chromium. Go here, select your operating system, then select the appropriate flash player.


Important Notes

  1. With a new version comes new code, new settings etc. Your settings can become corrupt and important information can become “scrambled”. When installing a different version of the viewer, using settings from the previously installed version may cause undesirable behavior in the viewer. If you experience issues after performing a straight update please Back-Up Your Settings and then Clear Your Settings.
  2. If you are experiencing issues after Updating via this Method you may be asked to perform a full Clean Install by our Support Team.
  3. If you have heavily modified settings and you are concerned that they may cause an issue on updating and/or restoring them you can take the precautionary measuring of Filing a Jira and attaching a zip file of your settings. *Please Note*: if taking this step please allow a minimum of 72 hours for this to be checked and responded to.

fs_old_version_blocks - [Those Who Cannot Update]

$
0
0
Be sure to back up your settings before upgrading your viewer and before your version is blocked!

Firestorm Blocks

Before folks start screaming, “You don’t care about us!”, please realize it is only because we care that we are developing Firestorm for you, and it is because we care that we are enforcing blocks. It is important for everyone to be on current releases that support the virtual world platform, its features and its capabilities.

Why Block Old Versions?

First, we are under pressure by Linden Lab to do this, and we can either do it ourselves or adopt LL’s update system, which allows them to do it instead. Either we update you or LL does, but either way, folks, updating is quite inevitable. The LL viewer enforces updates, as do most software applications with a fair grace period. Our grace period will leave three versions available: the current version and the two before that.

Second, updating is necessary in order to keep everyone enjoying the same shared experience. Second Life is not immersive if we see things drastically differently from one another. This is going to sound harsh, but in some respects if you are using versions that can only render avatars gray and/or versions without mesh, you might as well be—and perhaps should be—using a text based viewer.

Third, since we are a small team of volunteers, we are limited in our ability to provide support for old versions of the viewer.

Those Who Cannot Update

We recognize there are some users who cannot update to a current version due to their computer systems not being modern enough. For you there are still a few options. In some cases, people who believe they cannot run later versions of Firestorm are actually experiencing a fixable issue with which support can help; see the troubleshooting guide on our wiki. Contrary to popular belief, it only takes a computer around a US$300 value or so to run Firestorm. Firestorm does not require a “gamers” computer. Just something from the last five to six years will usually do. A decent video card will go a long way and often is all that is needed to dramatically improve performance for you.

You can download the latest version from here, there's even a link to currently available older versions. http://www.firestormviewer.org/downloads/

What Version We Are About to Block

Firestorm 5.0.1.52150 - August 14th, 2018


Adapted from this blog post.


fs_compiling_firestorm_64bit_debian_8 - [Establish your programming environment]

$
0
0

Building Firestorm in 64-bit Debian Jessie

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.

This procedure is used for building a 64-bit viewer on 64-bit Debian systems and was tested and verified on Debian 8.11. 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.

Install Required Tools

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

make | g++ | gdb | mercurial (for hg) | python2.7 | python-pip

sudo apt-get upgrade # to make sure all installed packages are current
sudo apt-get install --install-recommends make g++ gdb mercurial python2.7 python-pip

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

Do not install cmake from the repositories, Debian 8 comes with too old of a version, we will be downloading and installing a newer version from cmake's website.

Install Required Libraries

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

libGL.so (libgl1-mesa-dev) LibGLU.so (libglu1-mesa-dev) libstdc++.so.6 (libstdc++6)
libX11.so (libx11-dev) libxinerama-dev libxml2.so (libxml2-dev) libXrender.so (libxrender-dev)
sudo apt-get install --install-recommends libgl1-mesa-dev libglu1-mesa-dev libstdc++6 libx11-dev libxinerama-dev libxml2-dev libxrender-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 from 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 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..40000..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://hg.phoenixviewer.com/fs-build-variables/

Downloading cmake

Because Debian 8 comes with cmake version 3.0 and cmake 3.4 is the minimum needed to build the viewer, we will download the prebuilt version of cmake 3.6 (the last to support 32 bit targets on linux) and adding it to our path so it can be seen.

cd ~src
wget https://cmake.org/files/v3.6/cmake-3.6.0-Linux-x86_64.tar.gz
tar xf cmake-3.6.0-Linux-x86_64.tar.gz
PATH=$PATH:~/src/cmake-3.6.0-Linux-x86_64/bin/
export PATH

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
export AUTOBUILD_VARIABLES_FILE=$HOME/src/fs-build-variables/variables

Configuring the Viewer

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

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
autobuild configure -A 64 -c ReleaseFS_open -- --chan="MyBuild"

In the last example, the channel and resulting viewer name would be “Firestorm-MyBuild”.

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.

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-x86_64/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 author (preferred) or discuss on IRC.

Common Issues/Bugs/Glitches And Solutions

  • Missing libraries/applications/packages This may occur if you did not or could not install the listed packages. The packages do exist in the default Debian 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.

motd - [Event Messages of the Day.]

$
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 too fast, it was too 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 Rock Your Rack Registration
Rock Your Rack 2018 supporting the National Breast Cancer Foundation is now taking designer, Live Musicians, DJ's, Bloggers and Content Creator 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.

fs_compiling_firestorm

fs_compiling_firestorm_alexivy_debian_9 - Copying instructions from deb8 instructions and ...

$
0
0

Building Firestorm 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 viewer on 64-bit Debian systems and 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.

Install Required Tools

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

make | cmake | g++ | gdb | mercurial (for hg) | python2.7 | python-pip

sudo apt-get upgrade # to make sure all installed packages are current
sudo apt-get install --install-recommends make cmake g++ gdb mercurial python2.7 python-pip

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

Install Required Libraries

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

libGL.so (libgl1-mesa-dev) LibGLU.so (libglu1-mesa-dev) libstdc++.so.6 (libstdc++6)
libX11.so (libx11-dev) libxinerama-dev libxml2.so (libxml2-dev) libXrender.so (libxrender-dev)
sudo apt-get install --install-recommends libgl1-mesa-dev libglu1-mesa-dev libstdc++6 libx11-dev libxinerama-dev libxml2-dev libxrender-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 from 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 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..40000..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://hg.phoenixviewer.com/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
export AUTOBUILD_VARIABLES_FILE=$HOME/src/fs-build-variables/variables

Configuring the Viewer

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

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
autobuild configure -A 64 -c ReleaseFS_open -- --chan="MyBuild"

In the last example, the channel and resulting viewer name would be “Firestorm-MyBuild”.

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.

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-x86_64/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 author (preferred) or discuss on IRC.

Common Issues/Bugs/Glitches And Solutions

  • Missing libraries/applications/packages This may occur if you did not or could not install the listed packages. The packages do exist in the default Debian 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.

fs_height_offset

$
0
0

Height Adjustment

If you find that your feet are in the ground - or conversely that you are floating above the ground, you can adjust your height to get yourself back where you should be.

There are two ways to do this:

  • Method One: Use the newer Hover Height adjustment:
    • Either: Right click your avatar, select Appearance, then Hover Height. A window opens. Use the slider to adjust your height above the ground, then close the window.
    • Or: go to Quick Prefs > Hover Height, and adjust the slider there.

    • Note: RLVa is able to control this setting. If you find the setting changing apparently on its own, and you use RLV, one of your attachments may be adjusting the setting. Go to the RLVa menu → Debug → Show Debug Messages, and enable that setting. You will now see lots of “owner say” messages starting with “@….” One of them will most likely be @adjustheight:-0.2345=force or similar. This will tell you what attachment is controlling the setting.
  • Method Two:
    • Use the old setting in your Shape: Right click yourself, select Appearance → Edit Shape. In the Body tab, scroll down to Hover. Adjust the value till your feet are touching the ground. Save changes by clicking the Save button.
      Naturally, your shape must be moddable for this to work. 1)
    • Note: In general, it is best to leave this setting at 50 (the default value) since the setting has been deprecated. Values other than 50 sometimes cause erratic hover problems.
    • You can find some useful tips at I Was Floored: Frequently Asked Support Question.
1)
NOTE: Since this is a shape parameter and not a preference setting, it cannot be added to the QuickPrefs panel.
Viewing all 5258 articles
Browse latest View live


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