You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With Cache Buster, Compression and Mipmaps turned on, Bitmap font cannot be correctly phrased in the manifest. This causes error when loading the bundle.
desyel.png got phrased correctly, exported as all resolutions and formats with hashes, but desyel.xml was not phrased and simply got copied to the output folder.
When running PIXI.Assets.loadBundle('game-screen'), PIXI cannot find desyrel.png (because it's phrased to desyrel-F3uydg.png etc), 404 error occurs.
Expected Behaviour
desyel.xml should get phrased into all resolutions, formats with hashes, and each reference to its corresponding texture. Similar to how the spine atlas gets phrased.
Checking the Pixi.js Bitmap test-assets, each bitmap texture has its own data file (XML, FNT, etc), although the data files should be almost the same, but with different filename and size values.
Pixi's Side Solution?
I think this can also be fixed on Pixi's side. We always have ONE XML with different textures. When Pixi reads the XML and sees desyel.png, for example, it should reference back to the manifest and try to load the correct texture from the manifest.
The text was updated successfully, but these errors were encountered:
furic
changed the title
Bug: Bitmap font not getting phrased correctly
Bug: Bitmap font XML not getting phrased correctly
Sep 6, 2024
furic
changed the title
Bug: Bitmap font XML not getting phrased correctly
Bug: Bitmap font XML not phrased correctly
Sep 8, 2024
furic
changed the title
Bug: Bitmap font XML not phrased correctly
Bug: Bitmap font XML not phrased and exported correctly
Sep 8, 2024
Description
With Cache Buster, Compression and Mipmaps turned on, Bitmap font cannot be correctly phrased in the manifest. This causes error when loading the bundle.
Steps to Reproduce
game-screen
bundle folder.Current Behaviour
desyel.png
got phrased correctly, exported as all resolutions and formats with hashes, butdesyel.xml
was not phrased and simply got copied to the output folder.In
desyel.xml
, it still reference thedesyel.png
:When running
PIXI.Assets.loadBundle('game-screen')
, PIXI cannot finddesyrel.png
(because it's phrased todesyrel-F3uydg.png
etc), 404 error occurs.Expected Behaviour
desyel.xml
should get phrased into all resolutions, formats with hashes, and each reference to its corresponding texture. Similar to how the spine atlas gets phrased.Checking the Pixi.js Bitmap test-assets, each bitmap texture has its own data file (XML, FNT, etc), although the data files should be almost the same, but with different filename and size values.
Pixi's Side Solution?
I think this can also be fixed on Pixi's side. We always have ONE XML with different textures. When Pixi reads the XML and sees
desyel.png
, for example, it should reference back to the manifest and try to load the correct texture from the manifest.The text was updated successfully, but these errors were encountered: