Backwards compatibility with Unity 3.4 and below.

[unikronsoftware]

A few things can be done significantly more efficiently (and save a ton of memory) in Unity 3.5 - I am considering dropping support for 3.4 and older versions for these features, but I would like to know what everyone else thinks.

[fsadeq]

Appreciate you asking everyone. I am updating to 3.5 and never looking back, though

[Intrawebs]

I just installed today (your plugin) after my Unity upgrade from 3.4 to 3.5.  Im all set.  I've seen some peeps rolling back to 3.4 in the Unity forums, but it was mainly on very large multi GB projects and some advanced shader issues, so Im not worried with 2d.

[unikronsoftware]

A lot of people still seem to be using 3.4, which is unfortunate. I think our plan (still not fully decided) is to support 3.4 on all available features now, but new features (the tilemap editor, for instance) will leverage features which are 3.5 specific. The way it is set up now, is that it does work in 3.4 as well, but some interface stuff just isn't there.

That is our current train of thought anyway, it could change.

[unikronsoftware]

I am happy to say we have found a solution to the tilemap editor on 3.4, it is a superior solution to the 3.5 specific one we had previously, so full 3.4 compatibility for a while longer...