LukeW's Recent Forum Activity

  • Okay, it happened again, the exact same as last time. I added a variable to an instance that's sitting on a global layer. The editor then freezes for a second before jumping to that screen ^.

    Getting these crashes in project and c3p saves, with Edge and Chrome.

  • Just happened again. I'm pretty sure it was going to autosave and then just dumped me to this screen:

    I realized I'm using the app in Edge, so going to jump over to Chrome and see if that makes any difference.

  • Is the editor itself crashing for you, or just the preview? Since 308 I've had a lot of editor crashes, seemingly at random.

  • Hey Joe,

    One thing I've found with preview builds is they don't work a lot of time for me if they're in fullscreen mode. For whatever reason, I find that the previews run more consistently when windowed.

    Not sure if that's what you're dealing with, but thought I'd throw it out there.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • Hi,

    Since the latest stable build, I'm experiencing an unusual amount of crashes on my project. While a couple have given an error report and allowed a save before restart, the last two have, more concerningly, frozen the editor. Both times this occurred was just as the project entered autosave.

    As it's not really a reproducible issue that I can submit, I thought I'd check on here to see if anyone else is experiencing increase in crashes since the latest stable as well, or if it's just me.

    Cheers

  • Another option would be to have an entire event sheet dedicated to your debug events and include it in your main event sheet - then remove it before export. I like doing it this way as all debugging systems are located in one place.

    *Edit* Although re-reading your OP, I see that you're specifically concerned about forgetting to turn it off. If that's the case, stick to Wacky's suggestion.

  • Working today without autosave enabled, saving was a lot quicker for most of the day.

    I did notice the occasional slow save once in a while, though nothing like what I was experiencing before. We're talking a 30 second save every couple of hours.

  • Looks like Windows Defender is to blame! github.com/Scirra/Construct-3-bugs/issues/5825

  • NGX

    Whats up with this? Can someone fill me up with the Scirra objectives with the tool?

    I think they're referring to this: construct.net/en/blogs/construct-official-blog-1/announcing-new-product-beta-1589

  • Auto-save feature saves the project as a single c3p file. Maybe Construct needs to rebuild the file structure or something to save as a folder after that. You can test this by manually saving as c3p and then as a folder.

    Yep, looks like you're correct. I'm just trying this out now with the build I uploaded to the issues page and it's triggering a slow project save after the single c3p file save.

  • After a bit more testing and observation today, I'm almost certain that it's tied to autosave.

    As soon as my project autosaves, I can expect a long manual save straight after, no matter what (while using project folders). Meanwhile, disabling autosave results in no longer getting a long save time intermittently.

LukeW's avatar

LukeW

Member since 26 Mar, 2017

Twitter
LukeW has 9 followers

Trophy Case

  • 7-Year Club
  • Forum Contributor Made 100 posts in the forums
  • Coach One of your tutorials has over 1,000 readers
  • Regular Visitor Visited Construct.net 7 days in a row
  • RTFM Read the fabulous manual
  • Email Verified

Progress

12/44
How to earn trophies