When the bone and mesh have the same name, whether R15 or not, the mesh becomes the bone and the origin is the pivot point. That’s why so many people in this thread had weird deformations.
I had a tiny tiny cube correctly labelled left hand, just to be sure. The pivot point was the torso, which was the origin of the part.
How does Lola manage to keep her RootPart in her character when uploaded with the plugin?
My custom import (a different character) with the exact-same rigging name convention has the RootPart all the way out in space / not near the imported character, sort of like this (to provide an example):
Any help would be appreciated.
the rootpart is generated at 0,0,0 in blender.
Ah that must be why, the avatar I am exporting is not at the root, so I will try that.
Alternatively, I will try forcefully repositioning the root in studio while maintaining the bone positions.
Ho ahead, but exported animations will be messed up with the force reposition method if im not mistaken.
I’m going back to the original idea that triggered my current problem. I’m trying to split up my animations now.
“any priority will overlap if there are no keyframes assigned to a certain bone”
Unfortunately, the animation importer/editor (or blender, I’m not sure which) assigns keyframes to all bones, all frames. The editor portion of the plugin is not equipped to handle this. It seems like an absolute train wreck…
Edit: looks to be a failure of Blender, circa 2017. No solution available. Roblox could bypass this with a way to select multiple tracks and either delete selected or extract selected into new animation.
Somehow i was clicking to check articles again but page didn’t exists
This is where i clicked
now i ended up with
now i’m confused and i want to check what’s S15 requirements please bring it back
OK, it took a couple days, but I solved it. In order to bypass the FBX issues caused by Blender, I had to build an animation splitter plug-in.
I didn’t even realize I had this skill…
This gave me access to just the animation in the left arm, and loaded it as a core animation, which brought the arm out of the T pose for the default jump… This might even look good once I replace that animation, which apparently makes arms flap in the breeze.
But for now, I have defeated the beast! Wow, that was painful… I hope Roblox has some better tools coming for skinned meshparts and animations. I have tons of ideas, but no access to those discussions.
Sorry for the really late reply, I didn’t see this post and didn’t know what change has been made that was messing up my imports. I assume it is related to this, as this affects something that is somewhat similar to what I assume 3D clothing will be like in function. I’m not too sure if it is related to the same exact update however, but probably, in some capacity.
I can’t post in #bug-reports so I made a post in #help-and-feedback:art-design-support :
Custom rig importing with Avatar Importer is broken in recent update (causes floating eyes?) - Help and Feedback / Art Design Support - DevForum | Roblox
In short, the same file I have uploaded just days prior started behaving strangely, as when I uploaded it again, the eyes were floating.
(Screenshot from my post):
I assume this is related to the 3D clothing updates, since the eye is a single mesh with a few faces, facing outwards, like how I assume 3D clothing will be like. Oddly enough when I made some more of these types of meshes as an example (just duplicated the topology of the head and other parts of the body, then separated them to a different object) then they didn’t float. Only if I duplicated and did this with the vertices of the eyelids did it happen. So it’s probably related to some complicated vertex data stuff that I don’t understand.
I later figured out a workaround, which was to add a lot more vertices to the eyes. Because I noticed if I added just a few more, then the eyes would float a bit closer to the head. So going off that logic, I added a lot more vertices. I assume this works on some form of a weight based system. I actually made a complete(-ish) eyeball with a bit more vertices and it worked, now it is at the place where it’s supposed to be when I import.
On the bright side of things, now I can make the eyes rotate.
The change I mentioned was only enabled for a couple of hours that morning, so if this issue persisted longer than that, it is something unrelated. I will share your post with the importer group, maybe they will have an idea.
Floating parts for me have always been a function of part origins. Now everything gets the same origin as the rig (which also becomes the HRP).
I was thinking that too in retrospect but then how did adding more vertices fix it? And setting the eyes’ origin to gemoetry/to world origin didn’t actually change anything either when I imported them. They are literally just not where they are supposed to be on import, unless I add a bunch more geometry to them to weigh them down.
Also for some reason for me the HRP is still given at the world origin instead of the center of the rig, so I don’t think that update is quite out yet.
And when I select them, the highlight box (or their actual position) is at the right place, but the mesh itself is just somehow messed up. If I move their bone they snap back to place but their motor6D breaks.
Either way doesn’t matter anymore since I fixed it by the method I described above.
By the way never really posted a demo of what I’m doing here, so here’s a short recording. Going to be some sort of a fighting game demo since I don’t have much free time, but I have plans to make some kind of an RPG later on. Although the whole idea of mesh deformation characters might not be that groundbreaking of an idea on Roblox by that time.
Also learned scripting just for this, or more like while messing around with it, pretty fun so far.
Cool stuff that it has, as of now:
(Also besides other stuff but these are what are mainly related to skinned meshes and I’m gonna keep this related to the topic)
So yeah if anyone needs some help then feel free to ask, I have gone through a lot of trial and error to figure these out and now I have some experience.
One main thing that is still a problem is hitboxes, since they don’t really move with animations. But I do have some things in mind, so I will report back when I get to messing around with them.
Edit: Since I still see people stumbling into this post once in a while, I’d like to note that I attempted doing this again in favor of using layered clothing and for that I remade the whole thing. Basically you still need a character that follows the r15 schema (15 separate limbs) but you can skin it so that it bends all the same. If you average the normals along the cuts then there won’t be visible seams between the bodyparts either.
Is there a way to make skinned mesh ragdoll?
Is it still not possible for Implemented IK? wouldn’t mind animating in roblox but without the option to add my IK, I can’t, Seems the only workaround rn is just animating in blender?
I’ve ran into an issue with the skinned meshes not rendering or their animations not playing on the client when there’s around 50+ of them in the world. This seems like a bug since the memory stays almost the same regardless of whether there are 50 meshes or 500.
Video: Meshes don’t render in viewports. When the menu is closed, the meshes in the bottom icons don’t render back in
Video: Spawning a bunch of meshes at once stops the animations of meshes that were already in the world and new meshes don’t become visible until after a while
Do you have a repro file you can share privately? Or repro instructions if this happens in a live experience? Thanks.
More flickering happening, but this one is interesting…
My character model, when viewed through studio, is jittery. I assumed this was because I had some collision issues. However, when published and played, it is clear that the jitters are due to returning to the T pose for a split second, for what feels like every single frame. The T pose is never visible on studio.
I caught it on camera. Idle animation is running. I don’t know how to capture video while playing with a published game. It looks awful, and is absolutely the cause of the jitters.
anyone know how I’d predetermine the location of the humanoidrootpart? Whenever I import a mesh as r15 into roblox, the humanoid root part is always at the feet, no matter what, which brings issues because we can’t move it as it also moves the rig. I use blender.
