Current Project: HUD7
Issue ID# 176 | One previous trigger of issue #159 causes a persistent wrong message for Dom on each collar-attach. | |
Status: Completed | Version: 7.1.7 | Priority: 3 |
Assigned to: Lulu | Submitted by: Miriam Himanez | Attached file: |
Type: Bug |
Submitted: 24/02/2016 13:49:29 PST |
Last Update: 14/03/2016 01:29:34 PDT |
Description: 1. Attach your sub's gear (or let her attach it) making sure some parts going to already occupied attachment-points but take care not to share the collar's attachment-point (at least not in the same "wrong" sequence) to avoid the collar itself getting directly affected by issue #159 too. 2. Lock all the gear and let her relog. (This procedere will trigger issue #159 then.) 3. Unlock her collar and detach it (or let her detach it). 4. Attach it again after a while (or let her attach it). What should happen: Just collar-attach, without any message coming up at all. (At least no message as long as issue #167 isn't fixed yet!) What actually happens: Dom receives a wrong message about re-rez being completed in private. This message usually occurs after accidental/illegal detach. It will continue to come up whenever the collar is being attached until a HUD-restart has been made finally. |
Note ID# 740:
User: | Miriam Himanez | Submitted: | 24/02/2016 | ||
Last time I experienced this was yesterday after doing login-tests while already using the special Beta 1. (In which the wrong Owner-messages triggered by issue #159 have been disabled!) |
Note ID# 748:
User: | Miriam Himanez | Submitted: | 25/02/2016 | ||
After doing login-tests with the new Beta 2 today, this issue hasn't occured afterwards. Maybe it's already fixed by the changes? I'll keep monitoring this. |
Note ID# 749:
User: | Miriam Himanez | Submitted: | 25/02/2016 | ||
Sorry for my last comment. I posted it rashly. Did some attachs and detachs of the collar afterwards and had to realize that the issure is still here. Maybe the wrong message didn't come up just one single time for some reason...or I even just have overseen it. |
Note ID# 760:
User: | Lulu | Submitted: | 08/03/2016 | ||
Hey Miriam, I can't seem to repro this, as I have difficulty getting the detach bug. Is it possible for you to trigger this bug (i.e. re-rez message) and then tell me the SLT when it happened so I can check the logs? |
Note ID# 761:
User: | Lulu | Submitted: | 08/03/2016 | ||
Hey Miriam, I can't seem to repro this, as I have difficulty getting the detach bug. Is it possible for you to trigger this bug (i.e. re-rez message) and then tell me the SLT when it happened so I can check the logs? |
Note ID# 762:
User: | Lulu | Submitted: | 08/03/2016 | ||
Hey Miriam, I can't seem to repro this, as I have difficulty getting the detach bug. Is it possible for you to trigger this bug (i.e. re-rez message) and then tell me the SLT when it happened so I can check the logs? |
Note ID# 766:
User: | Lulu | Submitted: | 08/03/2016 | ||
Updated status to In Progress from New. Assigned to Lulu. |
Note ID# 772:
User: | Miriam Himanez | Submitted: | 09/03/2016 | ||
Hi Lulu. 🙂 I tested it out today. At first I had problems to trigger the bug again, too. (Possibly of some condition having changed between Beta 1 and Beta 2?) Anyhow I managed to trigger it on the first trial after having added the collar to an additional attachment. 09.03. - SLT: 16:14 login 16:16 collar unlocked and removed 16:16 collar worn again and re-rezz-message for Dom triggered ... 17:32 collar worn again and re-rezz-message for Dom triggered ... 17:47 collar worn again and re-rezz-message for Dom triggered 17:50 collar removed 17:51 collar worn again and re-rezz-message for Dom triggered ... If you need the complete protocol, just tell me please. |
Note ID# 781:
User: | Lulu | Submitted: | 14/03/2016 | ||
Updated status to Completed from In Progress. |
Note ID# 782:
User: | Lulu | Submitted: | 14/03/2016 | ||
Thanks Miriam, for the awesome repro. Fixed in 7.2-beta. |