`CreateDefaultPlayerModule`, breaks camera + character control in new/empty places (studio-only)

[orangFest]

In any brand-new empty place, more specifically from chosen templates like Baseplate, Flat Terrain, etc. or via “New Experience”, upon launching and playing, camera is frozen (positioned/rotated as if no character has loaded) and the character cannot be moved or rotated, even though the character does indeed spawn. This only happens in Studio playtest, the same place runs fine in Roblox Player on WIndows and Android. The error: exception while signaling: The Parent property of StarterPlayer is locked - Studio, appears when game.StarterPlayer.CreateDefaultPlayerModule is enabled. Disabling that property removes the error but does not restore the camera or character control.

It started happening today, and I was trying to debug it for three hours.

Specs

• OS: Windows 11 Home 64bit
• CPU: 12th Gen Intel Core i5-1235U, ~1.3GHz
• GPU: Intel Integrated (UHD) Graphics

Reproduction steps

• create new, completely empty place (any template)
• leave StarterPlayer.CreateDefaultPlayerModule as its default (true)
• press “Play” button (F5) in Studio
• observe that error exception while signaling: The Parent property of StarterPlayer is locked in Output window.
• also notice that the Character spawns, but the camera is frozen at a fixed position and the character cannot be moved nor rotated
• set that CreateDefaultPlayerModule to false, “Play” again and that error disappears, however camera and character are still frozen/uncontrollable (even though it is not showcased in video below, it stays true after recording)

Before and after investigation, I’ve (1) toggled CreateDefaultPlayerModule, (2) disabled and uninstalled all plugins, (3) reinstalled Roblox Studio alongside Roblox Player, (4) killed all Roblox processes, (5) reset all Roblox-related registry entries, (6) manually created PlayerModule in StarterPlayerScripts with CreateDefaultPlayerModule enabled and disabled.

Here’s attached .rbxl file, that contains absolutely empty place literally fresh from “Baseplate” template, tested on latest production channel publicly available (version 0.734.0.7340915):
Place1.rbxl (58.6 KB)

Friendly reminders that:

1. charcter does spawn correctly (CONFIRMED: Player.Character exists WITH Humanoid AND HumanoidRootPart)
2. those issues don’t occur in base Roblox Player;
3. these issues occur only in newly created/empty places, previously-created experiences are unaffected
4. All Beta features were disabled in advance!

Expected behavior

Simple. With CreateDefultPlayerModule enabled by default, the default camera and control scripts should be injected into “StarterPlayerScripts”, and the camera should follow the character with normal movement and rotation controls.

[Reisdro_08]

Hey there!

Thanks for reporting. We’ve identified this issue as a duplicate of another topic that was already acknowledged and under investigation.
I’ll close this topic, but please stay tuned to the following thread:

"exception while signaling: The Parent property of StarterPlayer is locked" —happens on every new place, only under one Windows user account

Yes, we’ve received it, thank you! We are actively looking into this issue. It may take some time for the fix to release, we appreciate your patience while we work on this.

Thanks for your patience and understanding.
Have a nice day!