How do I fix this (Solved)

0 favourites
  • Hello. Okay I first want to say that I didn´t find a good place to ask this. I thought that maybe I could ask it in the bug "department" but I don´t know if this is a bug. I only want to ask a short question to understand if this has happened to someone else too.

    My situation is this: If I just let the game run in a test layout and there are some physical objects there, it runs normally for about maybe 30 minutes, maybe an hour but after that in preview (chrome) there is an error.

    I have checked collision points and changed them etc. but no. It seems to be not about that.

    It´s a javascript error. (I don´t know how to put an image here, so here is the link to image with errors)

    or here

    This error comes with two sprites on the screen (separetely). Both are animated. I wonder if the collision points are the problem even though I changed them to match each other exactly (and none are crossing each other or anything like that)

    I´ll post the capx later if needed but maybe the Pros here can guess what the problem might be. It certainly has something to do with physics yet not very soon. It takes a long time to the error to come? That´s weird, and it happens even when in my test layouts player is not doing anything.

    Can this have something to do with memory. My computer has crashed two times now as i have left the game on it´s own (win 7 64-bit). This kind of crash has before happened very rarely and now 2 times in a short period of time (few days).

  • First check if non of the collision polygones overlap.

  • Posting the .capx would be the most effective way to get a more efficient and quicker response, otherwise we are just guessing.

  • Here is the capx. I thought that maybe the error won´t happen in this "stripped down" version. But it did. Game was run about 18 minutes and bang! Error. Weird.

    Capx: ... .capx?dl=0

  • It has something to do with that rotating beam animation. Now I try without them and see if there is an error.

    edit: after removal of the rotating beams no error so far.

    edit: Fixed the rotating beam in photoshop. Cropped all else out and seems to work better. No error for a long time, but must check more.

  • Computer however crashed during preview (after an hour of so). Don´t know if it has something to do with this but everytime it has crashed, the game has been running in chrome preview.

  • As i said.

    The collision polygones of clark animate to much. It will get stuck.

    The collision polygones of






    overlap eachother, thats a no no for the physics engine

    99% of the sprites have collision polygiones that Construct guessed by import. They are all messed up.

    This is just uncarefull coding.

    Not that i expect you to listen this time.

    It runs fine when i correct the biggest problems.

  • Thanks. I will look at those sprites.

    Edit. It´s very interesting. I never thought that these could cause problems since they are not physical objects, but it´s good to know for now on that even those can be a problem.

    I am sorry if I seemed to be "not listening" since I only thought that the rotating beam´s collision points were an issue. Since it only crashed when that was on layout.

    Thanks again and now I must test if it works now.

    No. Still an error. Must check every sprite.

    edit2: Yes, there was more sprites with this problem (only in my game version not the uploaded capx). Fixed now. Hopefully now everything is working great.

    edit3: No. Not working.

  • Can you upload the 'fixed' capx again ? Will go trough it one by one this weekend.

    The error you get there usaly is about what i mentioned.

    Also, you have to close the browser, between the tests.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Can you upload the 'fixed' capx again ? Will go trough it one by one this weekend.

    The error you get there usaly is about what i mentioned.

    Also, you have to close the browser, between the tests.

    Yes. I will upload it for you (the "full" version this time). Didn´t know about closing the browser. Thanks. Will try that too!

    I will upload it in a minute.

  • Cant promiss all, but can try eh

  • Yes. Thank you very much for trying to help. I will upload it now and give you the link soon.

  • Here is the link: ... .capx?dl=0

    I named the layout where the error comes to ERROR HERE

    These errors started to happen after that rotating beam and those chicken sprites but there certainly were many sprites having collisions points in a wrong way. I wonder if there is a problem if sprites are overlapping in the same layer (when putting them there. That´s why I moved those ground images (background images) separately (which now looks bad of course). There still was an error.

  • I think the first thing you should do is update your version of Construct 2 from r204.2 which is well over a year old now. There should be absolutely no reason for anyone to be using such an old version.

    Supporting such an old version that may have had the bugs subsequently fixed is a waste of everyone's time.

  • Updating now. Testing soon.

    edit. updated. So far no error. I am glad I bought it.

    edit2. Error. Update didn´t fix it. I think it ran more smoothly though.

Jump to:
Active Users
There are 1 visitors browsing this topic (0 users and 1 guests)