CODEWITHSUNDEEP
iossprite-kit
A Tyshka
A Tyshka

Reputation: 4090

Memory Usage of SKSpriteNodes

I'm making a tile-based adventure game in iOS. Currently my level data is stored in a 100x100 array. I'm considering two approaches for displaying my level data. The easiest approach would be to make an SKSpriteNode for each tile. However, I'm wondering if an iOS device has enough memory for 10,000 nodes. If not I can always create and delete nodes from the level data as needed.

Upvotes: 1

Views: 159

Answers (1)

Skyler Lauren
Skyler Lauren

Reputation: 3812

I know this is meant to work with Tiled, but the code in there might help you optimize what you are looking to do. I have done my best to optimize for big maps like the one you are making. The big thing to look at is more so how you are creating textures I know that has been a big killer in the past.

Swift https://github.com/SpriteKitAlliance/SKATiledMap

Object-C https://github.com/SpriteKitAlliance/SKAToolKit

Both are designed to load in a JSON string too so there is a chance you could still generate random maps without having to use the Tiled Editor as long as you match the expected format.

Also you may want to consider looking at how culling works in the Objective-C version as we found more recently removing nodes from the parent has really optimized performance on iOS 9.

Hopefully you find some of that helpful and if you have any questions feel free to email me.

Edit

Another option would be to look at Object Pooling. The core concept is to create only sprites you need to display and when you are done store them in a collection of sorts. When you need a new sprite you ask the collection for one and if it doesn't have one you create a new one.

For example you need a grass tile and you ask for one and it doesn't have one that has been already created that is waiting to be used so it creates one. You may do this to fill a 9 x 7 grid to fill up your screen. As you move away grass that gets moved off screen gets tossed into the collection to be used again when the new row comes in and needs grass. This works really well if all you are doing is displaying tiles. Not so great if tiles have dynamic properties that need to be updated and are unique in nature.

Here is a great link even if it is for Unity =)

https://unity3d.com/learn/tutorials/modules/beginner/live-training-archive/object-pooling

Upvotes: 1

Related Questions