This is problematic because the right-center side is often reserved for buttons placed specifically by the developer but are now gonna be overlapped by the capture button.
If the capture button requires a non-traditional position, developers should have access to an api to move it around at the very least, because forcing this arbitrary placement is very problematic.
Sorry for the inconvenience. It’s not intentional that this is enabled by default.
We made a change to enable the button by default for experiences participating in The Haunt but this inadvertently made it such that users who join any of these experience will see the button enabled by default in the next experience they join.
Users are still able to disable the button from the experience controls menu, or as the developer you can disable this feature using game:GetService("StarterGui"):SetCoreGuiEnabled(Enum.CoreGuiType.Captures, false). We are working to get a fix out for this issue as soon as possible.
Update: We’ve released a fix for this issue that will be applied when users close/re-open their app or game client.
Users who have the feature defaulted to the active state will still need to disable the feature in the experience controls menu, but the issue is fixed for new players who join one of the participating experiences.
This was the best mitigation we could immediately release, we will look into fixing the incorrect default for other users who joined during the broken period in a future change.
Yes, it’s suppose to be in the hamburger menu the button seems to be disabled by one of the game’s developers/you disabled it in your game which means that you can’t turn it off
Hi, yes there should be a way to turn off the button in the experience controls menu.
However there is a known bug with Captures sometimes not showing in this menu, the team who owns that menu is working on a fix. I’ll follow up to see what the status of that is.
Following up on this to say that we have released a change to reset Captures visibility to default off for users who had Captures incorrectly enabled for the period this bug was active on production.
All affected users should have this state fixed when they next join any experience.