Taximan's Recent Forum Activity

  • —

    Memory is not a problem.

    I'm getting a lot of negative reviews on Play store, before my games needed 200/300 megs of memory, but I updated them to C3, and now they need more than 700, and they are the same game with the same sprites.

  • My game has many sprites of many sizes and with many animations.

    It could save a lot of memory if you could edit the spritesheet, because they are generated randomly wasting a lot of memory.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads

  • I decided to increase x2 the size of my sprites, and the result... the game needs less memory...

    That shows how badly it manages C3 memory, this seems a joke, but projects with many sprites can not run on phones with less than 4g memory.

    Before

    After increasing the size of the sprites

  • This is a sample of how bad C3 uses memory.

    The sprites of the levels are in different folders, but C3 creates groups that lose a lot of memory.

  • Order all sprites in their folder, the game needs less memory, but it is still much higher than C2.

    I may not understand his, my English is very bad :p

  • Use C3 to update all my C2 games, but the use of RAM is multiplied by 3.

    Just change code, the sprites are the same.

    I think I found the answer to the problem.

    In one of my games C2 generates 532 Spritesheet, C3 only 167.

    C2 only loads the necessary sprite sheet into memory, C3 loads many sprit sheets with unnecessary sprites.

    Against bigger is my game, more memory needs in phases that are finished long ago.

    This is a huge problem for big-size games.

    In this example you can see how C3 loads a Spritesheet 2048x2048 in the 20 fases that poses the game, The more sprites you have, the more Spritesheet you need to load in all fases of the game.

    Sorry for my English... is very bad...

  • I think I found the answer to my problem.

    The same game exported in C2 needs 600m less memory to run than on C3.

    C2 generates 532 Spritesheet, C3 only 167.

    C2 only loads the necessary spritesheet in memory, C3 loads many spritesheet with unnecessary sprites.

    This is just my guess.

  • Import the construct 2 project, if in construct 2 needed 364 megs, I do not understand why in Contruct 3 uses 1300.

    Compress the images with Tinypng, that greatly reduces the consumption of RAM, the game works perfectly on a phone with 1g memory.

    You can check the version of construct 2

    play.google.com/store/apps/details

  • Delete all the text but the problem is not solved.

    In another test delete the rewar ads, not solved...

    A capture of the properties of my project.

  • I use the 125, but I have many text objects, I have more than 100 .... omg ... will I have to change them all?

  • Can't anyone help me? ;(

  • This is the game in motion, I hope I have no ram memory problem...

Taximan's avatar

Taximan

Member since 8 Feb, 2015

Twitter
Taximan has 2 followers

Connect with Taximan

estudio2pastores.mozello.com

Trophy Case

  • 9-Year Club
  • Forum Contributor Made 100 posts in the forums
  • Regular Visitor Visited Construct.net 7 days in a row
  • RTFM Read the fabulous manual
  • Email Verified

Progress

13/44
How to earn trophies