Tiled2Unity Update for Unity 5

by Seanba on March 4, 2015

unity-5-logo

I’ve been waiting a long to get my hands on Unity 5 and I’m happy to see that Unity Technologies has followed the lead from Epic’s Unreal 4 Engine and has made their full product free to hobbyist developers — not that you needed any of the professional features to use Tiled2Unity.

I’m also happy to announce that the latest version of Tiled2Unity is compliant with Unity 5. Enjoy.

Update for Unity 4.x users: This update had inadvertently broken scripts for those of you that haven’t jumped to Unity 5 yet – a completely plausible scenario given Unity 5 is less than a week old. I just put up a new version of Tiled2Unity that supports both versions. Sorry for the inconvenience.

For Visual Studio users: When switching between versions of Unity I’ve found that I often have to delete the solution files and have Unity regenerate them. Try that if you are still getting compile errors.

Reminder: The tool we all love the most for 2D development, Tile Map Editor, is seeking support on Patreon. Please consider throwing Thorbjorn a couple of bucks . He’s been good to us.

{ 5 comments… read them below or add one }

Brock March 5, 2015 at 11:25 am

Thanks for being on top of this update. Tiled2Unity has quickly become a vital part of my workflow.

Igor S. March 6, 2015 at 11:29 am

It seems that with this update the support for Unity 4 is a bit broken. Unity can’t compile script ImportTiled2Unity.Mesh.cs because of missing Collider2D.offset functionality.
Good exporter BTW 🙂

Kai Arnold March 6, 2015 at 5:40 pm

Dude you’re incredible. Thanks for the update.

Paul boutros April 9, 2015 at 3:07 am

Hello Sean,

I already sent you an email but I am not sure whether you got it or not.
I would be very interested in buying your megaman Unity engine source code, so if you are interested, please let me know what would be your ideal price.

Thanks,
paulboutros436@hotmail.com

Paul Boutros

Simone February 2, 2016 at 4:44 pm

Hello,

Apparently the fix for 4.x doesn’t work for 4.7, because I had to add:
|| UNITY_4_7
to the lines:
#if UNITY_4_0 || UNITY_4_0_1 || UNITY_4_1 || UNITY_4_2 || UNITY_4_3 || UNITY_4_4 || UNITY_4_5 || UNITY_4_6

In order to get rid of the compile errors.
So if anyone have the same issue with 4.7, this is the solution.

Oh, and thank you for this tool, it’s so awesome 🙂

Leave a Comment

Previous post:

Next post: