Construct 2 (r267) closes itself randomly.

    Although the thread is for version 267, I think that most of the reports here are referred to version 269.

    It might have something to do with Spriter's scon files. I've noticed that the more scon files i have in my project, the more frequently it will crash. I only use scon files for the player character now, and use spriteheets for the enemies etc.

    This started happening late 2018 for me.

    Same thing for both Win 7 and 10.

    Hello, it's still happening in r269 release Ashley

    Does Ashley here with us? why isn't any of response?

    As ever, there is very little we can do without reliable steps to reproduce the problem. There still does not appear to be anyone who's found reliable steps to reproduce.

    It might have something to do with Spriter's scon files. I've noticed that the more scon files i have in my project, the more frequently it will crash. I only use scon files for the player character now, and use spriteheets for the enemies etc.

    This started happening late 2018 for me.

    Same thing for both Win 7 and 10.

    I do not use Spriter and I also suffer from crashes, although the last was a few days ago and I am using C2 every day more than 5 hours a day.

    At this point wouldn't it be better to just rollback to a release that is stable?

    If construct randomly closes it self but not very often I would say just stick with the release. That's what I'm doing (ALSO CTRL-S !!! LOL)

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

    Now that you've mentioned Image Editor, I kind of remembered, that the first time when C2 closed was when I was doing something with one of the sprites in Image Editor. I think I was closing it, when C2 just closed itself completely. And one time it just corrupted one of the frames. I can't remember what the error was saying, but I had to delete the frame and replace it with other file. Not sure if it's connected to the main topic, but maybe this info will help.

    I'm also now starting to think it has something to do with the image editor.

    I've always been able to edit for long periods of time on the events sheet without crash, but now that i've been working a lot on the layout and using the image editor, C2 seems to be more prone to crash. I have autosave disabled and save manually every 5 minutes or so. I also don't get any notice.

    Hi, I´m using the last stable version os C2 and have the same issue. I don´t know what really cause it, it crashes with simple things like change the name of an object or changing an image.

    As ever, there is very little we can do without reliable steps to reproduce the problem. There still does not appear to be anyone who's found reliable steps to reproduce.

    I feel so much sad while reading this, seems like a robot machine replied this :(

    > As ever, there is very little we can do without reliable steps to reproduce the problem. There still does not appear to be anyone who's found reliable steps to reproduce.

    I feel so much sad while reading this, seems like a robot machine replied this :(

    A robot could fix this issue without any steps to reproduce it.

    Jokes aside, still no crashes for me using Windows 7. Does anyone in here use older Windows versions and crash?

    > As ever, there is very little we can do without reliable steps to reproduce the problem. There still does not appear to be anyone who's found reliable steps to reproduce.

    I feel so much sad while reading this, seems like a robot machine replied this :(

    I say this a lot, because it's true for all bug reports. I'm afraid reports without reliable steps to reproduce are usually useless. So until anyone can figure that out, there's almost nothing we can do towards investigating this, let alone fixing it.

    But if we find out the version where the bug started, wouldn't that help? You could track down the changes?

    Like all the information required for bug reports, it can help, but often does not in itself lead to a solution. This is why we require full reports for every issue: it can't be known in advance what will lead to the solution, so we require as much information as possible to help us identify what is going on. Very commonly people miss out crucial details which delays the investigation. We really need comprehensive reports in every case.

    In my case it happens when I'm changing an image or even a parameter in the event sheet. Thhe last time it crashes when I try to change the number in a variable. Is too random.

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