This issue just got absolutely terrible for me.
4/5 attempts to start a test spawns me in r15 instead of r6.
This issue just got absolutely terrible for me.
4/5 attempts to start a test spawns me in r15 instead of r6.
You can try using a StarterCharacter R6 rig and loading their character appearance in manually using a script, that’s what I did in my case to avoid any issues this could cause in the future
i found a solution, uninstall and re install studio
Hello, are you using teamcreate?
I have gotten the issue while using team create. (and while not using it if I remember correctly)
Additionally it only happens when you click Play (f5) or Play Here (No keybind)
As soon as you reset your player reverts back into r6.
I am sure you have already found some of this info from other but I just wanted to relay it back in case you didn’t
Hi, just to update everyone:
Our previous fix ended up breaking other people’s experience, so we’ve hopefully made another fix that’ll go live next week. Sorry for all the trouble
Oh, thanks for the news, because some of my scripts broke ( support R6 and R15; only R6 was working), and I was wondering what it could be.
Yes, I am using team create with a friend.
By default, the Playtesting Session in Studio spawns R15 characters at the beginning when the system haven’t realized the actual Default Rig Type yet.
To fix this, you can simply delay the the character spawning.
game.Players.PlayerAdded:Connect(function(plr)
task.wait(0.5) -- Anytime is ok as long as enough time is given to the system
plr:LoadCharacter()
end
Do you see it in play solo or team test or both?
I see it in play solo. Never tried in teamtest tho.
still happening, back then i released an update in one of the games i work in and the game somehow created a server that was r15 while the rest of the servers were r6
This is still happening… I can’t test my animation with r6 on my character. Playing it on Play Solo. Disabling the team create fixes it.
Hi all! We released a fix this morning that we hope will mitigate the issue. If you’re experiencing this issue on TeamCreate, you may need to leave and rejoin so that the TeamCreate server shuts down and can update with the fix.
Took you guys plenty of time
Tested it, no issues so far, ill mark it as solution for the post, maybe others will share their experiences too
Sorry for the long wait TT. Thanks for all your patience!
Hello!
Could I get what studio version you’re on, what place id / universe id you’re using, and the value of Workspace.MeshPartHeadsAndAccessories?
Place ID: 103750982012241 (Private) (Was created on 2/5/2025)
Workspace.MeshPartHeadsAndAccessories = Default
UPDATE:
Seems like it happens only on freshly created placed.
Seems to be fixed after: