No concerns whatsoever were raised on our Alpha users’ group.We ran a poll on our forums and out of 471 votes, only 11 (2.7%) were cast in favour of the 32-bit editor.Having had the numbers confirm our suspicions we wanted to reach out to the community to get a feel for the reception we would get from dropping support for 32-bit Windows editor. And if we look at the number of unique users on each type of build for the last 30 days we see very similar numbers: just 5.6% on 32-bit.Comparing overall editor starts between 32-bit and 64-bit, we confirmed that use on 32-bit has declined steadily from 6.2% 12 months ago to 4.7% today.
We already knew that usage of Unity on 32-bit Windows was low, but naturally we wanted to back up any decision to drop support with hard data, so we dived into our telemetry database in order to extract and analyse statistics on a couple of fronts: Additionally, as this OS continues to age, our cost of supporting it continues to rise. Even with that, it won’t come as a surprise to many to learn that usage of Unity on 32-bit Windows is pretty low compared to other OSs, and furthermore that it has been declining over the past few years.
Two years ago, the arrival of the 64-bit editor let most users deal with previous resource constraints and memory limitation issues however there are still legacy 32-bit native plugins that keep some users behind. For some time we have been thinking about when would be the right time to deprecate and ultimately end support for 32-bit versions of the Unity editor.
0 kommentar(er)
