Hello Guest

Author Topic: Getting an error on sprite collection commit  (Read 5537 times)

sleekdigital

  • 2D Toolkit
  • Newbie
  • *
  • Posts: 3
    • View Profile
Getting an error on sprite collection commit
« on: November 18, 2012, 07:08:46 pm »
Hello,

I get this error when I try to commit my sprite collection....

Actor::updateMassFromShapes: Compute mesh inertia tensor failed for one of the actor's mesh shapes! Please change mesh geometry or supply a tensor manually!
UnityEngine.GameObject:AddComponent()
tk2dBaseSprite:CreateCollider() (at Assets/TK2DROOT/tk2d/Code/Sprites/tk2dBaseSprite.cs:438)
tk2dBaseSprite:EditMode__CreateCollider() (at Assets/TK2DROOT/tk2d/Code/Sprites/tk2dBaseSprite.cs:498)
tk2dBaseSprite:ForceBuild() (at Assets/TK2DROOT/tk2d/Code/Sprites/tk2dBaseSprite.cs:530)
tk2dSprite:ForceBuild() (at Assets/TK2DROOT/tk2d/Code/Sprites/tk2dSprite.cs:221)
tk2dSpriteCollectionBuilder:RefreshExistingAssets(tk2dSpriteCollectionData) (at Assets/TK2DROOT/tk2d/Editor/Sprites/tk2dSpriteCollectionBuilder.cs:1144)
tk2dSpriteCollectionBuilder:Rebuild(tk2dSpriteCollection) (at Assets/TK2DROOT/tk2d/Editor/Sprites/tk2dSpriteCollectionBuilder.cs:1095)
tk2dSpriteCollectionEditorPopup:Commit() (at Assets/TK2DROOT/tk2d/Editor/Sprites/SpriteCollectionEditor/tk2dSpriteCollectionEditorPopup.cs:430)
tk2dSpriteCollectionEditorPopup:DrawToolbar() (at Assets/TK2DROOT/tk2d/Editor/Sprites/SpriteCollectionEditor/tk2dSpriteCollectionEditorPopup.cs:421)
tk2dSpriteCollectionEditorPopup:OnGUI() (at Assets/TK2DROOT/tk2d/Editor/Sprites/SpriteCollectionEditor/tk2dSpriteCollectionEditorPopup.cs:721)
UnityEditor.DockArea:OnGUI()

It's just one sprite with a polygon collider.  If I set to box collider, all is well.
« Last Edit: November 18, 2012, 07:16:01 pm by sleekdigital »

unikronsoftware

  • Administrator
  • Hero Member
  • *****
  • Posts: 9709
    • View Profile
Re: Getting an error on sprite collection commit
« Reply #1 on: November 19, 2012, 01:15:33 am »
Hi there, this is just an annoying warning isn't it? It should have been fixed by now, but there might be cases where it fails.
In any case, I've put it in the TODO to look at before the next release.