Does this mean we will be able to change the shape of a regular part in the Properties tab? Are the CornerWedgePart and WedgePart Instances going to be deprecated? Will this Enum also have the Truss part?
Dude, Floor UserCFrame is gonna be so helpful. Canāt wait to use it
Exciting! Iām eager to start using the new wedge enums soon!
UIScale working correctly with AutomaticSize was also a much needed upgrade for us! Canāt wait for these two to go LIVE!
Question unrelated to this release note but important non the less. āFindFirstDesendantā was added to the API around a year ago (if Iām not mistaken) but has stayed disabled ever since, when will we see it enabled?
Why wouldnāt :FindFirstChild(āxā, true) work?
Itās really neat that Roblox is going back to these old instances and upgrading them to match new behaviours. I really hope to see the deprecation of WedgePart and CornerWedgePart, as this property of Part is much easier to manage.
On another note, can we get more info on SharedTable and SharedTableService?
Wow, I didnāt expect this:
This could be very useful for VR games! Maybe Iāll continue mine?
Could somebody show what this inconsistent behavior looked like? I know of a few issues with AutomaticSize, but what is this one?
There will be an announcement and documentation on it, itās for shared data access between Parallel Luau Actors on different threads.
Thatās a bittersweet announcement for me, as I was really hoping we finally had a proper solution to share table data between actors, the server, and the client. I have a custom one, but a Roblox implementation can always handle more edge cases, and be more efficient than I can.
Highlight now displays correctly on Parts with transparency.
Yes 
Iāve been waiting for this. I hope it gets out of pending soon.
Is this also the case with a ScrollingFrame AutomaticCanvasSize? Current behavior when using UIScale on a ScrollingFrame with AutomaticCanvasSize to Y results in being unable to the scroll to the end of the child elements unlike where you can if UIScale was not being used.
Jumping in here to say that the Changelog release status doesnāt always match reality.
Click me for details!
Each āPendingā change reads a specific FFlag behind the scenes, and sometimes a feature is turned on through a different FFLag. This results in the feature being active, but the changelog saying āPendingā. Occasionally an FFlag gets re-named before it ever gets flipped, which caused the changelog entry to stay āPendingā forever.
That it shows up at all in the Release Notes means you should expect it to be flipped on before the end of the week. (The entire changelog is usually live, at worst, five days after the Release Notes get posted.)
That being saidā¦
ā¦Am I dreaming? Did someone at Roblox finally install SteamVR? What was the usecase that justified having this change? Not having a floor was always the thing that made VR games impossible to design because sense of scale was impossible to determine without using ugly hacks that were prone to abuse, and there were feature requests for this pretty much ever since Roblox VR existed.
Donāt get me wrong, Iām happy. This feature came along quite a bit late, but Iām still happy.
I hope so, Iāve been having that issue for a while
How long after that will we be getting localsafe properties for instances parented under the same actor? This is all really exciting!
One is BFS, one is DFS. The difference between the two is whether or not depth or breadth is prioritized. One will check children of children first, the other will check siblings of children first. (I am sure this will be better clarified on the docs btw)
This can have minor performance implications in some contexts, and Iām sure there is some justification for it, plus FindFirstDescendant being a slight bit more obvious.
I checked and we donāt plan to enable it. It will be cleaned up to not show up.
How long after that will we be getting localsafe properties for instances parented under the same actor?
Hi @Prototrode,
This is something we definitely want to enable. We recently did some work to support this, but determined that there were various complications that made the approach we were using unsafe. There is a more general (but also longer term) solution to this problem that is planned, but we donāt have a firm release date for the change.