Game Development Reference
In-Depth Information
Figure 5-16
is a snapshot of the amount of requests my game was making before moving
over to texture atlases.
Figure 5-17
shows the optimized build where about 90 percent of the
artwork is now being loaded via texture atlases.
Figure 5-16. Here you can see the total number of connections before moving over to texture at-
lases.
Figure 5-17. The number of connections is now lower after moving over to texture atlases.
As you can see when comparing
Figure 5-16
's Items count to
Figure 5-17
, I was able to cut
down 12 percent of my requests going from 200 down to 176. While that may not sound like
a big savings, check out the size of the game. My game went from 6.8mb down to 4.9mb,
which is almost a 23 percent reduction in file size. This is huge if you are trying to run your
HTML5 game on mobile browsers and also improves the memory footprint on any platform.
