You guys changed something about classic because I can no longer submit accessory meshes with custom skeletons. I posted an issue a few weeks back about it. Not realizing things were way more messed up.
My best guess is that if a file is recompressed, or whatever it is you guys do on your end, it botches the file. I say this because there is no problem with the file until you upload it. In which afterwards it is now messed up. It would also make sense as to why my 4+ year old files randomly are getting messed up. Perhaps they were edited on your end.
Right now, I cannot submit files that I submitted just a few months back. Even when I submit a fresh, brand new file, the skeleton is now messed up after IMVU does its thing to it. This is really bad.
I should note this is specifically a Classic Issue.
0 Votes
31 Comments
Sorted by
C
Communityposted
3 months ago
Admin
Posted by “Drosselmeyer” on April 11, 2024.
[Archived]
Hey All, Just following up to see if anyone has run into this rotated/broken skeleton issue recently. We believe the issue to be resolved, but wanted to make sure no new occurrences have shown up. Remember that products that were affected by the bug need the original working skeleton reimported and submitted. The full explanation and fix it steps can be found here Broken Skeleton Issue Resolved. Our fix is only for newly submitted products since we rolled back the change that caused the issue. Thanks!
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Drosselmeyer” on March 08, 2024.
[Archived]
Hi @Weyume, We have identified the source of issue with the broken skeletons and have steps to fix any product that you have submitted that is exhibiting the issue. The full explanation and fix it steps can be found here Broken Skeleton Issue Resolved
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Drosselmeyer” on March 08, 2024.
[Archived]
Hello All, We have identified the source of issue with the broken skeletons and have steps to fix any product that you have submitted that is exhibiting the issue. The full explanation and fix it steps can be found here Broken Skeleton Issue Resolved
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Weyume” on March 08, 2024.
[Archived]
Hi! Are there any updates surrounding this issue? I'm experiencing the same thing. I'm using the toolkit on Windows 11. Used both female and female 1.5 to make the accessory mesh. That whole process is fine, even importing into IMVU is fine. The issue arises when I upload the mesh because it disappears in IMVU Classic. Upon checking the mobile app and IMVU next, I do see them but they're not visible in IMVU Classic. It's either that or I upload the accessory mesh and it's fine once I upload it but when it passes peer review, the mesh suddenly hangs on the floor (as pictured).
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Nums” on March 07, 2024.
[Archived]
Well I should add, it makes sense why the Studio version in this case works because when you go to edit it (from uploading in Classic) it gives you an unencrypted file, so of course it works I guess. I didn't realize you guys made that a thing. It was a feature I was asking for awhile ago which is nice to have to edit files with
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Nums” on March 07, 2024.
[Archived]
I did more digging with the products that are messed up. Another interesting piece of information I found is that Classic Client and Studio are sent different files. The reason these files open in Studio fine is because Studio is sent a copy of the file that is correct. That's it. Why can't Classic be sent the same copy of a correct file? I can literally take the correct copy Studio is given and import it into Classic and it fixes everything.
The reason this is proven is this example:
Open a broken product in Studio and Classic
Take the XSF loaded in each client and swap them
You've now traded attributes. Classic will be working and Studio will be broken. So it proves the two clients are sent different files. (I mean just look at them in notepad too) Both files appear to function the same in each client but Classic is simply being sent a bad file.
However if you upload a correct copy of the file in Classic (the Studio version) it will send both clients the Studio version from here on out and everything just works fine.
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Drosselmeyer” on March 07, 2024.
[Archived]
@Epic3D, You say you tried exporting Cal3d files and the issue still occurred? Can you send those files to studio@imvu.com? Also, if you have examples of FBX files that work and/or don't work, could you send those also? Thanks!
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Drosselmeyer” on March 07, 2024.
[Archived]
@Nums, I just sent you an email requesting more information. If you see this first could you have a look and give me a reply. Thanks!
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Epic3D” on March 02, 2024.
[Archived]
I think that is my problem I'm importing the meshes using the old cal3D way with separate .xsf and .xmf files. I attempted similar steps this time pasting the .xsf file into the folder directly instead of browsing for it in the drop down box but unfortunately the mesh still fell off the avatar after I submitted the product. I might try the FBX way for now as a work around. I hope this gets resolved soon though. I appreciate your help thank you.
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Nums” on March 02, 2024.
[Archived]
Do you import via FBX? Let me break down my exact steps.
Export from 3ds Max in FBX format.
Import the FBX into Studio
Save the studio file in the top right, it's the only way to get the file into the folder to access
Grab "RootNode_AttachmentRoot.xsf" (yours will probably be named differently, but it's the .xsf file) and copy/paste it into Classic create mode folder (you could alternatively just upload using Studio potentially, but being a little defiant here and using Classic still)
That's all I did personally. If you aren't using FBX, I'm unsure of the steps you should take
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Epic3D” on March 02, 2024.
[Archived]
This post looks promising but I cant seem to get this to work maybe I'm missing something. I uploaded the working .xsf file into studio. It spits out a .compressed file in the ".compressed_data" folder. I take that file and remove the .compressed from the end of the file name, then I submit that .xsf into the skeletal variables field in classic and hit apply changes and it doesn't work for me.
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Nums” on March 02, 2024.
[Archived]
Okay so maybe I'm slow, but I saw no one mention it. If you upload the file in Studio it works fine.
I imported the file into Studio, grabbed the encrypted file, pasted it into the Classic Create and uploaded it from there. So it would seem it's just the encryption when sent from Classic into the servers is at fault since Studio's works fine. And uploading and already processed file doesn't flag it to be processed again.
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Nums” on March 02, 2024.
[Archived]
If you guys ever need more example XSF files, feel free to ask as well. I know I sent a few already but I could send more if needed.
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Drosselmeyer” on March 01, 2024.
[Archived]
Thanks. That rules out one of my concerns.
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Nums” on March 01, 2024.
[Archived]
Not currently. Might try it once the revised skeleton is released though
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Drosselmeyer” on March 01, 2024.
[Archived]
@Nums Are you using the IMVU Studio Toolkit for 3ds Max?
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Epic3D” on February 29, 2024.
[Archived]
I can say with 100% certainty the .xsf files are being modified after submission at least when it comes to the classic client. I haven't tried head attachments but for a choker I was making (neck02) it would immediately drop off the avatar after I hit submit. However when viewed outside of classic it would look normal.
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Polystyrene” on February 29, 2024.
[Archived]
Don't know if it helps but I'm not having this issue with head attachment products (derived from glasses spice/glasses king so not needing to replace the xsf file).
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Nums” on February 28, 2024.
[Archived]
Let me clarify when I say custom skeleton, it's the exact Master Skeleton exported from 3ds Max, that's why the avatar in picture one looks normal. It's not actually a custom skeleton with added bones in it. It's just not the Female04_Anime01_SkeletonMASTER file being used is all.
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Nums” on February 28, 2024.
[Archived]
@Drosselmeyer Not sure if this helps any, I saw you mention it's specifically avatar attachments. But even when importing a custom skeleton derived from PID 80, the avatar still explodes after imvu servers process the file. Seems like any skeleton? Maybe some additional info, I'm using 3ds Max. Not sure if it makes a difference anywhere. Just trying to help where I can so I can fix a few products of mine that broke.
Product: 66766551
Pre Upload
Post Upload and Re Opened in IMVU
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Polystyrene” on February 28, 2024.
[Archived]
Thank you!
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Drosselmeyer” on February 27, 2024.
[Archived]
@Polystyrene Ugh. :( So sorry. I will elevate the urgency of this issue. Thanks.
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Polystyrene” on February 27, 2024.
[Archived]
Glad to see this is being looked into. I'm having the same issue, four products I submitted this week have their skeletons screwed up. PIDs are 66747449, 66747449, 66747449, 66747460.
This is how they should look:
This is how they appear in Classic:
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Nums” on February 27, 2024.
[Archived]
Thanks for taking a look into it!
0 Votes
C
Communityposted
3 months ago
Admin
Posted by “Drosselmeyer” on February 27, 2024.
[Archived]
@Nums, Just to give you an update, I have been able to create a reproducible PID on my own that demonstrates the bug and it looks like it has to do with bone rotations getting altered between submit -> server -> edit and the PID never has to be edited in Studio as you mentioned. We are investigating and I will post a follow up here when there is more information.
0 Votes
People who like this
Delete Comment
This post will be deleted permanently. Are you sure?
Posted by “Nums” on February 26, 2024.
[Archived]IMVU and skeleton file compression?
You guys changed something about classic because I can no longer submit accessory meshes with custom skeletons. I posted an issue a few weeks back about it. Not realizing things were way more messed up.
My best guess is that if a file is recompressed, or whatever it is you guys do on your end, it botches the file. I say this because there is no problem with the file until you upload it. In which afterwards it is now messed up. It would also make sense as to why my 4+ year old files randomly are getting messed up. Perhaps they were edited on your end.
Right now, I cannot submit files that I submitted just a few months back. Even when I submit a fresh, brand new file, the skeleton is now messed up after IMVU does its thing to it. This is really bad.
I should note this is specifically a Classic Issue.
0 Votes
31 Comments
Community posted 3 months ago Admin
Posted by “Drosselmeyer” on April 11, 2024.
[Archived]Hey All, Just following up to see if anyone has run into this rotated/broken skeleton issue recently. We believe the issue to be resolved, but wanted to make sure no new occurrences have shown up. Remember that products that were affected by the bug need the original working skeleton reimported and submitted. The full explanation and fix it steps can be found here Broken Skeleton Issue Resolved. Our fix is only for newly submitted products since we rolled back the change that caused the issue. Thanks!
0 Votes
Community posted 3 months ago Admin
Posted by “Drosselmeyer” on March 08, 2024.
[Archived]Hi @Weyume, We have identified the source of issue with the broken skeletons and have steps to fix any product that you have submitted that is exhibiting the issue. The full explanation and fix it steps can be found here Broken Skeleton Issue Resolved
0 Votes
Community posted 3 months ago Admin
Posted by “Drosselmeyer” on March 08, 2024.
[Archived]Hello All, We have identified the source of issue with the broken skeletons and have steps to fix any product that you have submitted that is exhibiting the issue. The full explanation and fix it steps can be found here Broken Skeleton Issue Resolved
0 Votes
Community posted 3 months ago Admin
Posted by “Weyume” on March 08, 2024.
[Archived]Hi! Are there any updates surrounding this issue? I'm experiencing the same thing. I'm using the toolkit on Windows 11. Used both female and female 1.5 to make the accessory mesh. That whole process is fine, even importing into IMVU is fine. The issue arises when I upload the mesh because it disappears in IMVU Classic. Upon checking the mobile app and IMVU next, I do see them but they're not visible in IMVU Classic. It's either that or I upload the accessory mesh and it's fine once I upload it but when it passes peer review, the mesh suddenly hangs on the floor (as pictured).
0 Votes
Community posted 3 months ago Admin
Posted by “Nums” on March 07, 2024.
[Archived]Well I should add, it makes sense why the Studio version in this case works because when you go to edit it (from uploading in Classic) it gives you an unencrypted file, so of course it works I guess. I didn't realize you guys made that a thing. It was a feature I was asking for awhile ago which is nice to have to edit files with
0 Votes
Community posted 3 months ago Admin
Posted by “Nums” on March 07, 2024.
[Archived]I did more digging with the products that are messed up. Another interesting piece of information I found is that Classic Client and Studio are sent different files. The reason these files open in Studio fine is because Studio is sent a copy of the file that is correct. That's it. Why can't Classic be sent the same copy of a correct file? I can literally take the correct copy Studio is given and import it into Classic and it fixes everything.
The reason this is proven is this example:
Open a broken product in Studio and Classic
Take the XSF loaded in each client and swap them
You've now traded attributes. Classic will be working and Studio will be broken. So it proves the two clients are sent different files. (I mean just look at them in notepad too) Both files appear to function the same in each client but Classic is simply being sent a bad file.
However if you upload a correct copy of the file in Classic (the Studio version) it will send both clients the Studio version from here on out and everything just works fine.
0 Votes
Community posted 3 months ago Admin
Posted by “Drosselmeyer” on March 07, 2024.
[Archived]@Epic3D, You say you tried exporting Cal3d files and the issue still occurred? Can you send those files to studio@imvu.com? Also, if you have examples of FBX files that work and/or don't work, could you send those also? Thanks!
0 Votes
Community posted 3 months ago Admin
Posted by “Drosselmeyer” on March 07, 2024.
[Archived]@Nums, I just sent you an email requesting more information. If you see this first could you have a look and give me a reply. Thanks!
0 Votes
Community posted 3 months ago Admin
Posted by “Epic3D” on March 02, 2024.
[Archived]I think that is my problem I'm importing the meshes using the old cal3D way with separate .xsf and .xmf files. I attempted similar steps this time pasting the .xsf file into the folder directly instead of browsing for it in the drop down box but unfortunately the mesh still fell off the avatar after I submitted the product. I might try the FBX way for now as a work around. I hope this gets resolved soon though. I appreciate your help thank you.
0 Votes
Community posted 3 months ago Admin
Posted by “Nums” on March 02, 2024.
[Archived]Do you import via FBX? Let me break down my exact steps.
Export from 3ds Max in FBX format.
Import the FBX into Studio
Save the studio file in the top right, it's the only way to get the file into the folder to access
Grab "RootNode_AttachmentRoot.xsf" (yours will probably be named differently, but it's the .xsf file) and copy/paste it into Classic create mode folder (you could alternatively just upload using Studio potentially, but being a little defiant here and using Classic still)
That's all I did personally. If you aren't using FBX, I'm unsure of the steps you should take
0 Votes
Community posted 3 months ago Admin
Posted by “Epic3D” on March 02, 2024.
[Archived]This post looks promising but I cant seem to get this to work maybe I'm missing something. I uploaded the working .xsf file into studio. It spits out a .compressed file in the ".compressed_data" folder. I take that file and remove the .compressed from the end of the file name, then I submit that .xsf into the skeletal variables field in classic and hit apply changes and it doesn't work for me.
0 Votes
Community posted 3 months ago Admin
Posted by “Nums” on March 02, 2024.
[Archived]Okay so maybe I'm slow, but I saw no one mention it. If you upload the file in Studio it works fine.
I imported the file into Studio, grabbed the encrypted file, pasted it into the Classic Create and uploaded it from there. So it would seem it's just the encryption when sent from Classic into the servers is at fault since Studio's works fine. And uploading and already processed file doesn't flag it to be processed again.
0 Votes
Community posted 3 months ago Admin
Posted by “Nums” on March 02, 2024.
[Archived]If you guys ever need more example XSF files, feel free to ask as well. I know I sent a few already but I could send more if needed.
0 Votes
Community posted 3 months ago Admin
Posted by “Drosselmeyer” on March 01, 2024.
[Archived]Thanks. That rules out one of my concerns.
0 Votes
Community posted 3 months ago Admin
Posted by “Nums” on March 01, 2024.
[Archived]Not currently. Might try it once the revised skeleton is released though
0 Votes
Community posted 3 months ago Admin
Posted by “Drosselmeyer” on March 01, 2024.
[Archived]@Nums Are you using the IMVU Studio Toolkit for 3ds Max?
0 Votes
Community posted 3 months ago Admin
Posted by “Epic3D” on February 29, 2024.
[Archived]I can say with 100% certainty the .xsf files are being modified after submission at least when it comes to the classic client. I haven't tried head attachments but for a choker I was making (neck02) it would immediately drop off the avatar after I hit submit. However when viewed outside of classic it would look normal.
0 Votes
Community posted 3 months ago Admin
Posted by “Polystyrene” on February 29, 2024.
[Archived]Don't know if it helps but I'm not having this issue with head attachment products (derived from glasses spice/glasses king so not needing to replace the xsf file).
0 Votes
Community posted 3 months ago Admin
Posted by “Nums” on February 28, 2024.
[Archived]Let me clarify when I say custom skeleton, it's the exact Master Skeleton exported from 3ds Max, that's why the avatar in picture one looks normal. It's not actually a custom skeleton with added bones in it. It's just not the Female04_Anime01_SkeletonMASTER file being used is all.
0 Votes
Community posted 3 months ago Admin
Posted by “Nums” on February 28, 2024.
[Archived]@Drosselmeyer Not sure if this helps any, I saw you mention it's specifically avatar attachments. But even when importing a custom skeleton derived from PID 80, the avatar still explodes after imvu servers process the file. Seems like any skeleton? Maybe some additional info, I'm using 3ds Max. Not sure if it makes a difference anywhere. Just trying to help where I can so I can fix a few products of mine that broke.
Product: 66766551
Pre Upload
Post Upload and Re Opened in IMVU
0 Votes
Community posted 3 months ago Admin
Posted by “Polystyrene” on February 28, 2024.
[Archived]Thank you!
0 Votes
Community posted 3 months ago Admin
Posted by “Drosselmeyer” on February 27, 2024.
[Archived]@Polystyrene Ugh. :( So sorry. I will elevate the urgency of this issue. Thanks.
0 Votes
Community posted 3 months ago Admin
Posted by “Polystyrene” on February 27, 2024.
[Archived]Glad to see this is being looked into. I'm having the same issue, four products I submitted this week have their skeletons screwed up. PIDs are 66747449, 66747449, 66747449, 66747460.
This is how they should look:
This is how they appear in Classic:
0 Votes
Community posted 3 months ago Admin
Posted by “Nums” on February 27, 2024.
[Archived]Thanks for taking a look into it!
0 Votes
Community posted 3 months ago Admin
Posted by “Drosselmeyer” on February 27, 2024.
[Archived]@Nums, Just to give you an update, I have been able to create a reproducible PID on my own that demonstrates the bug and it looks like it has to do with bone rotations getting altered between submit -> server -> edit and the PID never has to be edited in Studio as you mentioned. We are investigating and I will post a follow up here when there is more information.
0 Votes