Create account / Log in

Layers and memory usage

Talk about module design ideas and techniques.

Moderators: Tim M, uckelman

Layers and memory usage

Postby Va7Ue » February 9th, 2019, 3:22 am

I am attempting to use layers to represent the modifications available for each card in several decks of cards. Each modification has a separate location on the card. Unfortunately I can't use a common layer prototype to represent the modifications so I've been adding a layer trait for each modification per card. As I've done this I noticed a large increase in memory usage, receiving out of memory errors, based on the amount of layer traits that have been added. I've bumped the heap size up to 1500 which has allowed the module to load.

Currently there are 892 modifications available, which will require a layer trait for each one, and each layer contains 19 levels. So a couple of questions. 1) Is there a better way to do this? 2) Do layer traits act as their own object, rather than acting as reference, even though they are using the same image for each layer level?

Thank you.
Va7Ue
 
Posts: 1
Joined: January 9th, 2019, 12:35 am

Return to Module Design

Who is online

Users browsing this forum: No registered users and 2 guests