JS error in debug mode - how to identify it?

  • While trying to run debug layout of my game, I get this:

    But when I run in preview or exported game there's no errors.

    How can I find this error as there's no reference to my c2 code but to JS?

  • Do you mean you see this when using the C2 editor debug run mode?

    Do you see any errors in the browser console when previewing normally?

    What browsers are you testing on?

    Do you use any non-standard plugins?

    What version of C2 are you using?

    What version of NW.js are you using?

  • Occurred too.

  • Do you mean you see this when using the C2 editor debug run mode?

    Yes. This error started to pop out when I updated to r217 (but in r219 it still exist). Before the update (latest working version was r216) debug mode was working fine.

    Do you see any errors in the browser console when previewing normally?

    I normally test on NW with no errors.

    But specially for this issue I launched project on Chrome and there were indeed errors that in NW doesn't occur. Those errors were connected to MouseLock plugin that I'm using. But when I removed this plugin from the project there was only those errors in Chrome console:

    but the NW debug mode still gives me the same error.

    What browsers are you testing on?

    On NW.js so I suppose it's on Chrome engine.

    Do you use any non-standard plugins?

    Rex MoveTo

    MouseLock v0.5 ()

    What version of C2 are you using?

    It's OK for r216

    Error occurs in r217

    What version of NW.js are you using?

    10.5

  • R217 to r219 were supporting new and newer versions of NW.JS.

    If you don't update NW.JS, it's kind of normal you get those JS errors I believe...

    Go to https://www.scirra.com/nwjs and get NW.JS 0.13 alpha 7 with r219 and see if you are still getting those errors.

    And please do read changelogs on each new version, you would have seen you were required to update your NW.JS version as you were updating C2's release.

  • I've just did this. Error still occurs for NW v0.13.0 alpha 7 (Chromium 47) and v0.12.0 (Chromium 41).

    ---edit---

    But now the error looks like this:

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • I have the same problem - Running C2r219 with NW.js v0.13.0 beta 2 (Chromium 47). I can export, or use NW.js preview fine, but when I try the debug preview I get an identical error as shown in the picture above.

    I'm guessing this isn't a common issue, maybe platform specific? Running C2 on Windows 10 64bit. I'll try putting it on a different computer and see if it works, and if not I guess I'll start downgrading C2 and NW.js until I find a combination that works.

  • oosyrag

    I have the same problem - Running C2r219 with NW.js v0.13.0 beta 2 (Chromium 47). I can export, or use NW.js preview fine, but when I try the debug preview I get an identical error as shown in the picture above.

    I'm guessing this isn't a common issue, maybe platform specific? Running C2 on Windows 10 64bit. I'll try putting it on a different computer and see if it works, and if not I guess I'll start downgrading C2 and NW.js until I find a combination that works.

    This has been fixed in the latest beta r220.

  • Ashley, thanks for fixing this so fast

  • I don't think there was a report for this in the Bugs forum, unless I missed it. Please report all such problems to the Bugs forum in future to make sure I see them!

  • Technically, your object is not available

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