Camera instances do not save when team create is enabled

overflowed · February 2, 2025, 3:53pm

(post deleted by author) ᅟ ᅟ ᅟ

Tavikron · February 2, 2025, 4:23pm

I can confirm this behavior and also note that it’s been happening as long since Team Create is a thing.

overflowed · February 2, 2025, 4:27pm

(post deleted by author) ᅟ ᅟ ᅟ

moondowndontfrown · February 2, 2025, 4:32pm

I think it’s a bug thats caused by team create

Judgy_Oreo · February 3, 2025, 1:45am

It seems that that one quirk of Cameras not serialising strikes again. This is why you need to create Viewport Frame Cameras through a Script and why the ones you set for them in Edit mode disappear.

thirdtakeonit · February 7, 2025, 5:20pm

Thanks for the report! We’ll follow up when we have an update for you.

brienneofthetarth · February 7, 2025, 6:37pm

Cameras currently by design are Client side objects and not replicated. For customizing camera, please refer to: Customize the camera | Documentation - Roblox Creator Hub

overflowed · February 8, 2025, 8:09pm

(post deleted by author) ᅟ ᅟ ᅟ

Judgy_Oreo · February 9, 2025, 3:25am

Team Create runs on a real Roblox server that Studio connects to. Cameras do not replicate from the Server to Clients, thus, even though the Camera exists in the place file (which is why disabling TC allows it to appear, as Studio loads it directly instead of having it replicated from the TC Server), and exists on the TC Server’s perspective, it doesn’t appear for connected Studio Clients.

Because this behaviour is intended (for whatever reason), you need to make a Feature Request or show your support to an existing one for this to be changed.

overflowed · February 9, 2025, 11:44am

(post deleted by author) ᅟ ᅟ ᅟ

system · February 23, 2025, 11:44am

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.