Main | My View | View Issues | Change Log | Roadmap | Summary | Docs | My Account
  

Viewing Issue Simple Details [ Jump to Notes ] [ View Advanced ] [ Issue History ] [ Print ]
ID Category Severity Reproducibility Date Submitted Last Update
0002480 [opensim] [GRID] User Server minor sometimes 2008-10-27 08:38 2008-12-22 07:45
Reporter cmickeyb View Status public  
Assigned To justincc
Priority normal Resolution fixed  
Status closed   Product Version
Summary 0002480: avatar appearance does not persist consistently
Description Changes to avatar appearance (eg selecting a new skin or shape) do not appear to be persisting with any consistency (meaning that it appears to work correctly "very infrequently").

Steps to reproduce are pretty simple... log in, wear a new skin, log out and the log back in. You'll be wearing the old skin. On most occasions when I appear to have the correct appearance after login, a "rebake textures" reverts to the original (incorrect) appearance.

I've tried this running both stand alone and grid. Always running MySQL for storage.
 
Additional Information
Tags No tags attached.
Git Revision
SVN Revision 6977
Run Mode Standalone (Multiple Regions) , Grid (Multiple Regions per Sim)
Physics Engine ODE
Environment Mono / Linux32, .NET / Windows32
Mono Version None
Attached Files

- Relationships
duplicate of 0002574closed No avatar appearance persistence under MySQL in standalone 

-  Notes
(0006614)
cmickeyb (reporter)
2008-10-27 08:54

 When checking the database... doesn't seem to matter what changes I make, the appearance entries are not changed except for the revision counter. That is, no matter what i do on the client the asset & item identifiers are not changed.
(0006657)
justincc (manager)
2008-10-29 13:22

 This may be fixed now with r7003. Feedback welcome :)
(0006660)
cmickeyb (reporter)
2008-10-29 13:36

 Running 7003... Appearance does not persist. The status of clothing & body parts in the inventory window does not reflect changes. I've tried rebaking appearance after changes... no luck. The appearance *eventually* persists (if I keep changing it often enough) but its not obvious which version will actually persist.
(0006663)
justincc (manager)
2008-10-29 13:52

 Okay, from our IRC chat it sounds like this may be a different problem, possibly to do with persisting the wearables for the client. It's a bit strange since in my short tests with a single piece of clothing things appeared to be persisting correctly.

As we both know, a simple reproduction would be really nice :)
(0006665)
cmickeyb (reporter)
2008-10-29 14:30

 Reproducing the failure is easy... reproducing the rare times when appearance persists is hard. Working more to characterize the problem.

Basically... log on with shirt A worn (see A on the avatar, A marked "WORN" in the inventory), wear shirt B (see B on the avatar, B marked "WORN" in the inventory), log out. log on again, the avatar is seen wearing A again and shirt A in the inventory is marked "WORN". checking the database... the serial field changed, but the asset and item fields for shirt (which should reflect the change in the item that is worn) have not changed.
(0006685)
justincc (manager)
2008-10-30 07:35

 Has this problem just recently started occurring for you or has it been around for a long time?
(0006906)
justincc (manager)
2008-11-04 14:54

 Okay, I only got as far as tweaking some log messages today, but I may well continue with this tomorrow since it's annoying me.

Could you upgrade to at least r7090 and tell me if you see the log message

[APPEARANCE]: Received wearables for <avatar name>

when you wear something? If so, could you post a short section of the log that follows this?
(0006911)
cmickeyb (reporter)
2008-11-04 19:24

 I don't get the "received wearables" message. Instead, I get "avatar is child agent, ignoring AvatarIsWearing event" (looks like one per item that I wore.

i do get several receiving appearance messages in the log, but nothing about wearables.
(0006912)
cmickeyb (reporter)
2008-11-04 19:29

 One more thing... testing a few other combinations of simulators and databases, I found that I was able to change my avatar appearance using the same code base, same grid servers, and same configuration EXCEPT that I was using SQLite for the simulator storage instead of the normal MySQL database. That is, it fails when MySQL is selected as the storage engine (assets still grid-based).
(0006913)
nlin (developer)
2008-11-04 22:04

 Could this be related to the viewer you are using? I've noticed differences in avatar appearance between 1.19.1.4 and 1.21.6, running on the same database. (I rebake immediately after login.)
