[Archived - Nums]

Posted by “Drosselmeyer” on April 11, 2024.

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!

Posted by “Drosselmeyer” on March 08, 2024.

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

Posted by “Drosselmeyer” on March 08, 2024.

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

Posted by “Weyume” on March 08, 2024.

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).

Posted by “Nums” on March 07, 2024.

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

Posted by “Nums” on March 07, 2024.

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.

Posted by “Drosselmeyer” on March 07, 2024.

@Epic3D​, You say you tried exporting Cal3d files and the issue still occurred? Can you send those files to [email protected]? Also, if you have examples of FBX files that work and/or don't work, could you send those also? Thanks!

Posted by “Drosselmeyer” on March 07, 2024.

@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!

Posted by “Epic3D” on March 02, 2024.

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.

Posted by “Nums” on March 02, 2024.

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

Posted by “Epic3D” on March 02, 2024.

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.

Posted by “Nums” on March 02, 2024.

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.

Posted by “Nums” on March 02, 2024.

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.

Posted by “Drosselmeyer” on March 01, 2024.

Thanks. That rules out one of my concerns.

Posted by “Nums” on March 01, 2024.

Not currently. Might try it once the revised skeleton is released though