Hello Guest

Author Topic: Asset server  (Read 4940 times)

Dragonhill

  • Newbie
  • *
  • Posts: 1
    • View Profile
Asset server
« on: April 26, 2012, 06:38:19 pm »
Hi everyone, My team has been using 2Dtk with the asset server since the beginning of the year and it works pretty well most of the time. The main problem was that the -tk2d object in the project view is never shared on the asset server (something about not recognizing it). So basically every time a new change is made by one member the other members will need to update their -tk2d objects by hitting commit on every atlas. 

The simple solution for us was to just rename the file. I used _tk2d. 
You can do this by finding the tk2dEditorUtility.cs file. look for line 117. 
It should be <const string indexPath = "Assets/-tk2d.asset";>
Change it to <const string indexPath = "Assets/_tk2d.asset";> 
A new object will be created on next commit.
You can delete the old object after this happens

unikronsoftware

  • Administrator
  • Hero Member
  • *****
  • Posts: 9709
    • View Profile
Re: Asset server
« Reply #1 on: April 26, 2012, 06:51:14 pm »
Hi,

The tk2d object should not be shared on the asset server - it is reconstructed when missing. The best thing to do is to delete it before updating / merging any new changes. You don't have to hit commit on every atlas - just deleting the file and letting it recreate itself should be more than enough.

If you check it in, you could end up with some really strange problems where the data is incorrect after merging in changes.

Finally, the next 1.70 beta has much much more robust handling of the index - it will automatically rebuild it when it detects things which are out of sync.

Hope that helps!

gearworks

  • 2D Toolkit
  • Newbie
  • *
  • Posts: 3
    • View Profile
Re: Asset server
« Reply #2 on: March 13, 2013, 09:43:05 am »
Is this still the recommended approach; deleting the tk2d object before updating?

unikronsoftware

  • Administrator
  • Hero Member
  • *****
  • Posts: 9709
    • View Profile
Re: Asset server
« Reply #3 on: March 13, 2013, 11:41:23 am »
You don't HAVE to, but deleting it is the best approach. If the system identifies that the index isn't valid, it will reconstruct itself or at least attempt to do so, but, it won't be able to identify changes within sprite collections.

"Rebuild Index" after updating.
« Last Edit: March 13, 2013, 12:34:53 pm by unikron »