Current Project: HUD7
| Issue ID# 153 | False messages of detached gear on any login | |
| Status: Closed | Version: 7.0.12 | Priority: 3 |
| Assigned to: | Submitted by: Miriam Himanez | Attached file: False_messages_of_detached_gear_on_any_login.png |
| Type: Bug |
Submitted: 21/01/2016 17:18:54 PST |
Last Update: 22/01/2016 15:31:12 PST |
|
Description: 1. Wear the whole gear and lock everything including main HUD and activate RLV-relay. 2. Relog. 3. What should happen: Just login and messages about the HUDs being locked. What actually happens: False messages of detached gear. (Please view attached file.) I never experienced this with HUD6. It appeared randomly since I switched to HUD7. (I started with 7.0.8 I believe.) Since HUD7.0.10 I get this on any login, no matter wether parts of the gear share attachment points or not. Actually nothing gets detached. (With 7.0.8 it sometimes happened.) All this just happens on login, never after teleporting. I took a replacement before sending this report to make sure that the issue isn't caused by damaged parts. |
||
Note ID# 657:
| User: | Miriam Himanez | Submitted: | 21/01/2016 | ||
| Correction: Exchange 7.0.8 with 7.0.7. | |||||
Note ID# 658:
| User: | Miriam Himanez | Submitted: | 21/01/2016 | ||
| I tested out doing a login with Firestorm. (Normally I'm using Singularity.) The gear's behaviour was worse than before. Except the collar any other part was detached and re-rezzed, some parts even two times. Got a script error (Too many http-requests) as well. Relogged in Singularity again afterwards - same behaviour than in Firestorm suddenly, possibly caused by the Firestorm-bridge which is surplus in Singularity but not detached automatically at login. Detached it, did another login and experienced the aboriginal behaviour which I described in the bug-report itself. | |||||
Note ID# 663:
| User: | Lulu | Submitted: | 22/01/2016 | ||
|
Ah, those messages. What happens during log-on or TP is this... 1. As your avie begins rendering in world, the sim will start retrieving info about worn attachments. Depending on overall SL asset-server and sim lag, the time for this will vary. 2. Besides the lag issue, there is an annoying SL bug that would actually detach your attachments once rendered. However, lately, they have created a workaround where they would immediately re-attach any such attachment. 3. The LULU HUD waits a while (something like 15 secs) before checking whether your locked Cuffs are still there. (There are ways to try to cheat and detach locked Cuffs and this check is necessary to prevent that.) 3. In your case, during this delayed check, has detected that several things (Collar, Cuffs, Gag) are not attached at that moment - probably due to point 1 or 2. So it informs you, in case SL doesn't successfully re-attach the gear (see point 2), the Alarm will trigger after 30 secs. 4. But if you do a manual check and everything is there, you're good to go. Your gear will respond when the HUD does a second check later. I'm going to close this for now, but if you have further comments or ideas, feel free to add it here. |
|||||
Note ID# 664:
| User: | Lulu | Submitted: | 22/01/2016 | ||
|
Updated status to Closed from New. |
|||||
Note ID# 666:
| User: | Miriam Himanez | Submitted: | 22/01/2016 | ||
| I could live with this messages but the gear sends owner messages because of detach on login as well and that's very annoying. There must be a workaround for this because HUD6 never behaved that way. | |||||
Note ID# 667:
| User: | Lulu | Submitted: | 22/01/2016 | ||
|
I see, that's not supposed to happen, unless the second check has failed to find the relevant Collar/Cuffs/Gag. The next time this happens (i.e. your Owner gets notified wrongly), can you update this immediately so I can check the logs and see what's up? You're welcome to start a new bug report then too. |
|||||
Note ID# 668:
| User: | Lulu | Submitted: | 22/01/2016 | ||
| Oh, and don't wait to send in the bug report/update this as it's easier for me to look things up if it's near the end of the log (i.e. there aren't many more events/activity after the login/TP that generates more entries) rather than lost somewhere in the middle somewhere. | |||||
Note ID# 669:
| User: | Lulu | Submitted: | 22/01/2016 | ||
| Oh, and don't wait to send in the bug report/update this as it's easier for me to look things up if it's near the end of the log (i.e. there aren't many more events/activity after the login/TP that generates more entries) rather than lost somewhere in the middle somewhere. | |||||
Note ID# 670:
| User: | Miriam Himanez | Submitted: | 22/01/2016 | ||
| Yes, I will open a new report as you suggested, immediately after the messages have shown up. | |||||