Appearance Troubleshooting - Revision history

Justincc: /* Solution */

2014-06-26T23:36:59Z

‎Solution

Justincc: /* General */

2014-06-26T23:32:35Z

‎General

Cmickeyb: /* Establishing avatar appearance on login */

2013-04-22T19:58:03Z

‎Establishing avatar appearance on login

Justincc: /* Solution */

2013-02-22T00:56:26Z

‎Solution

Justincc: /* appearance show */

2013-02-22T00:55:42Z

‎appearance show

Justincc: /* Steps */

2013-02-21T22:38:27Z

‎Steps

Justincc: /* Steps */

2013-02-21T22:14:29Z

‎Steps

Justincc at 21:37, 21 February 2013

2013-02-21T21:37:00Z

Justincc: /* Introduction */

2012-10-03T01:47:32Z

‎Introduction

Justincc: /* Useful commands */

2012-10-03T01:46:41Z

‎Useful commands

← Older revision		Revision as of 23:36, 26 June 2014
Line 202:		Line 202:
	Try setting ResendAppearanceUpdates = true setting in the [Appearance] section of OpenSim.ini. This will resend appearance data every 60 seconds. This will probably not help if avatars are clouds, since this usually signals a failure to upload the data in the first place.		Try setting ResendAppearanceUpdates = true setting in the [Appearance] section of OpenSim.ini. This will resend appearance data every 60 seconds. This will probably not help if avatars are clouds, since this usually signals a failure to upload the data in the first place.

−	In OpenSimulator 0.7.4 this setting is not on by default (it is not present in OpenSimulator 0.7.3.1 and before). In OpenSimulator 0.7.5 it ~~will be~~ on by default.	+	In OpenSimulator 0.7.4 this setting is not on by default (it is not present in OpenSimulator 0.7.3.1 and before). In OpenSimulator 0.7.5 onwards it is on by default.

@@ Line 139: / Line 139: @@
 * Another general tip is to try clearing the viewer cache and logging back in.
 * One should also try a different viewer, either an old viewer such as Imprudence or a newer viewer such as Kokua or Firestorm.  Different viewers may have different ways of baking textures or may have issues with bugs.
 * If possible, one should also try a different simulator.  Even if simulators are running exactly the same version of OpenSimulator, they can be running on a different software stack (e.g. Mono rather than Windows .NET) or different hardware.  There may be differences in behaviour that stem from this.
 * Try a quiet region.  Regions with a lot of avatars and objects may be dealing with a lot of traffic that may cause appearance issues.  To test this, you could go to a quieter region or ideally even a local installation of OpenSimulator.

@@ Line 26: / Line 26: @@
 <!-- # If the viewer does not already have the baked texture asset, it requests it from the simulator via the GetTexture HTTP capability. -->
-As you can imagine there are many points at which this process can go wrong on, in the simulator, the sending viewer, the receiving viewer and at the network inbetween.  If it does go wrong, you will often end up with a gas cloud instead of an avatar.  The text below lists the various ways in which avatar appearance can go wrong, diagnosis commands and some suggestions for trying to fix the situation.
+As you can imagine there are many points at which this process can go wrong on, in the simulator, the sending viewer, the receiving viewer and at the network in between.  If it does go wrong, you will often end up with a gas cloud instead of an avatar.  The text below lists the various ways in which avatar appearance can go wrong, diagnosis commands and some suggestions for trying to fix the situation.
 == Establishing avatar appearance on teleport/region cross to another region on the same simulator ==

← Older revision		Revision as of 00:56, 22 February 2013
Line 200:		Line 200:

	In OpenSimulator 0.7.4 this setting is not on by default (it is not present in OpenSimulator 0.7.3.1 and before). In OpenSimulator 0.7.5 it will be on by default.		In OpenSimulator 0.7.4 this setting is not on by default (it is not present in OpenSimulator 0.7.3.1 and before). In OpenSimulator 0.7.5 it will be on by default.
−
−	~~If this works then you will need to update your configuration system.~~

@@ Line 77: / Line 77: @@
 The textures may be listed as (not found) if they have been uploaded by the viewer but can't be found in the asset cache.  Or they may be listed as (not set) if the viewer has never uploaded this data.
-If no name is given then data for all users is displayed.
+If no name is given then summary data for all users is displayed.
 == appearance send ==

@@ Line 13: / Line 13: @@
 # On login, the viewer asks the simulator what body parts and clothing it is wearing (AgentWearablesRequest UDP packet)
 # The simulator replies (AgentWearablesUpdate UDP packet).
-# The viewer confirms its appearance information to the server (AgentSetAppearance UDP packets).  This includes visual parameters (nose length, etc.).
+# The viewer confirms some appearance information to the server (AgentSetAppearance UDP packets).  This includes visual parameters (nose length, etc.).
 # The viewer asks the simulator if its appearance is already cached (AgentCachedTexture UDP packet).
 # The simulator currently always responds that no data is cached (AgentCachedTextureResponse UDP packet).
 # The viewer creates the appearance textures from the wearables (bakes them).
 # The viewer uploads these new baked textures to the simulator via the UploadBakedTexture HTTP capability.
 # The simulator stores this asset data in the simulator cache but does not send it to the asset service.
