2D Toolkit Forum

2D Toolkit => Releases => Topic started by: unikronsoftware on May 24, 2015, 04:26:53 pm

Title: 2D Toolkit 2.5.3
Post by: unikronsoftware on May 24, 2015, 04:26:53 pm
Please read the migration guide before updating. 2D Toolkit 2.x is not API compatible with 1.x.
http://unikronsoftware.com/2dtoolkit/docs/2.4/migration_guide.html

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


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

What's new

Bug fixes and improvements
Title: Re: 2D Toolkit 2.5.2
Post by: mrkake on May 24, 2015, 08:08:23 pm
Hi,
I'm not totally sure but I think there can be a bug introduced here, as my game stopped working.

I checked the line where I'm getting the error - tk2dTileMapMeshBuilder.cs line 61.

colorChunk is null, and there is a null reference exception trying to read the values from it.
Strange because line 31 above is checking it's null, but it doesnt stop the code from continuing.
And I see like 79, if (useColor), but this would clearly never be reached.
Title: Re: 2D Toolkit 2.5.2
Post by: unikronsoftware on May 24, 2015, 10:19:48 pm
Yeah, my bad :( I'll fix it.
Thanks for reporting it.


Update -
Fixed: Incremented version number to 2.5.3
Title: Re: 2D Toolkit 2.5.3
Post by: mrkake on May 24, 2015, 10:43:50 pm
tested , its working now :)

thanks! you rule :)
Title: Re: 2D Toolkit 2.5.3
Post by: DNA-Studios on May 25, 2015, 10:00:23 am
Hey folk,

Thanks a lot for this update, especially for the sprites disappearing :-) However, I get a strange behaviour when trying to patch the API:

Any clue about that ? We use Unity 5.0.2 and the TK2DROOT folder is set in a Libraries folder (/Assets/Libraires/TK2DROOT). Integrity checker gives me a full list of incorrect files.

Thanks again.

DNA Studios
Title: Re: 2D Toolkit 2.5.3
Post by: jmenossi on May 25, 2015, 10:52:52 am
Hi,
I had same problem with obsolete API on Unity 5.0.2...
I'm using tk2d 2.5.1 and tried to update to Unity 5.0.2, but got some errors in tk2d scripts.
Does tk2d 2.5.2 or 2.5.3 actually fix this?
Thanks!
Title: Re: 2D Toolkit 2.5.3
Post by: fallingbrickwork on May 26, 2015, 10:44:35 pm
Great update and no issues here.

A quick Q... Support for flat colors instead of interpolated with Tilemaps, how do we use/setup this (I can't see anything in the docs although I could be looking right at it  ;)?

Cheers,
Matt.
Title: Re: 2D Toolkit 2.5.3
Post by: unikronsoftware on May 27, 2015, 01:14:05 am
Its an option in tilemap settings > Tile Properties > Color Mode :)
Title: Re: 2D Toolkit 2.5.3
Post by: unikronsoftware on May 27, 2015, 01:18:23 am
Hey folk,

Thanks a lot for this update, especially for the sprites disappearing :-) However, I get a strange behaviour when trying to patch the API:
  • I first download the package and extract it with python
  • I remove the old version of 2D Toolkit
  • I import the files into Unity (tried both inside and outside Unity)
  • Unity asks me to run the update manager because the library uses some obsolete methods
  • Regardless of what I chose above (automatic update of scripts or if I update them myself), all the tk2d scripts are then displayed as "missing behaviours" in the scenes. Not a single error appears in the console and when I run the game, none of my scripts are able to access a tk2d script.

Any clue about that ? We use Unity 5.0.2 and the TK2DROOT folder is set in a Libraries folder (/Assets/Libraires/TK2DROOT). Integrity checker gives me a full list of incorrect files.

Thanks again.

DNA Studios

If the integrity checker gives you a list of incorrect files, then your files are incorrect and updating is going to cause a lot of grief. This usually only happens when not storing meta files at some point in the past.

