matrixreal's Forum Posts

  • ok thanks colludium i will try it later and post result

  • hi

    any one tested or have trick how to submit score or highscore to facebook and twitter ?

    thanks

  • hi aphrodite

    with your tricks i get excellent performance on iphone 4s

    on iphone 4 , before i do your trick it was very very slow ... now with your trick it goes little faster than iphone 4S you understand me ?

  • > hi,

    > i want to know how can i do pause game with very tick

    >

    > explain :

    >

    > iam using every tick ---- set x of background to background.X-5

    > but when i when to make pause (by set time scale to 0) the game is pause but the background stil move

    >

    > thanks

    >

    if instead of doing set x of background to background.X-5, you do set x of background to background.X-5*60*dt, not only the pause will work, but also if the framerate takes a hit during gameplay, the speed of the background in pixels/sec will not be affected.

    FANSTASTIC , EXCELLENT

    i dont know how to thank you

    that work ... and the "X-5*60*dt" save performance and optimisation on iphone 4

    now work fine and i solve my problem regarding iphone 4 (you remember in another post)

  • hi,

    i want to know how can i do pause game with very tick

    explain :

    iam using every tick ---- set x of background to background.X-5

    but when i when to make pause (by set time scale to 0) the game is pause but the background stil move

    thanks

  • mmm ok

    i just tru to optimise my game by reducing at maximum all collisions and polygone colisions

    i get results ... gameplay is fast but just first 5 secondes

    that mean when i lunch it on iphone 4 and go playng game, it run normal but after 5 , 6 seconds game go slower

    on iphone 4s no problem all seem to be good

    any idea about that mr.silver or mr.ashley ?

  • You should not use create object every 0.01 seconds, because thats faster than the threshold for 60 fps (16ms).

    iPhone 4 is just awful, and thats the truth of it. I believe the 4S is still the bulk of the market, with iPhone 5 replacing it quickly.

    yes i know

    but the problem that i not playing good with c2 this why .... i will try optimise it

    about ejecta 1.5 , mr.ashley say that he include all about it on his memory management patch ... its true that the game load faster but performance on game still same

    have you an game on appstore to see your work ?

    thanks

  • Its sad how bad the iPhone 4 is, particles destroy its performance when on an Android phone released at similar times runs fine.

    Might have to draw the line and just aim for iPhone 5 for my future games.

    yes iphone 4 is really poor ... and if we make application or game we have to improve performance for all device ... specially iphone 4 ... because owner of iphone 4 is bigger than 4s or 5 (low cost its normal)

    but tell me have you tryed with ejecta 1.5 ? maybe it will be better ?

    because it say on ejecta forum that performance are good with canvas 2D and webgl too

    the problem that for example my game is simple

    but i use a lot of (set x , move to top , move to bottom , create object every 0.01 seconds )... thats the problem

  • hi i just try it

    nothing change for me

    still bad performance on iphone 4

  • yes i use on collisions

  • i just try it now ...

    when i use on screnn condition with collisions

    it still calculate collisions even when object is outside screen

    and if destroy the object it will calculate 0 collisions

    try an example ...

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • [quote:nsvayk0p]yes

    and if thats like you said better add condition to collisions script

    for example like i said

    if object A (player) is on collisions with object B (ennemy)

    and if object B is on screen

    this will tel to construct engine to calculate colissions only if object B is on screen

    ??? am i logic ?

    I would still say no, I don't see any evidence that it should matter in regards to collision checks. As you can test it pretty easy. Make 2 sprites and put them on the layout.

    In the code you write "On collision object 1 with object 2" that would give you 60 collisions checks, if you move one of the objects out of the layout you get 0 collision checks. So to check if its on layout doesn't matter.

    yes you get reason

    is on layout or on screen it will still calculate same collisions BUT if we destroy the object it will reduce ...

  • > [quote:l2xw0816]Getting rid of objects outside layout will help (they normally are collision checked, and even if not because of collision cells, it still helps a little),

    >

    What do you mean with that they are normally checked if outside layout, its standard that they are excluded if outside layout, or do you mean something else?

    I meant that even if they are outside the layout, they still exist, and C2 still register collisions with them from my experience. Which is normal, not every game can satisfy itself with a predefined layout size.(however, most likely the collision cells will filter that out).

    yes

    and if thats like you said better add condition to collisions script

    for example like i said

    if object A (player) is on collisions with object B (ennemy)

    and if object B is on screen

    this will tel to construct engine to calculate colissions only if object B is on screen

    ??? am i logic ?

  • Also destroy outside.layout saves memory by removing objects no longer in pay. Make sure all you collision check objects are on layers with the same parallax values or it breaks the collision checks. I also disable collisions for objects that are not on those layers such as the UI etc....

    mmm good idea

    is that mean that we have to add another condition to collisions object with another object ?

    for example : if object A (player) is on collision with B (ennemy) (and another condition if object B is on screen ? or on layout ) ?

    yes , no ?

  • Getting rid of objects outside layout will help (they normally are collision checked, and even if not because of collision cells, it still helps a little), reducing collison polygon of object could help during intense phases.

    If your ennemies have an AI that doesn't need to be active when not on screen, you could do something for that too.

    Some collisions maybe could be check only each other ticks.

    At the end, the goal is to keep the amount of calculations as low as possible, while preserving the game.

    thanks aphrodite ... you are really like aphrodite in mythology (saverrrr)

    yes this why i was thinking to destroy object when its outside layout maybe will reduce the collisions calculations ... so as i understand i will help (just little but better than nothing ...)

    and for reduce polygons collisions on object (as you sad i have object with some parts that not need to be checked for example only their X and not ther Y so ... that will help ??? yes ?

    finally i just not understand something ...

    when you say "Some collisions maybe could be check only each other ticks."

    that mean that i have to add another condition to "when object 1 is on collisions with another object B" for example every tick or every seconde ?

    thanks a lot for all

    i just finish my game and publish it on appstore ... but i see that its slower on iphone 4

    so i would like to improve performance at maximum for iphone 4