Current Project: HUD7
| Issue ID# 221 | The collar's leash-menu isn't able to detect unscripted objects. | |
| Status: Completed | Version: 7.2.12 | Priority: 3 |
| Assigned to: | Submitted by: Miriam Himanez | Attached file: |
| Type: Bug |
Submitted: 30/06/2016 19:47:01 PDT |
Last Update: 10/07/2016 18:08:31 PDT |
|
Description: 1. Make sure to have some scripted and unscripted objects in reach. 2. Try to leash sub to one of them. 3. What should happen: The nearest objects should appear inside the leash-menu included affiliated buttons, no matter wether they are scripted or not. What actually happens: The HUD ignores all objects not having at least one script inside. Please note, that the leash-menu is affected by issue #220 as well, causing the HUD to ignore objects named just "Object" even if scripted. |
||
Note ID# 953:
| User: | Lulu | Submitted: | 30/06/2016 | ||
|
Hey Miriam, Same as #220, this isn't a bug, it's a feature. The HUD, by design, filters out all nameless objects so as not to clog the menu with irrelevant objects (e.g. floors, walls, or test objects). The assumption is that anything worth sitting on during playtime, would also have scripts to animate the sub! e.g. bdsm furniture, cage etc. |
|||||
Note ID# 955:
| User: | Miriam Himanez | Submitted: | 01/07/2016 | ||
|
Hi Lulu, I completely agree with you regarding the feature making it impossible to force sit onto objects simply named "Object". (Please view note #954.) Anyhow I'd like to push the focus back to the topic of this issue (leash-menu) because it seems to me, that I might have confused you a bit by posting Issue #220 and this one directly in a row. Let's have a look at the last sentence of note #953: "The assumption is that anything worth sitting on during playtime, would also have scripts to animate the sub! e.g. bdsm furniture, cage etc." I'm speaking of confusion because this statement is wrong. The force sitting-menu detects unscripted objects without any problem. (It just doesn't recognize objects named "Object.") It needs scripted objects to leash to instead and this doesn't feel correct to me. For example, why shouldn't Dom be able to leash sub to an unscripted column? It surely would look more realistic than having to choose the vendor a few metres next to it because it might be the only scripted object in reach at the moment. (Actually I found this issue because of being in a similar situation yesterday.) Today I found out a new detail too: I built a 2-prim-object, having a script inside the slave-prim and none inside the root-prim. The leash-menu ignored this object too. (I already assumed this, just wanted to test it out.) |
|||||
Note ID# 956:
| User: | Miriam Himanez | Submitted: | 01/07/2016 | ||
| I'd like to add, that I'm very fine with the HUD's capability to force-sit onto unscripted objects. (It's off-topic again -sorry- but refers to what I explained above.) | |||||
Note ID# 959:
| User: | Lulu | Submitted: | 01/07/2016 | ||
|
I see, you have a point. Another to-do! |
|||||
Note ID# 970:
| User: | Lulu | Submitted: | 10/07/2016 | ||
|
Updated status to In Progress from New. |
|||||
Note ID# 971:
| User: | Lulu | Submitted: | 10/07/2016 | ||
|
Updated status to Completed from In Progress. |
|||||
Note ID# 972:
| User: | Lulu | Submitted: | 10/07/2016 | ||
|
Fix is now live in the 7.2.13 patch. Fix pending in the 7.3 beta. |
|||||