title: Advantage of the TextureAtlas and how to use it right
body: <p>I am refactoring my small RPGs I developed in libgdx. </p>
  
  <p>I got a general question how to use the texture atlas right. I got like 100actors with around 10 Kinds of Sprites. Current i don't use an atlas but I'd like to to increase the renderingperformance since this is the only thing that does take long inside if my game loop.(got around 100binds and 15 rendercalls..) </p>
  
  <p>So it took a look at the <code>TextureAtlas</code> Class <a href="https://github.com/libgdx/libgdx/blob/master/gdx/src/com/badlogic/gdx/graphics/g2d/TextureAtlas.java" rel="nofollow">link to git</a> and was wondering how I get more performance out of It. If I get a sprite of it with the right texture I do get a copy so I still would switch the OpenGL binding right? So that wouldn't be a better solution a special if I have like 100 actors all with it's own sprite or am I wrong with it and I just didn't get that right?</p>
  
  <p>The Atlas itself does recommend not to call the <code>getsprite</code> multiple times but I would need to do so, so that every actor has it's own sprite with a own status.</p>
  
  <p>Maybe you could give me a little example how I use multiple sprites from one atlas without switching the binding of OpenGL. That should be the reason to use the atlas but I don't get it at the moment.</p>