Jump to content

Search the Community

Showing results for tags 'spritesheet atlas memory'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • HTML5 Game Coding
    • News
    • Game Showcase
    • Facebook Instant Games
    • Web Gaming Standards
    • Coding and Game Design
    • Paid Promotion (Buy Banner)
  • Frameworks
    • Pixi.js
    • Phaser 3
    • Phaser 2
    • Babylon.js
    • Panda 2
    • melonJS
    • Haxe JS
    • Kiwi.js
  • General
    • General Talk
    • GameMonetize
  • Business
    • Collaborations (un-paid)
    • Jobs (Hiring and Freelance)
    • Services Offered
    • Marketplace (Sell Apps, Websites, Games)

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Twitter


Skype


Location


Interests

Found 1 result

  1. As we all know it's not easy to have all textures in power of two size. So a lot of memory is wasted when such textures are loaded into memory. Atlases helps with that, because it optimally packs all textures into texture of power of two size. In our case we could easily save 30% of memory. I'm wondering is there any way to reduce memory footprint using texture altases in pixi.js? Texture packages are produced with TexturePacker ( https://www.codeandweb.com/texturepacker ) and loaded following this pixi tutorial ( https://github.com/GoodBoyDigital/pixi.js/tree/master/examples/example%202%20-%20SpriteSheet ). The main problem is that creating PIXI.Sprite object with texture from atlas increases memory usage twice, because looks like it creates texture cache for sprite. I'm wondering maybe there is some way to eliminate texture cache and make PIXI.Sprite object just a metadata that defines rectangle in the atlas instead of copying texture rectangle from atlas to texture cache?
×
×
  • Create New...