Started occurring after today’s Studio update. Happens during play test when the client calls StarterGui::SetCore or SetCoreGuiEnabled. I’m able to replicate on play solo and local server but only on the client side (for reasons)
Certainly a low priority issue but I saw some confusion about it posted earlier, which leads me to believe it’s not platform specific to macbooks. Doesn’t seem to be a cause or symptom of any other issue either, but I’d imagine the warning is there for a reason.
Expected behavior
observableValue is defined and we never hear about it again
Expected result
define observableValue / fix the underlying code or remove the warning if it’s not actually needed
FYI: the bug is tied to the Updated Roblox Controls Studio Beta, so you can turn that off if you’re in need of an immediate fix. This also means that the bug should be studio-only, so it won’t be an issue at all for your players. If you do happen to see the error show up outside of studio, please let us know!
You edit your flags manually, right? @QuirkySquid said that with the assumption that no one has the new topbar UI rolled out to them (which is the case right now, unless you manually edit your flags). If you edit your flags you should expect to see this kind of behavior, these features are not intended for public use yet.
Confusion is understandable, we call the new UI “New Experience Controls”, “Chrome”, “Updated Roblox Controls”, and “Unibar” across different places, lol
In any case, yes, the AB test has ended— though keen viewers may have noticed its return in the opening keynote at RDC this morning
this bugs me more than the output warning