Actually a follow-up…
So I got the buttons to work by physically moving them, but something still does not sit right with me. I created a new layer for this particular set of elements and made sure that it was being sorted manually on render. In this case, I’m not sure why we would still be calculating what is the closest to the camera if the intent is made clear by the created layer that the UI should be sorted manually.
This could especially pose a problem for 3D screens that can be interacted with by a user in a 3D environment that they can walk around in. If each element needs to stick out above the screen, it may be readily apparent to the user that it isn’t a flat screen as it should be.
Looking back through the previous posts, I now understand the reason for the pull, but it looks like the original forum post had problems with the fact that he created a distance sorted layer that did not fire events correctly based on the distance based sorting. I would think that those that are using manually sorted layers should be able to continue creating their UI in the same way.
edit: It looks like mine isn’t the only project affected. @gnormanlippert 's project is also affected by this change: