Studio is heavily dependent on back-end endpoints to function correctly especially for modeling/art purposes. Back-end surface tend to change over time, so certain features of older Studio versions would stop working correctly if any of those older endpoints are taken down, or if endpoint signatures/behavior are changed.
Perhaps they made changes to the update bootstrapper that requires a fresh install of the bootstrapper, and can’t be iteratively installed from the previously installed version.
I know this is definitely the case, but, like I said, even if that’s the case I still harshly disagree with completely blocking off access to even load studio at all. I would still like to attempt a studio load, for all the reasons I mentioned before, because it makes it much more feasible to work around the API issues with my own stuff. Even if it means I need to work around those sorts of conflicts, having an extra wall in front of me that’s just making it harder to work around issues is obnoxious, and it does concern me a lot.
(Besides, a partially functioning version of Studio is still a partially functioning version of Studio)
In 99% of users/cases, you likely want to allow Studio to auto-update and reduce risk of breakage. For that other 1%, I recommend filing a feature request, but keep in mind you are that rare 1% of use cases around launching Studio so it will get prioritized accordingly.
not for a while as in “waiting for the apple cert” or like not this year
pretty hyped to start plugging it in to a bunch of old things for cell shading, night vision, wallhacks, etc