What’s the big difference between the two builds that half the things in the asset store aren’t for sale to people below version 3.5?
Things like textures, monsters, buildings. I figured a png is a png regardless of what Unity build you’re running?
I’m curious because on external websites nobody mentions this and I’d like to know what to look for since I’m using 3.4.2f and in the middle of a project and would hate to buy stuff I can’t use. I had to roll back to 3.4.2f from 3.5 2 months ago due to some unresolved bugs and don’t really know how smooth/risky an upgrade would be at this point.
I am in same position as you. I’m on 3.4.x and in the middle of development and there is a model pack I would like to buy however it have the limitation of supporting 3.5+. I haven’t heard anything back regarding the problems I reported when I first tried out 3.5 so I assume they have not been addressed.
Submitting a package to the asset store with Unity 3.5 apparently raises the minimum required version to 3.5. That’s what happened to all of the packages I submitted and updated.
Wow, that’s annoying. It just got to a point I figured I should rage on the forums about it because it’s a significant portion of anything new.
It just happened with the handpaintedtextures, I was on his site, figured I should check the asset store cause he mentioned having packages, and low-and-behold they cannot be bought. If it’s just because he has 3.5 then I can still buy from his site but for the rest of asset owners I guess take note. I figured there was something about them that didn’t run on 3.4, but if it’s simply a png file…frownface
I assume it’s because Unity 3.4 and 3.5 have incompatible project file formats and 3.5 can convert from 3.4 but not vica versa (the same reason why upgrading your project to 3.5 is a one-way trip)
I upload my packages using Unity 3.4 specifically so the requirement is 3.4 rather than 3.5. It’s not really a great system, but I’m not sure what else they can do. The .x updates tend to be quite significant and not everything is backwards compatible.
–Eric
I can understand the ‘rationale’ that the developer has uploaded using 3.5 so therefore it has only been testing in 3.5 but it should be at the creators discretion. Some check boxes or something would be nice, that would allow the creator to say compatible with versions A B and C and platforms X Y and Z. The creator is ultimately responsible for supporting their product so automatically restricting versions seem almost like an underhanded way to pressure users to upgrade.
That’s not actually the rationale. They have no way of knowing what versions you tested. What’s really going on is that Unity 3.5 simply doesn’t use the same format that Unity 3.4 does. It physically does not work to load 3.5 packages into 3.4. (Well, it works to some extent, but you can expect that you will have to fiddle with stuff to get it to be the same as it was in 3.4, and Unity Tech certainly can’t have customers ending up with semi-broken packages.) However, Unity 3.5 can load 3.4 packages, so it’s OK going the other way.
As I said, it’s not really a great system but I don’t know what else they could do.
–Eric
Agreed there simply is no way of changing this. Not just loading the packages is an issue but if you compared 3.0 with 3.5 you realize that the mesh and generally asset import and options there changed massively and you simply can not use import features on 3.4 that just didn’t exist on 3.4 → meta data in the package will fail or be wrong → import will cause incorrect assets → fail → blame towards dev or unity for allowing it on the store when it was the user who fucked it up → solution is not to offer it to the user right from the start → thats whats done
They could fold the 3.4 package exporter into 3.5 (or at least, they could have done at release), so that it’s possible to export 3.4-format packages from 3.5.
Wouldn’t work cause your prefabs will not transfer.
3.5 has a an indepth reworked prefab system and those prefabs go exactly nowhere basically
3.4 already reworked it over 3.3 which is why an attempt to go back fails there pretty regularly too.
same goes for texture import settings.
Exporting the package in unity 3.4 format makes 0 sense if there will be no working content in → you want to create something for unity 3.4, you must use unity <= 3.4, as unity has only upward compatibility, not backward compatibility
Well that does make sense, but it seems that it would work for other assets. If there is a package which is purely scripts, that should be compatible but it seems their one one-size-fits-all method breaks that. In this case I want to buy some textured models, AFAIK they should work as well. I would prefer a big warning and ticks and crosses showing which assets are compatible.
You can always use 3.5 to buy the assets, then transfer them to 3.4, which for simple things will work without issues. Inconvenient but not a huge deal.
–Eric
From an end user point of view, what’s changed?
Sure, so there are some settings that aren’t supported under 3.4. Exporting assets that are configured to use those settings can generate an error. But exporting assets that aren’t configured to use those settings is fine.
This doesn’t have to be an all-or-nothing deal. There’s still value in supporting export of the bits that haven’t changed back to 3.4.
(Of course, I’d probably rather that they spent their effort building new versions that were usable such that we weren’t stuck on 3.4 in the first place…)
I’d understand if a prefab doesn’t work, but textures, 3d models, etc are the same for all versions.
Yea I bought the textures off the guy’s site and they’re phenomenal.
Maybe some sort of legacy ftp site where people can download zip files rather than import directly through the editor from the store???
Like turbosquid and every other stock asset site on the web…I unzip downloaded files and import them into unity from numerous stock sites and they work fine… if it’s an fbx or 3ds file and a texture, there’s a very HIGH likelihood that it will work perfectly in Unity.
I have 3.5 on a second computer (how I found out the bug in 3.5 wasn’t me after installing fresh and having it bug out) I will try downloading them there and transferring to this machine…