Exploring Pixi Asset Pack 1.0 – Benefits and Current Limitations

[furic]

It's exciting to see that Pixi's Asset Pack has officially reached version 1.0. I've taken a deep dive into it to assess whether it can benefit our projects. So far, it looks promising, though there are still a few issues that need to be addressed. I'd love to discuss it here and hear if anyone else has had similar experiences.

Reasons to Use Asset Pack:

• Texture Sprite Packing: No more manual work with Texture Packer.
• Automated Compression & File Formats: Keeps a 100% PNG, while automatically generating compressed PNG and WebP versions.
• Mipmaps Generation: Devices with smaller resolutions can use lower-res textures for better performance.
• Bundle Manifest Generation: No more hard-coded asset lists.
• Hash Versioning: Ensures the latest files are always used.
• Artist-Friendly Workflow: Artists only manage raw assets, while export automation handles the rest.

Issues/Limitations:

• Spine Atlas Export Issues: Spine atlas not correctly export (submitted a PR for spine-runtime).
• Bitmap Font Export Problems: Bitmap fonts are not exporting properly (submitted an issue).
• Sound Sprite Support: Currently unsupported (submitted an issue).

While Asset Pack is still in its early stages, I believe it has great potential to become an essential tool for Pixi development. Has anyone else worked with it? I'd love to hear your thoughts and experiences!

[wolfv]

Hi @furic - sorry but I think you unfortunately reached the wrong repository :) You are probably talking about pixi.js?

Cheers!