-# The simulator tells other viewers that can see that avatar (either because they are in the same region or neighbouring regions) about the UUIDs of the baked textures uploaded for that avatar (AgentAppearance UDP packets).
+# The simulator tells other viewers that can see that avatar (either because they are in the same region or neighbouring regions) about the UUIDs of the baked textures uploaded for that avatar (AvatarAppearance UDP packets).
 # These other viewers then request the baked textures for these UUIDs.
 # When a viewer has received all the baked textures for such an avatar, then it is displayed instead of remaining as a cloud.
@@ Line 29: / Line 30: @@
 == Establishing avatar appearance on teleport/region cross to another region on the same simulator ==
-In this case, the baked textures are already in the simulator's asset cache.  T
+In this case, the baked textures are already in the simulator's asset cache.  Hence, the steps are
-# The simulator tells other viewers that can see that avatar (either because they are in the same region or neighbouring regions) about the UUIDs of the baked textures it already has for that avatar.
+# The simulator tells both the uploading viewer and the other viewers that can see that avatar (either because they are in the same region or neighbouring regions) about the UUIDs of the baked textures it already has for that avatar.
-# These other viewers then request the baked textures for these UUIDs.
+# These other viewers then request the baked textures for these UUIDs if they don't already have them cached.
 # When a viewer has received all the baked textures for such an avatar, then it is displayed instead of remaining as a cloud.
-== Establishing avatar appearance on teleport/region cross to another region on a different simulator ==
+== Establishing avatar appearance on region cross to another region on a different simulator ==
-'''Todo: Need to fill out this section.  The big issue here is that by default, current OpenSimulator does not send baked textures to the asset service.  Therefore, other simulators end up telling the viewer that it doesn't have baked textures and the viewer rebakes and resends them.'''
+'''Todo: Need to fill out this section.  This should be the same as for teleport, but in current git master (as of 2012-02-21) there may be an issue where the avatar does not send AgentSetAppearance on entering the new region, which means that the rebake request is never triggered.'''
 = Useful commands =

@@ Line 1: / Line 1: @@
 = Introduction =
-Making an avatar appearance available in a simulator currently involves a large number of steps.
+Avatar appearance is a particularly complex issue in current OpenSimulator since it involves a complex interaction between a user's viewer (where the texture is actually created) and the simulator (which needs to send appearance information to the viewer, receive the baked textures and distribute those to other viewers).  Moreover, the exact steps of this interaction vary depending on whether the user is freshly logging in or region crossing/teleporting to another region on the same or a different simulator.
-# On login, the viewer needs to told what body parts and clothing it is wearing.
+This document currently describes only the classic viewer-side texture baking.  Server-side baking would do most if not all of these steps (especially the baking itself) in OpenSimulator instead.  However, this is not yet implemented by OpenSimulator.
-# The viewer then creates the appearance textures from this data (bakes them).
-# The viewer uploads the baked textures to the simulator via the UploadBakedTexture HTTP capability.
-# The simulator temporarily stores this asset data.
-# The simulator sends asset UUIDs to other viewers in the region.
-# If the viewer does not already have the baked texture asset, it requests it from the simulator via the GetTexture HTTP capability.
-# Other avatars appear with those baked textures.
-As you can imagine there are many points at which this process can go wrong.  If it does go wrong, you will often end up with a gas cloud instead of an avatar.  The text below lists the various ways in which avatar appearance can go wrong, diagnosis commands and some suggestions for trying to fix the situation.
+= Steps =
-'''Todo: Need to fill out this section with exactly what happens when a user teleports or crosses regions, both on the same region, regions on the same simulator and between regions on different simulators.'''
+== Establishing avatar appearance on login ==
 = Useful commands =

← Older revision		Revision as of 01:47, 3 October 2012
Line 12:		Line 12:

	As you can imagine there are many points at which this process can go wrong. If it does go wrong, you will often end up with a gas cloud instead of an avatar. The text below lists the various ways in which avatar appearance can go wrong, diagnosis commands and some suggestions for trying to fix the situation.		As you can imagine there are many points at which this process can go wrong. If it does go wrong, you will often end up with a gas cloud instead of an avatar. The text below lists the various ways in which avatar appearance can go wrong, diagnosis commands and some suggestions for trying to fix the situation.
		+
		+	'''Todo: Need to fill out this section with exactly what happens when a user teleports or crosses regions, both on the same region, regions on the same simulator and between regions on different simulators.'''

	= Useful commands =		= Useful commands =

← Older revision		Revision as of 01:46, 3 October 2012
Line 83:		Line 83:

	Attempt a JPEG2000 decode of the given asset. All baked textures are JPEG2000 files, so this can be useful to assess whether a given upload is corrupt or not. If the decode succeeds then it will tell you how many the number of layers and components in the JPEG2000 texture.		Attempt a JPEG2000 decode of the given asset. All baked textures are JPEG2000 files, so this can be useful to assess whether a given upload is corrupt or not. If the decode succeeds then it will tell you how many the number of layers and components in the JPEG2000 texture.
		+
		+	== dump asset ==
		+
		+	Usage
		+
		+	dump asset <id>
		+
		+	e.g.
		+
		+	dump asset ae8fe60d-9d20-440d-989a-869d2ee1ed3d
		+
		+	Dumps an asset to a file with the same name as the ID given. Can be useful for taking a closer look at textures in an external program (e.g. jiv on Linux) if they have been apparently successfully uploaded.

	= Problems and resolutions =		= Problems and resolutions =