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

hud_issues_fr - created

July 3, 2018, 2:37 am
$
0
0
,

HUD Issues

HUDs (or Other Attachments) Are Not Working

Possible reasons why HUDs or other scripted attachments may stop working:

  • Disconnected during a teleport after restarting a region. See BUG-5034.
  • Script (running) state is lost when logged out during forced teleport. See BUG-41379.
  • There are griefing objects that can be rezzed on a region; anyone who goes there will have their HUDs and all other scripted attachments put into a non-running state. For instance: a HUD for a mesh body, and all the mesh body parts you are wearing, may be broken at the same time.

Note: While this issue most commonly affects HUDs, it can also affect any and all other scripted attachments you were wearing when the breakage happened.

There are a few things you can try to get the items working again.

First of all:

  • Go to Top Menu → Avatar → Avatar Health → Refresh Attachments. See if that fixes the items.
  • Relog then test the items again. That may be enough. If not, read on.

Things to try:

  • Check for location issues:
    • Make sure you are in a region that has scripts enabled.
    • Go to other regions and test the items there. This will rule out technical problems with the original region.
    • If you have RLV enabled, disable it (Preferences → Firestorm → Extras, top option), relog, then try again.

Stay in a script-enabled region to do all of the following. You do not have to do the following steps in this order, but the simplest and less drastic steps are listed first:

  • Attempt to get scripts running:
    • Try removing and reattaching the items.
    • If the items are modifiable, try resetting them or setting their scripts to running: Inventory, right-click the item → Edit, and while it is in Edit, go to Build menu → Scripts → Reset Scripts, or Build menu → Scripts→ Set Scripts to Running).
  • Check for interference:
    • Look in Inventory > Current Outfit folder, and see if you are wearing any HUDs you were not aware of. (Note: HUDS do not necessarily have “HUD” in the name.) This could include temporary “Experience” HUDS that you may not be aware were attached. (Temp HUDs have been known to freeze other HUDs on the same attachment point.)
    • Check that HUDs are not overlapping each other on the screen (and so preventing you from clicking).
  • Check for issues with attachment points:
    • If any HUDs are sharing the same HUD attachment point, try moving them to separate HUD attachment points:
      Inventory → Right-click → Detach from Yourself, then Inventory → Right-click → Attach to HUD, and choose an unused point.
    • Even if they are not sharing attachment points, try moving them to different attachment points.
  • Test basic functionality. To make sure that HUDs work for you at all, and work in your present location, do this:
    1. Rez a fresh cube
    2. Add the default script to it
    3. Take it into inventory
    4. Attach it to an empty HUD point
    5. Touch the HUD and see if there is script output in Local chat.
    6. If this doesn't work, then the problem is not with specific broken HUDs, but perhaps with your region, or some other unknown problem keeping you from running scripts.
  • Identify broken items:
    • Try removing all the HUDs and other attachments and testing them one at a time: test each one, then remove it, then test another.
    • If you have original copies of the items, try detaching the ones you are currently wearing and using a fresh copy from the original.
    • If an item is no-mod and you can't get it to start running again, and you don't have another copy, you will need to request a new copy from the creator.
    • Note: If the non-working HUDs are for your mesh body parts (or other scripted attachments), you probably will need to use fresh copies of the original HUDS and the body parts – every part, from scratch (not copies of the broken ones you were wearing).

HUDs Not Showing

Hiding/Showing HUDS

Look in the Avatar menu and make sure that “Show HUD Attachments” has a checkmark.

HUDs Moved/Rotated out of Visibility

