Region3 from size and CFrame

Feature Requests Engine Features
#1

As a Roblox developer it is currently Inconvenient to create Region3 values.

Region3’s only two properties are size and CFrame [1], so it would make sense for me to be able to create a region 3 using these two values? It’s annoying having to convert a part into two Vector3’s representing opposite corners when it’s just going to revert them right back to a size and position. It’s not difficult, just needlessly inconvenient

[1] - It’s odd that regions even have CFrame instead of position, given region3’s are inable to have any kind of rotation to begin with.

9 Likes
#2

This is a little bit of a bump, but I do think that making the CFrame and Size aspects of a Region3 readable and writable would eliminate a lot of extra math in creating Region3’s based on parts in the workspace, or really any time you need to convert a CFrame into a Region3. It seems like a simple feature addition (I have no idea how these work so correct me if I’m wrong) that would make workflow a lot faster for some devs.

4 Likes