Starling Forum

1. 

   MacShrike
   

   Expert Bird
   Joined: Apr '12
   Posts: 194

   Ls,

   Im just testing out some code to check performance vs nr of clips onstage and such.

   For my tests I just:
   embedd some .pngs, create some bmps from them, create textures from those.
   in the main class contructor.

   Then in a loop i create new images from those textures and add them to the stage.
   After added to stage i move some of em. A bit like the sausage demo.
   Nothing fancy.

   I was wondering where/when the actual upload to the gpu takes place and if putting my textures in an atlas would improve speed.
   There are only +/- 9 textures I use for the tests.

   Regards,

   Mac

   Posted 1 year ago #
2. 

   Daniel
   

   Primary Feather
   Joined: Jan '10
   Posts: 2,445

   The texture data is uploaded to the GPU exactly in the call to "Texture.fromXYZ()". By re-using those texture objects, nothing new has to be uploaded.

   When you use a texture atlas, only one single texture is uploaded to the GPU. That allows Starling to render your code very efficiently.

   Thus, a Texture Atlas is always recommended for optimal performance. On a very simple game that's targeting only the browser, you can be lazy and skip that, but for all other use-cases, I'd go for it.

   IMHO, it even makes working with textures more easy, because you don't have to constantly write new Embed Statements. That alone is worth the effort!

   Posted 1 year ago #
3. 

   MacShrike
   

   Expert Bird
   Joined: Apr '12
   Posts: 194

   Thx.
   I will def. be using every single byte of code i can squeeze out of starling.
   But for now im just creating all kinds of small tests to see how far i can take things before my fps drops to much.
   I just wanted to be sure that this simple texture adding didnt spoil the possible result.

   Mac

   Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.