Camera instances do not save when team create is enabled

Bug Reports Studio Bugs
,
#1

Camera instances, when team create is active, do not appear when save-loading. Turning team create off then save-loading re-instantiates the camera instances for no apparent reason. This is quite an irritant when working with systems that use multiple cameras such as cutscene-only cameras or viewport frames.

It takes 2 steps to repro and is hotfixable by disabling team create. Below is a video outlining the repro steps and the .rbxl file associated with the video

camera disappearing act.rbxl (50.3 KB)

3 Likes
#2

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

1 Like
#3

If it’s been a thing since the dawn of time then i don’t anticipate this getting fixed anytime soon

There’s probably a lot of gymnastics involved in fixing this and it wouldn’t be worth it for whatever team/group in charge of TC maintenance to expend resources toward fixing

1 Like
#4

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

#5

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.

#6

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

#7

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

#8

I don’t understand, what does that have to do with why cameras save for non-team-create studio sessions and why they don’t save for studio sessions with team create enabled?

#9

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.

1 Like
#10

Okay thanks for clarifying, that makes sense now

I would make one but considering that this has been a thing since forever + the roblox ethos of backward compatibility/caution towards breaking things that “have been a thing” it just wouldn’t be worth the effort knowing it wouldn’t get anywhere past me clicking on the create topic button

I’ll just take the loss and keep relevant camera data/properties in a table and read from that ¯_(ツ)_/¯

Thanks for the insight

1 Like
#11

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