Ah, I see. (This is the kind of detail that gets lost in long threads...)

I've added a new beta branch on Steam that is fixed to r265 so you can use that to roll back if you want. But that doesn't itself do anything to solve the problem.

Thanks a lot, really appreciate it!

> Then what about making a beta branch with r265?

What does that actually solve? You can already roll back to r265 if you want. Just download and install it. It won't open projects saved in newer releases, but if you're willing to modify the project file to allow that, then you can already go ahead and do it.

As relixes said, I've meant Steam version. You can't roll back manually, if you're using Steam version of Construct 2.

Ashley,

I see your point. Then what about making a beta branch with r265? That way, users that know how to open a file in an older version (it's possible to do that) will "revert" manually and I think this will solve this question for some time, at least, while saving the time and nerves to people and to yourself. I understand that it's not a great thing from the point of actually finding out the cause of all this, but this issue ruins people's workflow for months now, and it doesn't seem like the solution is somewhere near.

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

Ok, so far I had one crash, roughly after 15-20 minutes of working, after opening C2 that was updated to beta r268. I am not sure what caused it, though. I was just adding a new action when C2 suddenly froze and closed itself without any error. Just like it happened before. I checked out the autosave that was made close to the time that it crashed, and it seems like it works fine, on the first look.

P.S. I can confirm, though, that UI elements, that were previously bugged, now work fine.

Hi all! Just wanted to share a link on my first released game on Steam. It's called Flat Trip. I started to use Construct 2 in the summer of 2017 (July, if I remember correctly). And I've finished and released my first game on 3 Oct, 2018. All stuff made by me, except music and sounds. Game is rather short (can be completed under an hour), but contains fun hand-drawn graphics, nice music (OST is available as free DLC) and a little art-book, for those who is interested in knowing a little bit more about the lore of the game. It's also has a discount now, that will continue until 20/04/2019 10:00 (PST). Cheers! store.steampowered.com/app/918740/Flat_Trip

Okay, I will opt-in into beta and try to work for some time in it tomorrow. If something will change, I'll post it here. Thanks.

Hm, yeah, I can see your point, since not everybody watches forums/other info sources about current state of Construct, so that may lead a lot of people into confusion.

Well, then I'm out of ideas. I just hope that you guys can look into that issue (with r267) and fix it, so people can get back to work without constantly worrying about losing progress. I don't even care that much about bugs with UI elements. Only those sudden crashes worry me a lot.

Well, thanks again for looking into that issue and I hope the situation can be resolved soon.

Hello,

I've got a proposition to roll back the Steam version of Construct 2 to r265, since using r267 brings a few really annoying bugs (crashes, Z order window and possibly other UI elements not working properly).

I get it that Scirra staff is probably busy building C3, so it will be a while until we can get another update for C2, so the easiest way to make those crashes stop is to just roll back to r265 for now, which is really stable compared to r266 or r267.

I tried to resolve that issue on my own by downloading r265 from the site and replacing the files in Steam directory, but Steam forces an update anyway. You can only postpone it, but it will be updated. So this way of dealing with that issue is not an option.

I've got no other way, but to ask for your help. Please, bring back r265, so we can work without constant thinking about those random crashes (I've posted about them in Bug section).

I've said "we", because I've encountered other people, that are on Steam and that have those crashes too. I'll try to reach them so they can share their thoughts about it here.

Thanks in advance.

Just wanted to bump that thread with two things.

1. C2 closed itself yet again, while I was trying to import new frames into sprite.

2. It would even be nice to just revert to r265 in Steam, since Steam users can't go back in versions on themselves.

Thanks.

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.