Jhaelen wrote:Edit : problem solved, I deleted three levels that I have to rework anyway because I was not satisfied with the result. These three levels used the Asian Tileset, and by removing it I'm now way under the "out of memory" error. I'm now looking to somehow merge the three remaining levels in the 40 others in order to avoid this fu***ng error to pop up again.
Number of levels has essentially no bearing on memory usage. Textures are by far the biggest thing to worry about, along with the memory balloon when saving. When the game is saved, every object has to be serialized. Objects with minimalSaveState set to true have only their name, id, x, y, facing, elevation, and level saved, so they are not too expensive to save. But objects without minimalSaveState have that, plus their world position/rotation, plus every property of all of their components saved, so if you are forgetting to put minimalSaveState on objects that are used a lot such as walls, you will run into horrible saving performance and high memory usage.