Click on the Camera object inside of the Workspace through the Explorer window, and inspect the properties named CFrame and Focus in the Properties window:
You’ll notice that the value column of each CFrame property is empty.
Expected Behavior
There’s supposed to be a text value formatted as {X, Y, Z}, {RZ, RX, RY} in the value column of the CFrame property. This is made apparent when you click on the name of the property 3 times, and it suddenly gets populated with a value:
Actual Behavior
The value of the property starts empty and gets repeatedly cleared as long as the property is expanded. If the property is collapsed and you triple click on its name, it will start updating correctly. This stops working when selecting another object.
Issue Area: Studio Issue Type: Display Impact: Moderate Frequency: Often
Hi, this behavior is intentional. We don’t show the contents when a CFrame is expanded to avoid showing duplicate data and adding clutter (that data is already available in the Position/Rotation properties). The formatted string is only shown when the Cframe is collapsed.
The value is being left blank even when it’s collapsed unless you keep clicking on the property to populate its value. This is a legitimate bug and not a side effect of how it’s currently intended to work.
Quality of life wise, I think it would make more sense to grey out the value while expanded rather than leaving it blank. I’d like to be able to copy and paste a position and rotation upon mousing over the property, quick and simple.
It’d also be nice if properties could remember whether they were collapsed or not, but this isn’t a necessity.
I found this a bit unfortunate as well. I was hoping I could copy the CFrame from one box for convenience when expanded to easily use it elsewhere (say CFrame a part to another without code), but alas, no luck. Even if the value should be hidden to reduce clutter which I agree, I still think it would be better QoL if we could copy from the box to get the value (or something like it), and you wouldn’t be sacrificing usability.
On top of this, even if not exactly related, it would be cool to see an improvement with these kinds of values in the future. Like when I edit UDim2 values, it would be faster if the brackets weren’t selectable and acted as their own boxes.
Outside of transferring values, I personally don’t find much use in having these extra characters I have to navigate around that don’t serve much purpose to me. I want to edit the raw data, being able to mess around with the commas and brackets makes it feel clunkier… unless if it’s just me lol (As an example, I’ve accidentally deleted these or messed up the format while messing with them, which caused the value to not be set)
Hi there! We got a response, but I had some feedback and was hoping this is still open to discussion. Should I make a new feature request based on the feedback?
