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.

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.

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

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 :(

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.

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.

This is understandable. But why not just roll back to the stable version then (r265)? It would save a lot of nerves to the users (plus, you won't have to pay attention to this question until you will have time to figure it out) and it won't take much time (I am speaking only about the procedure of build uploading through Steam dev's service).

> 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.

This is understandable. But why not just roll back to the stable version then (r265)? It would save a lot of nerves to the users (plus, you won't have to pay attention to this question until you will have time to figure it out) and it won't take much time (I am speaking only about the procedure of build uploading through Steam dev's service).

Agreed, I remember when nvidia do the same cause the new update has problems. Scirra cpuld do the same. If only I could open my projects in a previous update but it can't, so the roll back could be a good temporal solution.