Hello Guest

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - 2dddd

Pages: [1]
1
Support / Re: tk2dSprite.SetSprite() bug?
« on: July 24, 2014, 09:16:00 pm »
I've been having a similar issue. When I used SetSprite(), the sprite would change to the correct sprite, but it would not change the collider along with it. However, after I deleted all of the related sprites from my sprite collection and then once again added them to the sprite collection and gave them new colliders in the sprite collection window, then there was no problem at all and it would change the colliders just fine.

2
The same thing keeps happening to me. I noticed that when the sprite will not show in edit mode, the Mesh Filter component in the Inspector shows "Missing (Mesh)" for the Mesh drag-and-drop box. But when the sprite appears again, the drag-and-drop box shows a symbol for the mesh as it should. I don't know why it would be doing this seemingly randomly. I'm using a Mac by the way.

3
Support / Problem with tk2d custom box colliders not working
« on: July 18, 2014, 07:03:26 pm »
I ran into what seems to be a tk2d bug, but I found a way to fix it in my case. I was using custom box colliders on some of my sprites in one of my tk2d sprite collections. The colliders were working fine when the game was running, but later I adjusted some colliders in that same sprite collection on some different sprites, and then all of a sudden the box colliders on my aforementioned sprites suddenly would not work anymore during runtime.

After trying all kinds of things, I found a way to fix the problem: Select the game object in the Hierarchy, and then in the Inspector change its sprite to a different sprite and then switch it back to the original sprite. After I did this for each of my faulty sprites, then they worked perfectly once again. So if someone has a tk2d sprite with a custom box collider that suddenly will not work correctly during runtime, then try switching the sprites in the Inspector and see if that fixes the problem. I hope this helps anyone who runs into this problem.

4
Support / Re: frame custom box colliders bug?
« on: July 18, 2014, 06:50:46 pm »
I had the same problem. I was using custom box colliders on some of my sprites in one of my tk2d sprite collections. The colliders were working fine when the game was running, but later I adjusted some colliders in that same sprite collection on some different sprites, and then all of a sudden the box colliders on my aforementioned sprites suddenly would not work anymore during runtime.

After trying all kinds of things, I found a way to fix the problem: Select the game object in the Editor, and then in the Inspector change its sprite to a different sprite and then switch it back to the original sprite. After I did this for each of my faulty sprites, then they worked perfectly once again. So if this happens to you again, try switching the sprites in the Inspector and see if it works for you.

Pages: [1]