(0006914)
Orion_Shamroy (reporter)
2008-11-05 00:54

 I can confirm, using 7090 appearance persistence is intermittent. It seems my own account will always persist its appearance, however others always show as Ruth after logging or relogging.

08:48:23 - [APPEARANCE]: Found : [Wearables] => Body Item: 2bfadfa9-1c47-436b-9331-27bc19fb5b2d; Skin Item: bf440bc5-9e19-4b84-93c5-059fb8c38a8e; Shirt Item: 00000000-0000-0000-0000-000000000000; Pants Item: b6c0ba5b-a372-4520-a2b3-da6246b0798c;
08:48:23 - [EVENTQUEUE]: New client 841316e1-af93-4b6a-b370-f9ec31d2f467 detected in region Ravenport West
08:48:23 - [GROUP]: Adding Orion Pseudo to OpenSimulator Testing
08:48:23 - [FRIEND]: Claiming Orion Pseudo in region:1099511628032512.
08:48:24 - [CLIENT]: Entered main packet processing loop for Orion Pseudo
08:48:24 - [APPEARANCE]: Wearables requested by Orion Pseudo
08:48:24 - [APPEARANCE]: Sending wearables to Orion Pseudo
08:48:24 - [EVENTQUEUE]: sending response for 841316e1-af93-4b6a-b370-f9ec31d2f467 in region Ravenport: <llsd><map><key>events</key><array><map><key>body</key><map><key>SimulatorInfo</key><array><map><key>Handle</key><binary encoding="base64">AAPpAAAD6gA=</binary><key>Port</key><integer>9008</integer><key>IP</key><binary encoding="base64">0E1jaw==</binary></map></array></map><key>message</key><string>EnableSimulator</string></map></array><key>id</key><integer>7069016</integer></map></llsd>
08:48:24 - [CLIENT]: Got authenticated connection from 74.245.225.88:4973
08:48:24 - [CLIENT]: Adding new circuit for agent 841316e1-af93-4b6a-b370-f9ec31d2f467, circuit code 578697263
08:48:24 - [SCENE]: Adding new child agent Orion Pseudo 841316e1-af93-4b6a-b370-f9ec31d2f467 in Ravenport East
08:48:24 - [USER CACHE]: Adding user profile for 841316e1-af93-4b6a-b370-f9ec31d2f467
08:48:25 - [APPEARANCE]: Found : [Wearables] => Body Item: 2bfadfa9-1c47-436b-9331-27bc19fb5b2d; Skin Item: bf440bc5-9e19-4b84-93c5-059fb8c38a8e; Shirt Item: 00000000-0000-0000-0000-000000000000; Pants Item: b6c0ba5b-a372-4520-a2b3-da6246b0798c;
08:48:25 - [EVENTQUEUE]: New client 841316e1-af93-4b6a-b370-f9ec31d2f467 detected in region Ravenport East
08:48:25 - [GROUP]: Adding Orion Pseudo to OpenSimulator Testing
08:48:25 - [APPEARANCE]: Setting appearance for Orion Pseudo
08:48:25 - [APPEARANCE]: Sending appearance to all other agents for Orion Pseudo
08:48:25 - [APPEARANCE]: Sending wearables to Orion Pseudo
08:48:25 - [CLIENT]: Entered main packet processing loop for Orion Pseudo
08:48:30 - [OGS1 INVENTORY SERVICE]: Received inventory response for user 841316e1-af93-4b6a-b370-f9ec31d2f467 containing 70 folders and 3718 items
08:48:30 - [ATTACHMENT]: Rez attachment 56fceee2-4bd3-4912-8df7-ea2295bae716
08:48:40 - [REGION DB]: Removing obj: 9f4a388f-0100-4366-a8d8-83c2ef980ec4 from region: 7bd70e3e-a0b0-4639-80d4-bbbdcafd1f83
08:48:41 - [ATTACHMENT]: Rez attachment 56fceee2-4bd3-4912-8df7-ea2295bae716
08:48:41 - [DATASNAPSHOT]: Marking scenes for snapshot updates.
08:48:41 - [DATASNAPSHOT]: Marking all scenes as stale.
(0006923)
cmickeyb (reporter)
2008-11-05 08:22

 Regarding viewers... I have verified the problem with hippo, coolviewer and the stock SL client at various version numbers 1.20.15 through 1.21.6.
(0006924)
cmickeyb (reporter)
2008-11-05 08:38

 Back on the child agent/root agent issue.

