Hello Guest

Recent Posts

Pages: [1] 2 3 ... 10
1
Support / Re: Issues with Unity 2018
« Last post by LifeZero on January 15, 2019, 09:26:31 AM »
Hi there.

We had to upgrade to 2018.3 before launch (this January) but now we're not able to commit changes in any collection (just wanted to rescale them). We tried the solution given in this thread (reimporting 2DT), but to no avail. Is there any other workaround for this? Or should we do something else aside from just reimporting the package from the Asset Store?


Thanks in advance.
2
Support / Re: Issues with Unity 2018
« Last post by unikronsoftware on January 14, 2019, 09:49:24 PM »
Cheers for the offer for help guys. Will let you know when the update is ready - still needs quite a bit of work as it requires so many changes.
3
Support / Re: Issues with Unity 2018
« Last post by Arnold on January 14, 2019, 01:04:15 PM »
I gladly help with any testing needed -> hello@tinytouchtales.com
4
Support / Re: Issues with Unity 2018
« Last post by Zeptolab on January 14, 2019, 08:14:37 AM »
Hi, guys! Any news?
5
Support / Re: Issues with Unity 2018
« Last post by csumsky3 on January 11, 2019, 12:06:13 AM »
Oh perfect, that sounds great. Consider me a volunteer!
6
Support / Re: Issues with Unity 2018
« Last post by unikronsoftware on January 11, 2019, 12:01:08 AM »
By manual project upgrade I mean
1. Updating tk2d
2. Starting Unity and running a menu entry to upgrade (it will still work, but you wont be able to edit your collections until you upgrade)
3. Modify your code (potentially?) if you use some parts of the system (eg. if you use tk2dSpriteCollectionData directly, the class ref needs to be changed to tk2dSpriteCollectionDataV2).

I assume its less likely that people direclty access these data classes... the functions are EXACTLY the same, and none of the runtime classes should be affected, eg. tk2dSprite and friends are all exaclty the same.

I have V2 working, just need to sort the migration next, but will need volunteers to help test (BACKUP YOUR PROJECT PLEASE!)
7
Support / Re: Issues with Unity 2018
« Last post by csumsky3 on January 10, 2019, 11:11:16 PM »
By "manual project upgrade" do you mean manually importing some new version of tk2d that you'd pass along?

But yea in general this solution sounds reasonable to me. We're pretty desperate for a solution and can't go backwards in unity versions so I'm pretty open to any ideas that work! Haha. Thanks for the work on this so far.
8
Support / Re: Issues with Unity 2018
« Last post by unikronsoftware on January 10, 2019, 10:45:34 PM »
I think I have a solution to this. It will need a manual project upgrade after switching to 2018, but it should be a one off, and it should automatically upgrade everything. There may be caveats with assetbundles but otherwise should work as a one way upgrade step. That way I can support what is there, but deprecate it and provide a migration for users.

Also it would be unrealistic to support any version prior to 2018 in this update (quite possibly, but still unsure) as the changes will be so far reaching.

Thoughts?
9
Support / Re: Issues with Unity 2018
« Last post by Kirb on January 10, 2019, 02:11:51 AM »
Thanks for the update; it's lucky that our team hadn't updated the project to 2018.3 yet, although we'll need to update to 2019.1+ soon. Hope you're able to find a solution.
10
Support / Re: Issues with Unity 2018
« Last post by unikronsoftware on January 08, 2019, 11:37:02 PM »
This is not looking great - its changed quite substantially and I'm running out of hacks that I can think of to work around this. Will keep plodding at this.
Pages: [1] 2 3 ... 10