Hi all:)
Just putting this out there. I’m not asking anyone to try and make packages work in versions lower than possible. I think package dev is hard, and the extra hours to make an asset work in an earlier version than it can by default is understandable too much work for most devs.
But if it already does work by default in an earlier version, releasing it in that version might open up some sales.
There’s at least a few hundred dollars worth of purchases im holding off on because for the moment i am stuck on Unity 5.2.2 and 5.3.7. I can’t be the only one so that could add up.
Ive seen the download stats and know most people are downloading the latest version. But for those of us with legacy projects, upgrading our version of Unity can be a more daunting task. It might help if Unity could let developers and asset creators know the stats of which versions developers are actively using, as opposed to downloading. For example, ive download 5.4, 5.5 and 5.6, but i only work with 5.2 and 5.3, so that skews the stats.
It might help with updates too - there are a few dozen packages i cannot update for the same reason.
That said, thank to Unity for the asset store, and to the devs for all of the wonderful packages I’ve purchased. I could not make games without your help:)
I agree that one should be able to purchase assets which require a higher Unity version. A simple warning that you need an update in order to use it would suffice imo.
However. Some time ago I have found a “workaround”. I added the asset to my wishlist. In the wishlist is a small shopping cart icon beside the asset. I just clicked it to add it to my shopping cart. This seems to prevent the version check.
However. This has been some years ago so I don’t know if it still works. Could be worth a try. I had also a thread about it when you feel like searching it ;).
1 Like
Thanks exiguous:) I think the general Unity ecosystem is geared towards move fast/break things approach so backwards compatibility doesn’t seem to be a priority, which is fair enough but does cause some problems for some devs. New versions of Unity are great if you’re starting a new project, but if youve been developing on Unity for a few years it can be no small feat to upgrade your project because many APIs and workflows are changing as well.
What I do is buy the product and then just import it like normal - it works but the only issue is if the assets actually does not work on my version of Unity. Right now i have Unity 5.2 for production, and i test out more assets in 5.3 in anticipation of eventually being able to upgrade to a higher Unity version in production.