I did another test this morning based on some observations from others. If I log in (initial login NOT teleport) to a region that uses SQLite for local storage (simulator version 7037), I can change my appearance and it persists.

If I log in (again, initial login NOT teleport) to a region that runs MySQL for storage, changes to my appearance do not persist. Further, if I log in to a MySQL region and teleport to the same SQLite region, changes made while in the SQLite region do not persist. The MySQL region is running 7091, but we saw the same behavior with 7037.

My hypothesis at this point, based on the differences in the log messages, is that for some reason, the MySQL regions (which, other than the storage use identical configurations) the wearables request is ignored because of the child/root agent issues.
(0006996)
StrawberryFride (reporter)
2008-11-07 13:08

 This sounds like the exact same problem we have on MSSQL - the code to persist appearance is never being run (I stuck in logging statements to check) - the message on the console consistently says "avatar is child agent" from all neighbouring sims hence that call to update the database isn't happening. Will investigate - it's a major nuisance for all our grid clients at the moment.
(0006997)
cmickeyb (reporter)
2008-11-07 13:25

 Just wanted to capture a couple more observations...

I'm running with multiple regions on the simulator. It turns out that on (what appears to be) exactly one of the regions I can set appearance and it works but only if I log into that region directly. I can never set appearance (meaning make changes that persist across logins) after a teleport between regions. In each case, I get the child agent message. And what's more it appears that the one region where appearance can change is different for each avatar.
(0007104)
justincc (manager)
2008-11-13 13:32
edited on: 2008-11-13 13:33

 May be fixed by r7284, with many thanks to awebb. Would you believe this could be a one word fix (the avatar factory module was shared between scenes when it shouldn't have been - the last scene to register would end up in its member variable (which may be the wrong one depending on which region you are in).

- Issue History
Date Modified Username Field Change
2008-10-27 08:38 cmickeyb New Issue
2008-10-27 08:38 cmickeyb SVN Revision => 6977
2008-10-27 08:38 cmickeyb Run Mode => Standalone (Multiple Regions) , Grid (Multiple Regions per Sim)
2008-10-27 08:38 cmickeyb Physics Engine => ODE
2008-10-27 08:38 cmickeyb Environment => Mono / Linux32, .NET / Windows32
2008-10-27 08:54 cmickeyb Note Added: 0006614
2008-10-29 13:22 justincc Status new => resolved
2008-10-29 13:22 justincc Resolution open => fixed
2008-10-29 13:22 justincc Assigned To => justincc
2008-10-29 13:22 justincc Note Added: 0006657
2008-10-29 13:36 cmickeyb Status resolved => feedback
2008-10-29 13:36 cmickeyb Resolution fixed => reopened
2008-10-29 13:36 cmickeyb Note Added: 0006660
2008-10-29 13:52 justincc Note Added: 0006663
2008-10-29 14:30 cmickeyb Note Added: 0006665
2008-10-30 07:35 justincc Note Added: 0006685
2008-10-30 21:46 nlin Issue Monitored: nlin
2008-11-04 14:54 justincc Note Added: 0006906
2008-11-04 19:24 cmickeyb Note Added: 0006911
2008-11-04 19:29 cmickeyb Note Added: 0006912
2008-11-04 22:04 nlin Note Added: 0006913
2008-11-05 00:54 Orion_Shamroy Note Added: 0006914
2008-11-05 00:54 Orion_Shamroy Issue Monitored: Orion_Shamroy
2008-11-05 08:22 cmickeyb Note Added: 0006923
2008-11-05 08:38 cmickeyb Note Added: 0006924
2008-11-07 13:08 StrawberryFride Note Added: 0006996
2008-11-07 13:25 cmickeyb Note Added: 0006997
2008-11-07 14:19 justincc Relationship added duplicate of 0002574
2008-11-13 13:32 justincc Status feedback => resolved
2008-11-13 13:32 justincc Resolution reopened => fixed
2008-11-13 13:32 justincc Note Added: 0007104
2008-11-13 13:32 justincc Note Edited: 0007104
2008-11-13 13:33 justincc Note Edited: 0007104
2008-11-14 05:48 Orion_Shamroy Issue End Monitor: Orion_Shamroy
2008-12-22 07:45 cfk Status resolved => closed

Mantis 1.1.1[^]
Copyright © 2000 - 2008 Mantis Group
Powered by Mantis Bugtracker