Also you've moved the folder from its default location, making it harder to overwrite... Removing and adding like you did with a corrupt installation will end up with missing behaviours, and everything is going to be broken. You'll have to import into a new project and manually copy the files and overwrite in this project if you wish to update.

Unity update manager prompts doesn't indicate an issue, it just runs because the unity package was exported from Unity 4. If you download from the asset store using Unity 5 you won't have that message.
Title: Re: 2D Toolkit 2.5.3
Post by: unikronsoftware on May 27, 2015, 01:19:51 am
Hi,
I had same problem with obsolete API on Unity 5.0.2...
I'm using tk2d 2.5.1 and tried to update to Unity 5.0.2, but got some errors in tk2d scripts.
Does tk2d 2.5.2 or 2.5.3 actually fix this?
Thanks!

There is no issue in 2.52 / 3 in Unity 5. The obsolete API message is only visible because we exported the package here using Unity 4.6, you can download the same thing from unity asset store and you won't get the message there. There is no known issue updating, post the error you get and should be able to work it out from there.
Title: Re: 2D Toolkit 2.5.3
Post by: DNA-Studios on May 27, 2015, 09:15:14 am
Hey folk,

Thanks a lot for this update, especially for the sprites disappearing :-) However, I get a strange behaviour when trying to patch the API:
  • I first download the package and extract it with python
  • I remove the old version of 2D Toolkit
  • I import the files into Unity (tried both inside and outside Unity)
  • Unity asks me to run the update manager because the library uses some obsolete methods
  • Regardless of what I chose above (automatic update of scripts or if I update them myself), all the tk2d scripts are then displayed as "missing behaviours" in the scenes. Not a single error appears in the console and when I run the game, none of my scripts are able to access a tk2d script.

Any clue about that ? We use Unity 5.0.2 and the TK2DROOT folder is set in a Libraries folder (/Assets/Libraires/TK2DROOT). Integrity checker gives me a full list of incorrect files.

Thanks again.

DNA Studios

If the integrity checker gives you a list of incorrect files, then your files are incorrect and updating is going to cause a lot of grief. This usually only happens when not storing meta files at some point in the past.

Also you've moved the folder from its default location, making it harder to overwrite... Removing and adding like you did with a corrupt installation will end up with missing behaviours, and everything is going to be broken. You'll have to import into a new project and manually copy the files and overwrite in this project if you wish to update.

Unity update manager prompts doesn't indicate an issue, it just runs because the unity package was exported from Unity 4. If you download from the asset store using Unity 5 you won't have that message.

Hi,

Thanks for your answer :)

The integrity checker complains after trying to update, not before. Anyway, I don't really understand why the location of the library is important since it doesn't contain hard links to itself. I was able to do every update like this (we currently are at 2.5.1).

The update manager will actually perform changes to thoses classes (even when importing from the assets store):

They are using Resources.LoadAssetAtPath instead of AssetDatabase.LoadAssetAtPath.

I think Unity new scenes management may be responsible for this...

Cheers
Title: Re: 2D Toolkit 2.5.3
Post by: unikronsoftware on May 27, 2015, 09:41:20 am
Urgh, no idea why it doesn't do it on my Unity 5 repo - I have 2 parallel checkouts of the same repo, in Unity 4 and 5, as you need to export from 5 for asset store. It definitely has run through the "upgrading API" process at least once :( I'll look into it for the next release.

Moving directory tends to break 2 things - shaders that include fxh files, and if the integrity is broken, it will happily overwrite them, but not if they've been moved.
Title: Re: 2D Toolkit 2.5.3
Post by: jmenossi on May 27, 2015, 11:19:15 am

There is no issue in 2.52 / 3 in Unity 5. The obsolete API message is only visible because we exported the package here using Unity 4.6, you can download the same thing from unity asset store and you won't get the message there. There is no known issue updating, post the error you get and should be able to work it out from there.

Well, I tried a different way to update:
I first updated to TK2.5.3 in my Unity 5.0.1 (it works fine).
After that, I updated Unity to 5.0.2 and, when opening the project I get the message on image 1 (attached) about obsolete API.
If I click "No thanks" and continue loading the project, I get the error on image 2 on the console, about "LoadAssetAtPath".

