2D Toolkit 2.5.8.3

[unikronsoftware]

Please read the migration guide before updating. 2D Toolkit 2.x is not API compatible with 1.x.
http://2dtoolkit.com/docs/2.4/migration_guide.html

Documentation available at:
http://2dtoolkit.com/docs/2.5


Be sure to run "Setup for JavaScript" after importing if you're using JavaScript/UnityScript or Boo.

What's new

• More Unity 2017.1f3 compatibility fixes
• Fixed up Unity 2017.1f3 warnings
• Exported in Unity 5.4. Previous versions of Unity are no longer supported
• Removed tk2dSkin.dll dependency. Dll has been emptied out for backwards compatibility
• Lots of bug fixes and improvements
• Added experimental support for polygon colliders in tilemap. In the tilemap edit page, Edit > Settings > Tile Properties > Use 2D Polygon Colliders to turn this mode on.

Bug fixes and improvements

• Fixed tilemap prefab instantiation bug
• Fixed tk2dCamera rotation issue, added support for WSA
• Fixed issue with some inspectors not saving changes correctly in Unity 5.3+
• Inertial scrolling fix for scrollable area
• Removed platform specific functionality for WebPlayer, WP8 and Flash
• Fixed negative box collider warning
• Fixed input field string doubling up on Android
• Rudimentary physics stripping to remove dependencies to 2D and/or 3D physics
• Fixed deprecation warnings for Unity 5.4 and 5.5
• Fixed texel size when atlas texture is globally scaled 0.5x or 0.25x
• Editor collider rebuilder script - Don't rebuild when sprites have "user defined" colliders set
• Texture importer supports "Sprite" textures as input in Unity 5.5

[playspace]

Hi there, I just saw that you added #if UNITY_VERSION > 550 into the shader code to handle the mul(UNITY_MATRIX_MVP,*) to UnityObjectToClipPos(*) case.

While this is correct I think you are missing the // UNITY_SHADER_NO_UPGRADE flag if not Unity will just upgrade both parts of the conditional code.

[unikronsoftware]

Hi, Thanks for that!

I am slightly worried to add that in case a future unity update breaks something in the shader that is fixed by the auto-updating thing, but since that is turned off, it just ends up breaking catastrophically... Any thoughts?

[playspace]

I think it's just something we have to maintain by hand. Unity should not upgrade those parts if thei are enclosed in the right defines, so using those defines without the flag is completely useless (rendering the version defines itself usless xD). So I guess it's just reading release notes and checking nothing breaks, a good think is that it will break at shader compile time so it should be easy to spot.

Cheers,
Moss