Went to the Classic Client's dressing room to put on this unisex female Tuft product on my Male avi.
Put on Coffin Phone and Tufts were removed.
Fetched derivable parent mesh of the Tuft & edit/open my coffin phone to open in the Classic Client's create mode to view which body pattern # they were both using.
Noted none were the same, but had a hunch that maybe since the usual numbers cap off after 100, then maybe the system got confused when it saw 226 and clipped the extra digit in front.
Changed 26 to 126 Tufts in create mode and it allowed my 226 coffin phone to stay instead of remaining blocked like suspected.
Reverted 126 back to 26, and it was good, I guess resetted it?
I closed the tests and msg'd the coffin phone mesher to share my confusion, (this would be @LestatDeLioncourt )
Dressing Room was still the same issues. I tried to will it in place, but kept on removing itself lol.
I gave up, made a choice of which to currently wear, and as I was wearing the Tufts and clicked to put on the Phone, expecting the phone to remove the Tufts, I impatiently did notwait for it to finish loading as I clicked on Shop to go find something, and behold... they were both together at last o,o
Dressing room was still open so I switched back to quickly save them together.
---
--- This sort of reminds me of how @CheeseBurgerMelt was telling me that when we include unisex female items into male bundles, that it resets the category for those items and allows the customer receiving the male bundle to wear the unisex female items as easily as any other item with their male avi outside of the classic client.
Thx for anything!
Dia
0 Votes
5 Comments
Sorted by
C
Communityposted
3 months ago
Admin
Posted by “DiamondBones” on November 10, 2022.
[Archived]
Some staff and discussion mods have been advising us to log back into the Classic Client to put on unisex items, save our outfits, then log back into the new imvu to put them on in order to override the compatibility issues, that's why I went to the classic client. But this case isn't a unisex issue. The problem was that it misidentified 26 & 226 body ids as the same.
I'd put one on, and it would remove the other product.
I opened the products in create mode to view which # they shared, and they didn't.
As a test, I changed the 226 to another number, and it worked together, meaning the system thought it was the same as 26.
My guess was that since imvu capped our ability to change those numbers after 100 (unless we use the debug tabs), that the system has issues recognizing individual numbers above the cap, like this case, confusing 26 and 226, making them not able to be worn together, clipping eachother off. And I was able to slap this issue by interfering with it before it fully loaded onto my avatar in my dressing room/shop, and also reset it in create mode by kicking it a few times over and over again. I dunno, thought this incident would had been useful to share instead of keeping it to myself.
@Drosselmeyer Sorry for the confusion though! I've been told over-writing like this is hard to keep track of x.x I'm still working on my communication skills!
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “LestatDeLioncourt” on November 08, 2022.
[Archived]
Hey @Drosselmeyer I believe she is using the Classic Client :)
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Drosselmeyer” on November 07, 2022.
[Archived]
@DiamondBones I had a look and as near as I can tell this is an issue of male and female products cannot be worn at the same time. Both of these products are derived from clothing not accessories and neither is set to unisex (80, 191) and therefore you cannot where them together. Is there something I am missing?
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “LestatDeLioncourt” on November 05, 2022.
[Archived]
Great information @DiamondBones
As far as I know the Mesh Channels are not supposed to cause this issue unless the exact Body Part ID is used on two products.
Perhaps Staff can shed some light on these. I will test more products with you as time allows. If someone else can give some input
on this, it would be appreciated.
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “DiamondBones” on November 05, 2022.
[Archived]
Added Note:
Yes, when I opened the #26 Tufts in create mode, it was removing my #226 coffin phone, just like in my dressing room. I used the saved outfits, so had the drop down msg tell me exactly that the phone was not compatible.
0 Votes
People who like this
Delete Comment
This post will be deleted permanently. Are you sure?
Posted by “DiamondBones” on November 05, 2022.
[Archived]Body Pattern ID # confused 26 & 226 as the same, then resolved when I interrupted the loading:
Link to Tuft Mesh: #26
https://www.imvu.com/shop/product.php?products_id=43309357
Link to Coffin Phone: #226
https://www.imvu.com/shop/product.php?products_id=61072407
Events as transpired:
---
--- This sort of reminds me of how @CheeseBurgerMelt was telling me that when we include unisex female items into male bundles, that it resets the category for those items and allows the customer receiving the male bundle to wear the unisex female items as easily as any other item with their male avi outside of the classic client.
Thx for anything!
Dia
0 Votes
5 Comments
Community posted 3 months ago Admin
Posted by “DiamondBones” on November 10, 2022.
[Archived]Some staff and discussion mods have been advising us to log back into the Classic Client to put on unisex items, save our outfits, then log back into the new imvu to put them on in order to override the compatibility issues, that's why I went to the classic client. But this case isn't a unisex issue. The problem was that it misidentified 26 & 226 body ids as the same.
I'd put one on, and it would remove the other product.
I opened the products in create mode to view which # they shared, and they didn't.
As a test, I changed the 226 to another number, and it worked together, meaning the system thought it was the same as 26.
My guess was that since imvu capped our ability to change those numbers after 100 (unless we use the debug tabs), that the system has issues recognizing individual numbers above the cap, like this case, confusing 26 and 226, making them not able to be worn together, clipping eachother off. And I was able to slap this issue by interfering with it before it fully loaded onto my avatar in my dressing room/shop, and also reset it in create mode by kicking it a few times over and over again. I dunno, thought this incident would had been useful to share instead of keeping it to myself.
@Drosselmeyer Sorry for the confusion though! I've been told over-writing like this is hard to keep track of x.x I'm still working on my communication skills!
0 Votes
Community posted 3 months ago Admin
Posted by “LestatDeLioncourt” on November 08, 2022.
[Archived]Hey @Drosselmeyer I believe she is using the Classic Client :)
0 Votes
Community posted 3 months ago Admin
Posted by “Drosselmeyer” on November 07, 2022.
[Archived]@DiamondBones I had a look and as near as I can tell this is an issue of male and female products cannot be worn at the same time. Both of these products are derived from clothing not accessories and neither is set to unisex (80, 191) and therefore you cannot where them together. Is there something I am missing?
0 Votes
Community posted 3 months ago Admin
Posted by “LestatDeLioncourt” on November 05, 2022.
[Archived]Great information @DiamondBones
As far as I know the Mesh Channels are not supposed to cause this issue unless the exact Body Part ID is used on two products.
A standardized set of product "Channels" was devised many years ago to prevent these issues. Meshers should use the list as
a guideline.
Perhaps Staff can shed some light on these. I will test more products with you as time allows. If someone else can give some input
on this, it would be appreciated.
0 Votes
Community posted 3 months ago Admin
Posted by “DiamondBones” on November 05, 2022.
[Archived]Added Note:
Yes, when I opened the #26 Tufts in create mode, it was removing my #226 coffin phone, just like in my dressing room. I used the saved outfits, so had the drop down msg tell me exactly that the phone was not compatible.
0 Votes