Based on a staff member’s replay, selection surface object is deprecated:
It doesn’t say it is deprecated in documentation. The more important question is why it is used by studio itself when the object should not be used anymore if deprecated. The object is used when adding a decal and selecting a face of a part:
If it was up to me, I would keep these instances maintained as making a bunch of base parts with physics-based properties seems like a waste of memory to me. But if it’s deprecated, it should be marked as deprecated and not used by studio interface.
Expected behavior
Mark it as deprecated or maintain it. If deprecated, make the studio interface not use the object.
Hello @WinterStorm_Meow , just wanted to confirm that this is the same situation as your other report for SelectionSphere. I reached out to the responsible team and they have confirmed that this feature is not currently deprecated but is under review for deprecation. As soon as we receive confirmation, we will update the documentation. Thank you very much for flagging both API!
Yes, the main reason why I flagged SurfaceSelection is because the Transparency property no longer works but everything else seems fine. There should also be a Thickness property for customizing the outline and some optimization improvements, if not depreciated.
I personally believe that both SelectionSphere and SurfaceSelection should still be maintained as there is no a good suitable replacement. I know the Highlight instance is supposed to be the replacement to both, however the number of Highlights you can have at once is limiting and it comes at performance loss. SelectionSphere and SurfaceSelection are both low performance objects that could definitely could fill a space if fixed.