A HUD's orientation data (position and rotation) data is stored with the HUD when it's detached. It is relative to the attach point, not to the viewer. (Any attached object has its orientation data saved when it's detached) When you attach a HUD to a new attach point, the previous position data is applied relative to the new attach point and the rotation data is reset to zero, and this can cause the HUD to be out of position or rotated incorrectly. To fix a HUD's position:

  • Attach the HUD to its original attach point
    or
  • Edit the HUD (right click it in Inventory, choose Edit) and set the position data to zero and then adjust from there
    or
  • Edit the HUD and then scroll down with the mouse wheel to zoom out the HUD Layer, represented by a white rectangle. Drag the HUD so that it's inside the rectangle, then zoom in and finish adjusting.

If the HUD can't be seen but its position is correct, you may have to adjust the rotation. Edit the HUD, then change the rotation values or drag the rotation rings.

↧
Search

phoenix:outfits

July 3, 2018, 3:38 am
$
0
0

What are Outfit Links?

Outfit links (inventory links), gives you the ability to create complete outfits with hair, skin, shape, shoes, clothing etc without having to copy items into a folder. This is especially useful when you have a pair of shoes for example that are no copy.

So for example, I have a pair of shoes that look great with a few different outfits I like to wear, but the shoes are no copy. So I have to wear my outfit, then dig through my inventory to find the shoes. With Inventory links I can create an entire outfit, or several outfit combination's without having to move/copy or find my inventory items.

Where are the links saved?

In your inventory you will see a folder called “My Outfits”. In this folder you will first see a bunch of outfit links to newbie avatars. You can choose to keep or delete these if you want. When you create an outfit using inventory links, it gets created in this folder.

How do I create Outfit Links?

Find an outfit you like, including (or not) shoes, huds, anything you want to wear with this outfit.
- Go into appearance
- At the bottom right is a button called “Make Outfit”, click this.
- In the new window that opens you will see listed and checked by default, everything you are wearing. This includes attachments, clothing layers, huds, hair, shape, skin, eyes… Everything. If you uncheck something, it will not be included in the outfit folder.
- Make sure you have “Use Viewer 2 outfit folders” checked at the bottom left.
- Give your outfit a name under “Outfit Name”
- Click Save.

How do I find my new outfit?

Now if you go to your inventory and open the “My outfits” folder, you will see everything that was check marked, in the way of links. This means that you can right click on your outfit folder, and choose “Wear” or “Replace Outfit” and you will automatically wear everything in that folder.

What happens if I want to delete inventory linked items?

You can safely delete inventory linked outfits or items in the My Outfits folder. It will not delete the actual inventory items that they link too.

We also have a video tutorial on inventory links.

↧
↧

index_fr

July 3, 2018, 9:09 am
$
0
0

Cette documentation est en cours de traduction et/ou de mise à jour. Merci de votre patience et de votre compréhension.
Merci !
The Phoenix Viewer Project, Inc


Documentation Firestorm

Index Général

Téléchargements

Obtenir de l'Aide

Support

Guide d'utilisateur Firestorm

Fonctions de base

Sujets Avancés

Tutoriels & autres infos

Getting Help

Groups and Classes

Firestorm Tutorial Videos

The following videos are about the Firestorm AO:

Contact and Policies


↧

firestorm_support_groups_join_fr

July 3, 2018, 9:19 am
$
0
0
, ,

Rejoindre les Groupes de Support du Viewer

Cliquez le lien pour ouvrir le profil du groupe dans Second Life et rejoingez-le maintenant !

English
Official Support for the Firestorm Viewer
Phoenix/Firestorm Viewer Support

Deutsch
Offizielle Gruppe für Firestorm Viewer Support
Firestorm Support German

Español
Grupo Oficial en Castellano del Visor Firestorm
Firestorm Viewer Support Spanish

Francophone
Support Officiel Francophone Firestorm
Firestorm Viewer Support Francophone

Italiano
Sito ufficiale di supporto per il Viewer Firestorm
Firestorm Viewer Support Italian

Magyar
A Firestorm Viewer Hivatalos Magyar nyelvu Supportja
Firestorm Viewer Support Hungarian

Nederlands
Steungroep Firestorm
Firestorm Support Dutch

Polski
Firestorm Support Polska
Phoenix Support Polish

Português
Grupo oficial para suporte do Firestorm
Firestorm Support Portuguese

Русский
Oфициальная группа поддержки Firestorm
Phoenix/Firestorm Support Russian

↧

getting_help_fr - [Support pour Autres Problèmes (Hors Bugs)]

July 3, 2018, 9:43 am
$
0
0

Obtenir de l'aide pour Firestorm

Si vous rencontrez des problèmes pour l'utilisation de Firestorm, il existe plusieurs façons d'obtenir de l'aide. Nous vous recommandons d'essayer les suivantes, dans l'ordre où elles sont indiquées.

Phoenix Viewer n'est plus officiellement supporté depuis le 1er janvier 2013.

Documentation En Ligne

Il existe une documentation très complète pour le viewer, contenant toutes les explications sur ses fonctions et leur utilisation. S'il y a une fonction que vous ne savez pas utiliser, merci de commencer par consulter la documentation Firestorm

Les Choses Ne Fonctionnent Pas Correctement

Si ça ne marche pas correctement ou si vous crashez beaucoup, ou vous faites déconnecter, etc, alors le mieux est d'aller à la section des Diagnostics et Solutions Rapides sur notre wiki en ligne.

Obtenir de l'aide dans SL

Si les suggestions ci-dessus ne vous ont pas apporté de solution, ou si vous avez besoin d'une aide urgente, le mieux est de contacter l'un des groupes de support en ligne.

Merci de noter que le “chat lag” peut être un réel problème. Aussi, lorsque vous demandez de l'aide dans un groupe, merci de vous rappeler ceci :

  • Merci d'indiquer votre système d'exploitation (Windows, OSX, Linux) et sa version.
    Firestorm dispose d'une case à cocher en haut de la fenêtre du chat de groupe: Specify Version; merci de cocher cette case, cela rendra plus efficace et plus rapide l'aide que vous obtiendrez de la part des membres de l'équipe.
  • Si votre question n'apparaît pas immédiatement laissez aux autres le temps de répondre. Reposter plusieurs fois la même question ne servira à rien.
  • Le chat lag a parfois pour effet de fare apparaître les posts dans le désordre, aussi nous vous recommandons, au lieu de poster de courtes phrases, d'exposer votre problème en une seule fois, de manière concise et claire.
  • Si notre wiki a la réponse à votre question, il est très probable qu'on vous donnera le lien vers la page correspondante; la solution du wiki est bien souvent plus détaillée que l'aide que vous obtiendrez dans le groupe, en fonction de la disponibilité des modérateurs.
  • Ayez en tête que les membre du support sont des bénévoles, et qu'ils prennent sur leur temps de loisir pour vous fournir de l'aide, sans rémunération. Il peut arriver qu'il ne puissent pas vous aider, mais ils essaient. Restez respectueux.
  • Les groupes de support sont classifiées “PG” donc tous publics, merci de ne pas y tenir de propos grossiers ou de conversations pour adultes. Les conversations hors sujet sont autorisées, mais elles doivent faire place au support lorsque les questions en rapport avec le viewer se présentent. Pas de publicité, de propos haineux, racistes, ou insultants, pas de politique, de propagande, de provocation, pas de drame; pas de spam, de publicité, de racolage ou de mendicité.

Enregistrer une Demande de Support or Signaler un Bug

Si vous pensez avoir trouvé un bug - ou si vous n'avez pas pu obtenir d'aide dans notre wiki ou dans un groupe de support - vous pouvez enregistrer un signalement ici notre JIRA (bug tracker) . Dans le but d'obtenir une aide efficace, fournissez toute information de base.

Viewers basés sur Firestorm

L'équipe de Support Firestorm ne fournit de support que sur la version officielle la plus récente du viewer Firestorm. Les versions plus anciennes, même publiées par l'équipe Firestorm, sont sujettes à un support limité, voire pas de support du tout.

Viewer CtrlAltStudio

Bien que principalement basé sur Firestorm, le viewer CtrlAltStudio (CAS) n'a pas cependant aucun lien avec Firestorm. Pour l'instant, son site web dit à ses utilisateurs:

  • “Si le problème que vous rencontrez ou la suggestion d'amélioration n'est pas en lien direct avec les fonctions spécifiques de CtrlAltStudio (voir liste ici), merci de vérifier si cela est en rapport avec le viewer Firestorm; si c'est le cas adressez-leur directement votre demande”.

N'interprétez pas cela en imaginant que les utilsateurs doivent aller chercher de l'aide sur CAS auprès de l'équipe Firestorm. Cela ne concerne que le développement du viewer, ce qui signifie que la source adéquate pour ce type d'information est le JIRA, dans lequel les signalements de bugs et les demandes d'amélioration sont traités.

Etapes pour traiter votre problème sur CAS :

  • Cherchez dans le JIRA pour voir si votre problème a été signalé et s'il est en cours de traitement en tant que bug. Si c'est le cas, commentez et/ou suivez ce JIRA (si vous n'en avez pas, il vous faudra créer un compte JIRA pour ce faire); s'il existe des solutions elle seront sûrement évoquées dans les commentaires. Dans le cas contraire vous ne pouvez rien faire d'autre en attendant que le bug soit réparé. Notez bien que pour commenter un problème en cours de traitement vous devrez avoir testé votre problème sur la version actuelle de Firestorm.
  • Vous noterez que comme la version de CAS ne correspond pas toujours à la version actuelle de Firestorm, il est possible que le bug ait déjà été réparé, et que la dernière version de Firestorm en soit donc exempte. Dans ce cas, les utilisateurs de CAS n'en bénéficieront pas jusqu'à ce que le(s) développeur(s) de CAS mette(nt) CAS à jour.
  • Si votre bug n'a pas encore été signalé, téléchargez la dernière version de Firestorm pour tester la présence du bug puis ouvrez votre propre JIRA. Il est impératif de tester votre problème sur la version actuelle officielle de Firestorm avant d'ouvrir un JIRA. Les signalements de bugs sans l'information système actuelle de cette version seront rejetés et fermés.

Versions Compilées "Maison" de Firestorm

Même si la version de Firestorm que vous utilisez est la même que la version officielle actuelle, nous ne pouvons pas fournir de support dans nos groupes si vous l'avez construite sur votre système. Il peut y avoir de légères différences dans les environnements qui génèrent des résultats inattendus. Téléchargez la dernière version officielle et testez sur cette version avant de signaler votre bug ou de faire une demande de support.

Versions Plus Anciennes de Firestorm

Seule la dernière version officielle du viewer est supportée. Des versions précédentes restent disponibles (généralement les deux avant-dernières versions et parfois une ou deux de plus) dans l'idée que si elles fonctionnent pour vous il n'y a pas de raison de vous forcer à mettre le viewer à jour. Si des problèmes se présentent, installez la dernière mise à jour avant de demander de l'aide au Support.

Support pour Autres Problèmes (Hors Bugs)

Si vous savez ou si vous suspectez que votre problème n'est pas un bug :

  • Commencez par télécharger la dernière version de Firestorm pour vérifier si vous y rencontrez également le problème.
  • Utilisez la page Diagnostics et solutions rapides du wiki Firestorm pour rechercher des solutions à votre problème.
  • Si vous ne trouvez pas de solution adéquate à votre problème, vous pouvez rejoindre l'un des groupes de Support Firestorm pour demander de l'aide, mais rappelez-vous qu'il est impératif d'utiliser la dernière version officielle de Firestorm pour recevoir de l'aide.
↧
↧

file_a_jira_fr - [Travail Sur Votre Demande]

July 4, 2018, 7:41 am
$
0
0
, , ,

Comment Enregistrer Un JIRA

Vous pouvez enregistrer un JIRA pour les raisons suivantes :

  • Pour demander une nouvelle fonction
  • Pour demander une amélioration
  • Pour signaler un bug
  • Pour demander de l'aide

Création du Compte

Si vous souhaitez faire du JIRA une utilisation plus complète que la simple consultation, il vous faudra un compte JIRA? LA création du compte est facile. Allez sur la page d' inscription et renseignez les informations suivantes :

  • Full Name - (nom complet) - C'est votre nom SL complet. Si votre nom d'utilisateur (username)est beta.tester, votre nom complet est Beta Tester. C'est le nom que tout le monde verra lorsque vous créez un JIRA ou que vous commentez, donc n'utilisez pas votre nom RL.
  • Password (mot de passe) - Il doit comporter au moins 8 caractères, et ne doit pas être votre mot de passe SL, par exemple.
  • Confirm Password confirmez votre mot de passe - Tapez de nouveau votre mot de passe.
  • Username (nom d'utilisateur) - Vous pouvez mettre le nom que vous voulez mais nous préférons que vous utilisiez votre nom SLsans espace: si votre nom est en deux mots vous pouvez utiliser le point pour les séparer - exemple : beta.tester. C'est le nom qui vous servira d'identifiant pour la connexion au JIRA.
  • Email - Indiquez une adresse e-mail valide. Le JIRA peut vous envoyer des emails lorsque quelqu'un commente votre JIRA (y compris le support) ou sur les problèmes que vous suivez.

Lorsque vous avez totu rempli cliquez sur “Sign up” et c'est parti. Si le JIRA renvoie une erreur, corrigez les infos que vous avez fournies et cliquez de nouveau sur “Sign up”.

Cliquez ici pour aller sur la page d'inscription.

Création d'Un Incident

Peu importe le genre d'incident que vous voulez créer, le procédé est pratiquement toujours le même; il faut commencer par aller sur le tableau de bord JIRA (dashboard), et cliquer sur le lien “Create” (créer) vers le haut de la page (chaque page), à droite sur la ligne de menus. SI vous ne voyez pas cette ligne vous devez vous connecter - cliquer “Log In” (se connecter) dans le coin en haut à droite, puis entrez vore nom d'utilisateur (username) et votre mot de passe (password) et cliquez “Log In”.

Lorsque vous cliquez “Create” une fenêtre s'ouvre avec des options “Project” (projet) et “Issue Type” (Type de Problème). Il existe un choix assez large, voici les options les plus communes :

* Demande de Nouvelle fonction :

  • Dans “Project” choisissez Firestorm, et dans “Issue Type” choisissez “New Feature” (nouvelle fonction).
  • Demande d'Amélioration Dans Le Code Actuel :
    • Dans “Project” choisissez Firestorm, et dans “Issue Type” choisissez “Improvement” (Amélioration).

* Signalement d'Un Bug :

  • Dans “Project” choisissez Firestorm, et dans “Issue Type” choisissez “Bug”.
  • Demande de Support :
  • Dans “Project” choisissez Firestorm, et dans “Issue Type” choisissez “Support Request”.

Les champs suivants et les informations à fournir sont toujours les mêmes quel que soit le type d'incident que vous souhaitez envoyer.

  • Summary (Résumé) - Expliquez très brièvement (en quelques mots) de quoi il s'agit
  • Priority (Importance) - Par défaut l'importance est réglée sur “Major”(Majeure) et vous pouvez la laisser telle quelle. Si vous signalez un problème qui vous empêche de vous connecter avec tout viewer, vous pouvez sélectionner “Blocker” (Bloquant). Si votre signalement ne concerne qu'une erreur de frappe, vous sélectionnerez plutôt “Minor” (Mineure) ou même “Trivial” (Banale). Si vous séléctionnez un niveau d'importance erroné, pasde souci nous vous aiderons à le modifier de manière adéquate.
  • SL Avatar Name - Indiquez le nom de l'avatar affecté par le problème.
  • Patch Attached (Patch joint) - Si vous soumettez un patch qui ajouterait une nouvelle fonction, ou en améliorerait une qui existe déjà, ou qui corrigerait un bug, cochez cette case. Sinon laissez-la décochée.
  • Reported In (Signalé Dans)- Sélectionnez le viewer que vous utilisez, que ce soit celui sur lequel vous avez le problème ou non.
  • Affects Versions (Affecte les Versions)- C'est ici que vous pouvez identifier toutes les versions que vous avez vues affectées : par exemple si vous avez testé chacune des versions actuelles de Firestorm, listez-les toutes. Si vous ne savez pas, n'indiquez que celle que vous utilisez.
  • Environment - Cette indication est très importante pour les demandes de support et pour les signalements de bugs. Nous avons en effet besoin de voir la façon dont le viewer détecte vos infos système. pour recueillir cette information, ouvrez le viewer, clique sur le menu Help tout en haut et sélectionnez “About”, puis cliquez en bas le bouton “Copy to Clipboard”. Revenez sur votre page de création de JIRA et dans le champ “Environment”, faites un clic droit > Coller (ou pressez Ctrl -V).
    Notez que si vous demandez autre chose que du support, cette information sera visible publiquement. Vous pouvez donc supprimer la partie qui indique l'endroit où vous vous trouvez si vous le souhaitez.
  • Description - C'est dans ce champ que vous pouvez expliquer de manière très détaillée votre problème ou votre demande (vous pouvez le faire en français). Si vous signalez un bug ou si vous avez un problème que vous pouvez reproduire de manière systématique, indiquez en détail toutes les étapes que vous suivez pour le reproduire. Indiquez aussi si par exemple le problème affecte un seul avatar ou pas, s'il se produit sur plusieurs ordinateurs ou pas (si oui, merci de fournir également les infos système de l'autre ordinateur), etc. Si vous obtenez un ou des messages d'erreurs, recopiez les soigneusement de manière exacte.
  • Attachment (Pièces jointes) - Vous pouvez joindre des fichiers (images, clips vidéos, …) pour illustrer votre JIRA, pour nous aider à comprendre le problème : cliquez le bouton “Browse” pour les ajouter. Rappelez-vous simplement que la taille maximum de fichier est de 10MB, et que les images doivent être sous format JPG ou PNG. Si vous le pouvez, joignez aussi vos journaux de viewer (voir plus bas comment faire).

Lorsque vous avez terminé de remplir tous les champs, vous pouvez cliquer sur le bouton “Create” en abs de la page.

Comment Nous Fournir Vos Journaux de Viewer

Les informations supplémentaires de taille dont nous pourrions avoir besoin pour vous aider sont vos journaux de viewer. Ces fichiers son tparfois très utiles pour déterminer la cause du problème et trouver une solution. Les journaux doiventêtre recueillis après la déconnexion de SL - ou après un crash si c'est le problème que vous avez - et avant de redémarrer le viewer. Si vous vous reconnetez ces précieuses informations seront perdues.

NB: Merci de faire ceci, même si vous avez activé les rapports de crash.

L'emplacement par défaut du répertoire contenant les logs(journaux) est caché dans pratiquement tous les systèmes d'exploitation. Pour le trouver vous allez devoir afficher les fichiers cachés. Les logs(journaux) se trouvent :

Firestorm 32-bit
Windows Vista, 7, 8.1 and 10 C:\Users\[NOM D'UTILISATEUR]\AppData\Roaming\Firestorm\
(ou tapez %APPDATA% dans la barre d'adresse de votre exlorateur de fichiers)
Mac /Users/[NOM D'UTILISATEUR]/Library/Application Support/Firestorm/
linux ~/.firestorm/
Firestorm 64-bit
Windows Vista, 7, 8.1 and 10 C:\Users\[NOM D'UTILISATEUR]\AppData\Roaming\Firestorm_x64\
(ou tapez %APPDATA% dans la barre d'adresse de votre exlorateur de fichiers)
Mac /Users/[NOM D'UTILISATEUR]/Library/Application Support/Firestorm/
linux ~/.firestorm_x64/

Compressez tous les fichiers du répertoire “logs” :

  • Windows: Clic droit sur le répertoire > Envoyer vers > Dossier compressé
  • Linux Gnome: Clic droit sur le répertoire > Compresser
  • Linux shell: tar -cjvf “Viewer_logs.tar.bz2” ./logs/
  • Mac: Maintenez la touche Maj enfoncée pendant que vous sélectionnez le contenu du répertoire, puis Ctrl-clic > Compresser

Le plus facile est de placer ce fichier compressé sur le Bureau et le faire glisser dans le cadre “Drop files here to attach them or Select Files”, à droite dans la page. Si vous préférez, vous pouvez cliquer le bouton “Select Files” et naviguer jusqu'au fichier compressé puis l'ajouter.

Vérifiez bien une dernière fois que vous n'avez rien oublié et cliquez le bouton “Create”. Si vous changez d'avis et que vous renoncez à enregistrer ce JIRA, cliquez le bouton “Cancel”.

Travail Sur Votre Demande

Une fois le JIRA créé vous verrez le numéro d'indicent sous forme de projet abrégé (comme SUP ou FIRE), et un numéro (exemple : FIRE-1234). Seuls, vous et les membres de l'équipe, pouvez voir vos propres incidents SUP.

Vous allez aussi recevoir un email lorsque quelqu'un commentera votre JIRA, ou si un document est joint, ou si toute autre action intervient. Cliquez dans l'email le lien qui ressemblera au numéro d'incident qui vous avait été initialement attribué, et ajoutez un commentaire sur l'incident. Ne répondez pas à l'email, cela ne fonctionnera pas.

Si vous ne recevez pas d'email, vérifiez vos indésirables, et vérifiez aussi que l'adresse email que vous avez fournie est bonne. Vous pouvez confirmer votre adresse email en allant dans votre profil et en cliquant l'icône crayon dans la section “Details” en haut de la page.

↧

showing_hidden_folders_fr

July 5, 2018, 2:12 am
↧

logo.png - created

May 8, 2018, 9:03 am
↧
Search

logo_main.png - created

May 8, 2018, 9:03 am
↧
↧

mesh_issues - [OpenSIM-Specific]

July 6, 2018, 5:54 am
$
0
0
, , , , , , , , , , ,

Mesh Issues

General

So you have the latest viewer and still can't see mesh - what's the deal?

Well, it isn't necessarily automatic. Depending on your specific hardware, certain settings that need to be enabled for mesh, may be set off by default.

Go to Preferences→ Graphics -> General; then enable Basic Shaders.

If this remains greyed out, then increase the level of Render Quality until Basic Shaders becomes enabled and can be checked.

Make sure you have a reasonable draw distance. If you have difficulty rendering mesh, lower it; if your draw distance is over 128, set it to 128, or less. (The optimal value for draw distance is entirely dependent on your own hardware; you will need to experiment to find what works best for you.)

In some cases, worn mesh attachments will not render properly still. Go to Preferences→ Graphics -> Rendering and disable both of the Alpha Mask Rendering options.

There are also rare instances of glitches where mesh that you are wearing appears worn by another avatar (yes, it is bizarre!). In that case, try going to Preferences → Graphics → General, and enable Hardware Skinning.

In some cases, low-end graphics cards or very old graphics drivers may require you to turn hardware skinning off rather than on. Before doing this, please try updating your graphics drivers and review the other options on this page, as turning hardware skinning off may reduce your performance.

If you have Webroot SecureAnywhere Antivirus, see Webroot Issues. For other antivirus apps, see our Whitelisting Guide, and be sure to whitelist all parts of the viewer. This may need to be done from scratch each time you upgrade to a new version.

If mesh is simply slow to appear, but does appear eventually, that is not necessarily a problem with mesh itself; please work through this page: Slow Rezzing.

HTTP fetching may be overloading your router; please try the suggestions given here; if they do not help, revert the changes made then return to this page and continue.

If none of the above work - and make sure you try all of them first! - then in the top menu bar, open Advanced → Debug Settings, type in Mesh2MaxConcurrentRequests and gradually decrease (not increase) the value. (If Advanced is not visible on the top menu bar, press Ctrl-Alt-D.) If it does not help, try increasing the value from the default. Under no circumstances should you increase this beyond 64. Please see this comment on a related JIRA ticket for an explanation of the possible drawbacks of increasing this setting. Additionally, we recommend returning it to default once the mesh you're trying to see is visible.

Some Mesh Items Vanish If I Cam Out

In most cases, this is due to the mesh item being made low LOD so as to reduce its land impact. You should never try to resolve this by increasing LOD above the maximum allowed in Preferences → Graphics → General (4), as that would result in greatly increased memory use, usually leading to a significantly increased rate of crashing. Rather, the issue is inherent in how the mesh item was made. So you either live with it, or replace the item.

Spikes and Colored Shards Across Screen

This happens more frequently for those using ATI/AMD graphics and drivers, but has been seen occasionally with Nvidia graphics and drivers as well. Visit Graphics Glitches for ways to address this.

Pyramids / Ducks

If you can see most mesh fine but a specific mesh item fails to render and/or displays a pyramid, triangle, or ducky when it's first worn or rezzed, then read on. This is caused by mesh that fails to load, and in many cases is a result of having too high a draw distance in the presence of a lot of complex mesh.

  • Reduce draw distance significantly, then relog. That often clears the problem.
  • If that doesn't help, reboot all your network hardware and then your computer.
  • (If the problem occurs only on selected regions, it could simply be a symptom of region lag–see http://wiki.phoenixviewer.com/lag for information. In this case, there may be nothing you can do about it.)

If this still doesn't help, then:

Mesh Appears Splotchy, Blotchy, or Has Strange Patches of White, Black, or Other Colors

In Preferences → Graphics → General, make sure Basic Shaders and Hardware Skinning are enabled.

OpenSim-Specific

If certain mesh objects are invisible on Firestorm 5.0.11 on OpenSim grids, set the debug setting FSEnforceStrictObjectCheck to False. To change that setting, go to top menu, Advanced (Ctrl-Alt-D to enable Advanced, if it isn't), Show Debug Settings. Type in FSEnforceStrictObjectCheck, set to False, then close the DebugSettings window.
On OpenSim grids, mesh should never be uploaded using “Analyze”. Analyze should only be used on grids that support Havok.
On Firestorm 5.0.11, mesh uploaded with Analyze is likely to render invisible when FSEnforceStrictObjectCheck is set to true.
An in-depth discussion about this problem can be found here.

↧

mac_os_x_10.13_high_sierra

July 7, 2018, 1:53 am
$
0
0
, , , , ,

Mac High Sierra (10.13) Issues

Performance Issues and Low FPS

If, after upgrading to High Sierra, you are experiencing low performance and extremely low FPS, follow the steps for a full clean install of the viewer as set out here: Full Clean Install.

Nvidia Drivers

To install and use Nvidia web drivers

  • Find the list of Nvidia web drivers here, with download links directly from Nvidia: Nvidia Web Drivers.
  • It is important that the drivers are matched to you OS Build number, see here for: How to determine your OS Build Number.
  • You can switch between using the Apple Nvidia driver and the Nvidia web driver (needs a reboot after each change).

Failed to Decode Login Credentials

If, after upgrading to High Sierra, Firestorm complains that it cannot decode the credentials when you launch the viewer, refer to the steps set out here: Login Credentials.

↧

mac_os_x_10.11_el_capitan

July 7, 2018, 1:55 am
$
0
0
, , , ,

Mac El Capitan (10.11) Issues

Nvidia Driver Crash

General Info

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

(This crash has continued on Sierra.)

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

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

To Install and use Nvidia Web Drivers

  • Find the list of Nvidia web drivers here, with download links directly from Nvidia: Nvidia Web Drivers.
  • It is important that the drivers are matched to you OS Build number, see here for: How to determine your OS Build Number.
  • You can switch between using the Apple Nvidia driver and the Nvidia web driver (needs a reboot after each change).

Missing Characters

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

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

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

↧

mac_os_x_10.12_sierra

July 7, 2018, 1:56 am
$
0
0
, , , , ,

Mac Sierra (10.12) Issues

Nvidia Driver Crash

General Info

This crash started on El Capitan and has continued on Sierra.

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

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

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

To install and use Nvidia web drivers

  • Find the list of Nvidia web drivers here, with download links directly from Nvidia: Nvidia Web Drivers.
  • It is important that the drivers are matched to you OS Build number, see here for: How to determine your OS Build Number.
  • You can switch between using the Apple Nvidia driver and the Nvidia web driver (needs a reboot after each change).

Extra Title Bar

Sierra comes with a new feature that allows compatible applications to create multiple tabs in one window, much like a web browser. Unfortunately, Firestorm is not a compatible application, so if the key combo (Cmd-Shift-T) is hit while you're logged in on Firestorm, whether intentionally or by accident, a second title bar (the bar that shows the viewer name, version number, and name of the account currently logged in) will appear below the regular one, with no apparent way to get rid of it.

To rid yourself of this extra title bar:

  • Hit Cmd-Shift-T again. This should turn the second title bar into a blank red bar.
  • Relog.

The extra bar must be red and the app title not showing when you relog. If the second title bar is showing, it will still be there when you relaunch the viewer.

↧
↧

logo.png - created

May 8, 2018, 9:03 am
↧

logo_main.png - created

May 8, 2018, 9:03 am
↧
Search

graphics_crashes_and_glitches - [Viewer Not Responding]

July 7, 2018, 10:11 pm
$
0
0
, , , , , , , ,

Graphics Crashes and Glitches

If You Have Changed Any Debug Settings

Several creators recommend specific settings in order for you to be able to better see their products. Sadly, some of these recommendations will lead to many people crashing more. For example, go to the top menu, Advanced → Debug Settings (press Ctrl-Alt-D to enable Advanced, if it isn't):

  • RenderVolumeLODFactor should never be set over 4; a good value is between 2 and 3.
  • TextureLoadFullRes should never be enabled (in other words, it should be set to FALSE).

If you are advised to raise LOD above 4, please disregard that advice.

Similarly, there is a notecard going round which suggests settings to prevent graphics crashes. Sadly, those settings can often result in perfectly ordinary content refusing to render. So if you have changed debug settings per such a notecard, revert them.

For both the cases above, should you not remember what settings you changed, then proceed as follows:

  1. Back up your settings as explained here.
  2. Then wipe settings by following the instructions on this page.
  3. Log back in and see if this fixes your problem. If it does, you can try a restore and see if the issue returns.
  4. If the problem does return, wipe settings again and set them from scratch.

Rainbow Colors after Logout

Note: This is not the same as rainbow colors in-world.

If you see rainbow colors after logout and you have MSI True Color or f.lux installed on your system, do the following steps in order:

  1. Uninstall MSI True Color if installed.
  2. Install f.lux from https://justgetflux.com/ if not installed.
  3. Uninstall f.lux using the f.lux uninstaller, not the Windows uninstaller from Windows programs & features / add/remove programs.
  4. When running the uninstaller it will give you the option to reset to the windows default color profile; say Yes. (Running this uninstaller is the only way we have found to get rid of the MSI True Color profile.)

Refer to http://jira.phoenixviewer.com/browse/FIRE-12561. Also see the alternate workaround at the comment dated 13/Apr/17

Driver Not Responding

"Display driver stopped responding and has recovered" error in Windows

If you are getting the error in the title, then please refer to this page, this page or this page for those using Intel graphics for possible solutions.

With thanks to Skua Sarrasine for having found the first of these.

nVidia Driver Error Code 7 (or 3)

Symptom:“This is a bug thats only experienced with Firestorm running. Basically, at seemingly random, but very infrequent times, my dual screens will bug out, producing two displays of solid colour, randomly. Sometimes Windows will return saying it recovered from an error code 7 or 3.”

Some research turned up this for error code 7; it suggests setting physX to CPU. And that seems to have solved the issue.

Note also the (apparent) interaction with Chrome.

Viewer Not Responding

This is a known issue with Windows 7, 8.1, and 10 with a 64-bit operating system; it affects other programs in addition to Second Life viewers.

Please try the following - but NOT while logged in.

Windows 7

  • Go to the Start button
  • Type services.msc and then press enter.
  • Wait until the services window pops up.
  • You may have to expand the window a bit to see the services.
  • Look for DesktopWindowManager.
    • If it is running, right click it and select Stop. Wait until it stops.
    • You will probably see your desktop transparency window borders go flat. No worries.
  • Right click again and select Properties.
    • In the Startup type, select Manual. Click OK.

Windows 8.1/10

  • Open the Task Manager, by one of the following methods…
    1. Right click the task bar and choose Task Manager.
    2. Click the Start button and type Task Manager, then click on the result.
    3. Press Ctrl+Alt+Del and choose Task Manager from the list.
    4. Press Ctrl+Shift+Esc.
  • Click More Details link at the bottom if needed
  • Look at the several column headers, they will show a percentage of use. Memory or Disk may show a high percentage when Firestorm is not responding.
  • Click on one of the high-percentage column headers to sort the processes. The top one is likely the cause. If it's your antivirus, make sure you have whitelisted Firestorm and its cache (refer to this page for whitelisting guidance).

Viewer Freezing

If you find the Firestorm seems to freeze up every so often, then try these things, one at a time, testing between each one:

  • If you have chat saving enabled, and have a large number of chat transcript files, these could be causing the freezes. (Ref. FIRE-11322.) Try moving your chat transcripts elsewhere and see if the freezing stops.
    You can find your chat transcripts by going to Preferences→ Network & Files -> Directories→ Conversation logs and transcripts location; click the Open button.
  • Set Preferences → Network & Files → Directories → Cache Size to maximum (9984MB or the maximum space available, whichever is less)
  • Ensure that your antivirus software is not scanning the viewer cache folder. See Whitelisting the Viewer in Anti Virus Software for more information.
  • If you have ever enabled “Full Res Textures”, disable this setting. Top menu bar, Develop→ Rendering → Full Res Textures (dangerous). Ensure that this is NOT checked. (Ctrl-Alt-Q to enable Develop, if it isn't.)
  • Advanced → Debug Settings → Set FastCacheFetchEnabled to FALSE - then relog.
    Ctrl-Alt-D to enable Advanced, if it isn't.
  • Preferences → Graphics → Hardware Settings → Viewer Texture Memory Buffer - raise this as high as it will go. Then relog. (64-bit version only)
  • Tip from a user: Windows users: If you're running CrashPlan, open the “Advanced” section of “Backup” settings and uncheck “Back up open files.

For additional suggestions, see the page on Severe Lag.

↧

favorite-wearables.png

July 8, 2018, 8:23 am
↧
↧

fs_517_prerelease - ↷ Page name changed from fs_516_prerelease to fs_517_prerelease

July 8, 2018, 10:23 am
$
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.

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

[to be provided by KB]

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

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

↧

fs_voice

July 9, 2018, 4:20 am
$
0
0
, , , , , , ,

Voice Issues

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

  • Your ISP is throttling or blocking the voice service;
  • failure of the Vivox service;
  • voice issues on the region you are on;
  • voice being throttled by bandwidth set incorrectly - please check it by following the instructions here;
  • voice hardware (mic, headset) not configured correctly in your operating system settings;
  • voice hardware not configured correctly in the viewer;
  • another application has your voice hardware in use (example, Skype);

  • your anti virus software has “mangled” the voice application; see steps on this page: here.

  • your firewall is blocking slvoice. Add slvoice to your firewall's exclusion/allow list.
Please go to Voice Echo Canyon when trying to get voice to work. If voice is working correctly for you, anything you say there will be echoed back to you. Once there, relog to last location.

Known Issues

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

Steps:

  • Go to Preferences → Sound & Media → Voice, and untick “Enable Voice.”
  • Relog.
  • Wait 10-20 seconds, or until the viewer has finished rezzing the scene.
  • Re-enable voice.

Disable When Not in Use

Most voice connection issues happen when the viewer tries to connect to voice during the login process. The workaround is to disable voice before you log out, and then only enable it after logging in when you need it. You can toggle Voice from the Media Controls at the top of the viewer (not enabled by default for Vintage or Latency skins) by hovering over the speaker icon and then checking or unchecking the last checkbox, or by going to Preferences ⇒ Sound & Media ⇒ Voice and checking or unchecking the top option.

Ensure Headset Properly Connected

If you have issues hearing but not being heard, or vice versa, then make sure that you headset is properly connected to your computer. Unplug it, then plug it back in, making sure it is fully inserted.

And on a related note, if you plug your headset in while logged into SL, you will very likely have to relog to get it to be recognised.

Check Voice Settings in your Operating System

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

A bit more specifically, for Windows and linux, check in Mixer that SLvoice is listed, and not muted. Check that input and output devices are correct. For Mac, look in the Sound Preference pane.

Check Voice Settings in the Viewer

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

Try Reinstalling Drivers

Try reinstalling the drivers for your sound card, if you have one. Sometimes, these drivers conflict with the sound component of graphics card drivers. Similarly, you may have success by reinstalling your graphics card driver.

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

Voice Is Intermittent

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

You can also try adjusting your bandwidth as explained here.

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

Voice Worked Fine but Suddenly Doesn't Work

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

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

Never Been Able to Get Voice to Work

  • Does your headset/microphone work outside of SL? ie when using Skype, Yahoo or MSN
  • Is your voice chat volume turned up and not muted?
  • Is the SLVoice.exe (simply SLVoice on Mac) that is in the Firestorm folder in the exceptions/allowed list for your firewall? If your firewall is turned off, turn it on and add the SLVoice.exe (or SLVoice) anyway.
    If your Firewall has SLVoice listed twice, then remove both instances, and allow it again. For Win10, make sure that SLVoice has Private unchecked, and Public checked. If you had these set differently, change them, then close the window, log out of SL, reboot.
  • Check the bandwidth you are actually getting and what you have set in Preferences → Network & Files → Connection. Please refer to this page for specifics.
  • Go to top menu, Advanced → Debug Settings, and in the window that opens, type: Cmdlinedisablevoice - then ensure this is set to FALSE. (Use Crtl-Alt-D to enable the Advanced menu, if it isn't.)

By Operating System

Windows

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

  • To this end, download this file; save it to your hard drive. Make sure you do not have Firestorm running. Then extract the files to your Firestorm install folder. (For Firestorm 32-bit viewer, this is typically located at C:\Program Files\Firestorm on 32 bit Windows, and C:\Program Files (x86)\Firestorm on Windows 64-bit. For Firestorm 64-bit Viewer, this is typically located at C:\Program Files\Firestorm.) When prompted, allow the replacement of existing files.
Windows Vista and Windows 7

Try disabling compatibility mode, if enabled:

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

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

Mac

All Mac Operating Systems

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

Mountain Lion (10.8.x) Only

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

linux

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

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

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

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

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

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

    before launching Firestorm

1)
Incorporates suggestions from user Maverick Buccaneer.
↧

slow_rez_fr - created

July 9, 2018, 5:35 am
$
0
0
, , , , , , ,

Chargement Lent (Tout Est Gris)

Si les textures autour de vous restent grises trop longtemps, ou que les objets mettent du temps à charger, c'est essentiellement parce que les données n'ont pas été envoyées à votre viewer. Il existe If things around you remain grey for a long time, or objects take a long time to pop into position, this is essentially because the data has not yet been sent to your viewer. There are a number of possible causes, and solutions or at least work-arounds:

  • If you have Webroot SecureAnywhere antivirus installed, refer to this page.
  • Power down your router and/or modem. This generally means unplugging it from the power source. Leave them disconnected for at least a full minute before reconnecting. Wait for them to complete the power up sequence, then reboot your computer.
  • Teleport out, then back in.
  • The region is badly lagged (many avatars present, too many scripts running, etc.) and so the region server is using all its time processing and has very little time left over to deliver textures and other data to you. The best way to cope with this is to reduce the demand you make; in other words, reduce your draw distance, even to 12m or less, and wait until textures and objects have loaded before you increase it again.
  • You are experiencing packet loss or, more generally, have a poor network connection. Or your bandwidth slider may be set too high. Bring up the stats bar with Shift-Ctrl-1 and check Packet Loss and Ping Sim. Ideally, packet loss should be 0.0%, and Ping Sim under 200ms.
  • Determine optimal bandwidth: refer here.
  • You can also try to have less textures draw all at once by reducing draw distance when you teleport. You can do this manually, or make use of the built in Progressive Draw Distance function.
  • HTTP fetching may be overloading your router; please try the suggestions given here; if they do not help, revert the changes made then return to this page and continue.
  • Another possibility is that DNS look-up is failing. Try changing DNS to google; see this page for details.
  • Some other program on your computer might be interfering with your viewer's connection to SL, like a firewall or anti-virus. Try disabling them temporarily, to see if things improve. If they do, you have isolated the problem. Whitelisting the viewer and cache folder would probably help.
  • It has been reported that on Windows, the Aero background theme will also lead to textures refusing to rez, due to how much memory this feature consumes. Uninstalling that should help.
  • If mesh items, specifically, never rez, see Mesh Issues.
  • Several creators recommend specific settings in order for you to be able to better see their products. Sadly, some of these recommendations will lead to many people crashing more or having other issues, including very slow rez. Please see this page for more.
↧
Viewing all 5258 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>