iopmade.blogg.se

Texturepacker unity upgrade
Texturepacker unity upgrade











texturepacker unity upgrade
  1. TEXTUREPACKER UNITY UPGRADE HOW TO
  2. TEXTUREPACKER UNITY UPGRADE UPGRADE

Skin) Please see the example scene Mix and Match Skins on how to use the new Skin API to combine skins, or the updated old example scenes Mix and Match and Mix and Match Equip on how you can update an existing project that was using the old workflow. Skin customSkin = new Skin( "custom skin") ĬustomSkin. If you are using UnshareSkin() you can replace it as follows: replace occurrances of skin.AddAttachments() with skin.AddSkin(). To fix any compile errors, replace any usage of Skin extension methods with their counterparts, e.g. All Skin extension methods have been removed, these are replaced by the new Skin API.

texturepacker unity upgrade

If you receive compile errors from your own code because of using renamed and no-longer existing methods, the following points from the changelog will help to perform the required steps to make your own code compatible again: Some methods have been renamed or replaced in 4.0.

  • In the Project panel select RightMouseButton - Reimport All (or select Reimport on the folder containing your skeleton assets).įor notable changes to the API, please see the Changelog, sections C# and Unity.
  • Import the latest Spine-Unity 4.0 unitypackage.
  • Replace the old exported 3.8 skeleton assets with their re-exported 4.0 counterparts.
  • Delete your old "Spine" and "Spine Examples" folders.
  • Note any custom changes you made to your Spine-Unity runtime.
  • This is to make sure there are no active Spine objects.
  • Close all open scenes and create a new blank scene, and have nothing selected.
  • Create a backup of your 3.8 project to be on the safe side.
  • TEXTUREPACKER UNITY UPGRADE UPGRADE

    Recommended upgrade steps for upgrading from 3.8 to 4.0: If you have many projects, we suggest automating exporting your project files:įor example, here is a script we use to export all the Spine example projects and to create texture atlases: The skeleton data files need to be re-exported using Spine 4.0. Note: Json and binary skeleton data files exported from Spine 3.8 will not be readable by the Spine-Unity 4.0 runtime!

    texturepacker unity upgrade

    If you are upgrading from an older version of spine-unity than 3.8, please see the respective upgrade guide on how to adjust your code and assets accordingly: As the official 4.0 release is a few days away, you can find the officially compiled Upgrade Guide below.













    Texturepacker unity upgrade