Additional info surrounding the root cause:
Its not resolved yet, It still happens but its much harder to encounter
keeps happening to me rn, every time i play theres like a 1/2 chance of it happening, seems to only happen with one place though.
Still happening and now 100%, fix this please
still happening but im not in team create
My friend has started to recently experience this more. Solo or not.
This is still happening, And it’s annoying to keep play-testing multiple times to get the r6, as if its a chance of 1/6 or something like that.
This just happened to me. All I had to do was play test in studio and I spawned in as a r15 instead of r6.
I had this same problem a while ago and I ended up creating the same import system for Avatar’s R6
game.Players.PlayerAdded:Connect(function(Client)
Client.CharacterAdded:Connect(function(Character)
if (Character:FindFirstChildOfClass("Humanoid").RigType == Enum.HumanoidRigType.R15) then
repeat task.wait()
Character:FindFirstChildOfClass("Humanoid").RigType = Enum.HumanoidRigType.R6
Client:LoadCharacter()
until Character:FindFirstChildOfClass("Humanoid").RigType == Enum.HumanoidRigType.R6
end
end)
end)
As the server script runs much faster than the Client, so I guess you won’t have any problems
Same thing. Exactly. I am just wondering, how long will it take for this to get fixed?
Seems like this is caused due to attempting to playtest on a bad ping, and the engineers for some reason made R15 the default fallback on rendering characters, but since this is R6 and it’s deprecated it won’t get fixed anytime soon.
What was the last time a bug relating to R6 was fixed in the time span as a bug relating to R15?
An engineer literally said this was resolved yet it’s still occurring and we haven’t gotten any updates.
Well what would be the time span?
Temporarily, if you guys don’t want to manually fix it then reset your avatar when you first get in, it should send you to R6 again.
bump. Stills happens to me, it is now happening very often in some of my places
for some reason this also happens to me as well and im confused on why. is it a bug or something? i tested in other places and i had no problem but creating new places causes this to happen
Me twenty-one, I got this issue as well.
This fixed it for me.
Note that using this method, the character doesn’t keep any StarterCharacterScripts, which could cause issues. Implementing a function like the one below should solve most problems though:
local players = game:GetService("Players")
local starterPlayer = game:GetService("StarterPlayer")
local function transferStarterScripts(character)
local starterScripts = starterPlayer.StarterCharacterScripts:GetChildren()
-- Remove this line if you don't use an Animate script in StarterCharacterScripts
character:FindFirstChild("Animate"):Destroy()
for _, script in pairs(starterScripts) do
local scriptClone = script:Clone()
scriptClone.Parent = character
end
end
for _, player in pairs(players:GetChildren()) do
if player.Character.Humanoid.RigType == Enum.HumanoidRigType.R15 then
local humanoidDescription = players:GetHumanoidDescriptionFromUserId(player.CharacterAppearanceId)
local r6Character = players:CreateHumanoidModelFromDescription(humanoidDescription, Enum.HumanoidRigType.R6)
r6Character:SetPrimaryPartCFrame(player.Character.PrimaryPart.CFrame)
r6Character.Name = player.Name
player.Character = r6Character
r6Character.Parent = workspace
transferStarterScripts(r6Character)
end
end
Having a StarterCharacter inside of StarterPlayer also seems to fix it.