Atlas for uGUI using Texture Packer

UI UGUI
1

As the title. implement the Atlas for uGUI using Texture Packer and see the result in project panel.

2

?

3

I think what he means is: Right now, when you’re building your GUI, it always uses the raw original images; it’s not until you hit play that it switches to the packed atlas.

4

Yeah it doesn’t work like Daikon Forge or other sprite packers where it actually creates an atlas object in your project view. You just set the packing tag in the import settings and use the sprites directly. At run-time the draw calls will consolidate. One annoying thing about this is that if you have tons of sprites that you need script to choose from by string (like an inventory list or something), then you need to have something that holds a reference to every single sprite. I made a SpriteHolder component.

5

It is possible to enable the sprite packer to get more manual control:
http://docs.unity3d.com/Manual/SpritePacker.html

6

Even with the sprite packer enabled, the GUI doesn’t use the packer until you are in play mode. (If you are using a packed sprite that is Compressed, you can plainly see the difference; it’s crisp and clear when laying it out and becomes compressed in play mode.) Also, there are bugs using the sprite packer with UI.

7

You may e.g. create a scriptable object that holds the references to all your sprites. That scriptable object is updated whenever the atlas is created. It would be necessary to create a custom bundler as shown here, but it certainly would need to modify the scriptable object to update the references:
http://docs.unity3d.com/Manual/SpriteEditor.html

8

What I mean is I want use the TexturePacker to generate the Atlas and then import it to Unity and there is one Atlas just as the NGUI Atlas on the Project Window.

9

When I want change the sprite at run-time I can use the name of sprite to change just as doing as NGUI do so.

1 Like
10

Why? Just use the in built packer and then change the sprite reference. Unity will to this automatically without needing string name lookups.

11

For the convenience to change the sprite in code.I think the TexturePacker(Pro) is the professional even the standard for the Atlas generation.

12

Dude, you can change the sprite in code. Store the reference. If your so hell bent on doing it the way TexturePacker does it, then why don’t you use TexturePacker?

13

uGUI support the TexturePacker for atlas importing ? TexturePacker will generate one texture and one text file for atlas, how those files can be use for uGUI sprite packer ?

14

In MMO Game, the inventory Icon comes from its name in config file,that is why I need use the name for change sprite at code.

15

How about this.

16

Thanks very much

17

I’ve been using the official TexturePacker Importer. It works great with the 4.6 beta except for sliced sprites, which I think the TP Importer doesn’t support (yet). So each time I publish my atlas again in TP I have to:

  • Click into Unity so the TP Importer loads the newly published sheet
  • Delete the .tpsheet file
  • Open the Unity Sprite Editor and set up the borders again on my sliced sprites

It’s a little tedious but I assume that TP will eventually update the extension to work with sliced sprites. Also, step 2 is required because otherwise the TP Importer instantly undoes step 3 the moment you hit “Apply” in the Unity Sprite Editor.

1 Like
18

I found a little shortcut. If you leave the Unity Sprite Editor open while you publish the new TP sheet you can do this:

  • Click into Unity so the TP Importer loads the newly published sheet

  • Delete the .tpsheet file

  • Click into the Sprite Sheet Editor (that you left open) and adjust just one border attribute on one sprite, then hit “Apply”

It’ll re-apply ALL border attributes again, saving you work.

2 Likes
19

How can I store the TextureImporter spritesheet to a list of sprite ?

20

You need to use the TexturePacker Importer. It’s free from the Asset Store. Tutorial on how to use it here.