I tried to choose the "Go ahead" option (automatic API updater) and it seems to work, but it changed several code and prefab files in TK2D, and I am not sure about what it actually did.
Note that Integrity Check is success after automatic API upgrade.


Title: Re: 2D Toolkit 2.5.3
Post by: unikronsoftware on May 27, 2015, 12:59:23 pm
Thanks for posting that - I was on 5.0.1 hence not seeing the upgrade message.

This upgrade thing is getting ridiculous - I really really need to keep on the lowest version I can get away with, i.e. Unity 5.0.1 otherwise everyone using this will have to upgrade to the latest version of Unity, and with Unitys amazing track record of releasing broken stuff again and again its a terrible idea to upgrade Unity straight away... I'll likely have to re-release this after upgrading to the latest Unity 5.
Title: Re: 2D Toolkit 2.5.3
Post by: wagenheimer on May 28, 2015, 02:02:36 pm
"Official support for Unity Windows Mobile and Windows Store in Unity 5"

What is really new here? I was using it before and it seems to be working.
Title: Re: 2D Toolkit 2.5.3
Post by: unikronsoftware on May 28, 2015, 02:23:29 pm
Quote
"Official support for Unity Windows Mobile and Windows Store in Unity 5"

There were known bugs and issues in Unity 4.x, and we didn't have hardware to test on. MS provided some hardware to test on, and we've tested on the hardware with Unity 5 (not Unity 4x and some bugs are still there) and are happy to officially support it now!
Title: Re: 2D Toolkit 2.5.3
Post by: ledvina.m on June 03, 2015, 10:08:23 am
Hello, I'm Unity 5.1f2. With latest 2.5.3 I get Rebulding indexes whenever I click an object with sprite component attached. Also I noticed that you are using Resources.LoadAtPath which does not exists in 5.1. There is only Resources.Load.

Please can you fix that?

Thank you, Marek.
Title: Re: 2D Toolkit 2.5.3
Post by: ledvina.m on June 03, 2015, 10:14:41 am
Ok. I tried 2.5.1 and the Rebuild Indexes again and again is there as well. So seems like Unity messed something really up. So be careful 5.1f2 is somehow broken since it is changing my metafiles and prefabs without me touching them.

Title: Re: 2D Toolkit 2.5.3
Post by: TekuStudios on June 03, 2015, 10:39:22 am
@ledvina.m You should REALLY file a bug report to Unity (and post it in the Beta forums, if possible), they need to know important issues like yours, even when they only affect third-party assets.
Title: Re: 2D Toolkit 2.5.3
Post by: unikronsoftware on June 03, 2015, 07:58:08 pm
Ok. I tried 2.5.1 and the Rebuild Indexes again and again is there as well. So seems like Unity messed something really up. So be careful 5.1f2 is somehow broken since it is changing my metafiles and prefabs without me touching them.

I'll investigate this after Unity release a final version. They've been messing up releases at an alarming rate lately :(
I'll fix Resources.Load in the next release, but the automatic script upgrader should catch it, doesn't it?
Title: Re: 2D Toolkit 2.5.3
Post by: TekuStudios on June 09, 2015, 03:32:48 pm
Unity v5.1 final is already out:

http://unity3d.com/get-unity/update (http://unity3d.com/get-unity/update)

Maybe you want to check it out, unikron. You can read the whole list of new features (including "Crunch texture compression format on platforms which support DXT", maybe it's useful to you) here:

http://unity3d.com/unity/whats-new/unity-5.1 (http://unity3d.com/unity/whats-new/unity-5.1)
Title: Re: 2D Toolkit 2.5.3
Post by: unikronsoftware on June 09, 2015, 11:28:46 pm
Tested in Unity 5.1.0 - seems to work fine on one of our projects. @ledvina.m - if you're getting lockups rebuilding index, try rebuilding the libraries folder (delete and let unity recreate). If your'e version controlled, you should be able to see what Unity changes - if you have it in text that should make things a lot easier to track down.