• Content Count

  • Joined

  • Last visited

About Agile

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I have finally managed to get nice quality compressed textures for all platforms with relatively small file size, and they all work with the plugin pixi-compressed-textures plugin. However, the framework I use is loading assets automatically and provides ArrayBuffer already, so it would be nice to just create the compressed texture from the ArrayBuffer directly (I do know the file format of the texture ArrayBuffer upfront). (I'm aware that there is a new code for compressed textures in the latest pixi, but no matter what I do I get wrong format error or range errors, and the PIXI.INTERNAL_FORMATS doesn't have ASTC in its list, which I need, and works automatically and perfect with the plugin)
  2. I hear you, I am using vite and it has been working pretty good for a good while, but ran into problems here. I have been able to get it up and running now by wrapping the source js from the dist folder of pixi and pixi-compressed-textures into its own file and namespace and then export default PIXI from there. This way the plugin worked, and my first compressed texture is showing. Not the best way, but for now I have something showing on the screen and I can start experimenting, pulling the threads and then figure out the optimal setup later. Thanks for getting me there. I'm also trying the version you pointed me too, the latest vanilla js download version with included support for compressed textures. Also this version of PIXI is up and running now, but I'm currently struggling a little with getting a compressed texture to work here. I am cycling through formats, but nothing on the screen yet (exporting a multitude of formats in ktx, dds, as well as going through the different formats in PIXI.INTERNAL_FORMATS.*) but for the moment I either get Error: Invalid (compressed) texture format given! or RangeError: Invalid typed array length: ####).
  3. Pardon my noobness, js makes me dizzy - but how to I add it as global without imports? I do not need the URL resolver, as I have the compressed textures available as ArrayBuffer already. So I tried to check if it was available to the 5.3.3 build from yarn/npm which I have used so far. import * as PIXI from 'pixi.js'; console.log(PIXI.CompressedTextureResource); console.log(PIXI.INTERNAL_FORMATS); But it logs as undefined.
  4. I need to use the pixi-compressed-textures plugin, but I can't figure out how to use it with import statement. I'm not in an environment where I can use require().
  5. I have a webpage which needs multiple Pixi elements stacked in different places of the page DOM. Pixi elements are continuously created and destroyed as the webpage is used. At the most there will be 5 Pixi elements used/shown at once. The Pixi elements have their own scope and functionality, and does not need to "know" about each other. I have to avoid memory leaks as the page can be used for quite some time. Pixi elements can be created and destroyed for hundreds of times while the webpage are in use Is it good practice just to keep creating and destroying multiple PIXI.Applications (and show multiple at once)? = new PIXI.Application(); // Use component ... // Finished, true); Or should I try to clean and re-use the Pixi.Application instances? Or should I do this in a different way?