De vez en cuando todos tenemos problemas en SL, y necesitamos “repararlos” para poder seguir disfrutando. Esto no siempre es algo sencillo de hacer y requiere varias pruebas. La resolución de problemas no siempre es algo simple, de hecho, muchas veces es un proceso lento que implica ir descartando una causa tras otra hasta encontrar la raíz del problema.

Lo primero a probar en muchos casos es reiniciar el visor, te sorprenderá saber cuantos problemas se resuelven de esta manera.

Lo siguiente a probar es intentar ir a una región/SIM diferente. Intenta con algún buen SIM “conocido”, los SIMs marítimos son, generalmente, una buena opción (prueba con aich o hatton), hazte TP y reloguea ahí si al llegar sigues teniendo problemas.

Si el problema persiste, reinicia la PC e intentalo nuevamente.

Asumiendo que aún sigues con el problema luego de haber realizado los pasos previos, te sugerimos que continues leyendo la Sección de Soporte de nuestra Wiki.

El procedimiento de “vaciar el caché” es algo a lo cual recurrir SOLO si el problema parece estar relacionado con las texturas. Un caché completo es siempre mejor que uno vacío. Vaciar el caché de inventario cuando tienes problemas cargándolo puede ayudar. Hay ocasiones en las cuales no quieras vaciar el caché de inventario, sino solamente el caché de texturas. Esto puede hacerse manualmente. Hay ocasiones en las que puedes necesitar vaciar el caché manualmente, haz esto abriendo la carpeta de caché y borrando los archivos en ella. Si quieres vaciar el caché manualmente sin borrar el caché de inventario, evita borrar los archivos con extensión .inv.gz ya que esos archivos son los del caché de inventario.

Things to look for when you have issues

In the viewer itself

Cumulative packet loss, found in the Help menu → About Phoenix Viewer - on the bottom line of the top section It looks like “Packets Lost: 760/302154 (0.3%)” High packet loss is a very good indicator that you are having network issues, data is constantly being sent from the viewer to the server and vice versa. This data is called Packets. High packet loss is a very good indicator that you are having network issues and reflects the percentage of data that is failing to be delivered to either you or the simulator.

The Statistics Bar (Ctrl-Shift-1, or View → Statistics Bar) is another good troubleshooting tool. Things to look at here are:

  • Under Basic
    • FPS” Frames per second: The higher the number here the better although most people will not notice any real difference over 20.
    • “Packet Loss”: This shows the realtime packet loss. Lower is better. If it stays high for a long period of time you will experience lower performance.
    • “Ping Sim”: The lower the number the better. This is the time it takes for information to travel between you and the server, lower is better. NOTE: your RL location will make a difference here people further away from the servers will have higher ping times. Generally speaking anything over 300 can be a problem.
  • Under Simulator
    • Time Dilation: The physics simulation rate relative to realtime. 1.0 means that the simulator is running at full speed; 0.5 means that physics are running at half-speed.
    • Sim FPS: The simulator frame rate. This should now always be the same as the physics frame rate – 45.0 when things are running well.
    • Physics FPS: The frame rate at which the physics engine is running. This should normally be at or near 45.0.
    • Pending Downloads: Number of asset downloads to the simulator that are pending. If this is greater than 1, this means that you may see delays in viewing notecards or scripts, and rezzing objects.
    • Pending Uploads: Number of current uploads of asset data pending. If this number is non-zero, this means that there may be performance issues when attempting to teleport.

More information on the statistics bar is available at the Second Life Wiki.

On your computer

The task manager (Windows) can show you what processes are active on your PC as well as the memory use.

There are some applications out there that can help you with troubleshooting as well. Note that you need varying degrees of technical knowledge to use them. Personally, I use one called Net Limiter 2 to monitor bandwidth and what is using it. There is also LogViewer Pro, which will allow you to look at viewer logs. Wireshark is another program that can help you diagnose network issues.

Special Note: We have had several users that were having issues that despite our best efforts we could not help, that reformatted their computers (Windows and MAC) and started off with a fresh install of their OS and then found that Phoenix ran fine. Coincidence? Consider that MOST people with infected PCs do not know that they are, and that an infected PC will have issues.

32% of the computers with AV protection are infected (Source.)

  • resolucion_problemas_basicos.txt
  • Last modified: 2011/05/28 14:10
  • by damian_zhaoying