Windows 8 Share CanvasSnapshot bug

0 favourites
  • 6 posts
From the Asset Store
No Ad-Sharing, Fully Open Source, No Remote Control, Well maintained
  • Link to .capx file (required!):

    upload.ee/files/3373399/thing.capx.html

    Steps to reproduce:

    1. export to visual studio

    2. run

    3. click share

    Observed result:

    System throws out of the game to the metro main screen

    Sometimes gives this error:

    SCRIPT5042: Unhandled exception at line 302, column 85 in ms-appx://4ab4861a-3e78-4b4c-9d44-6d9e4e68a950/c2runtime.js

    0x800a13b2 - JavaScript runtime error: Variable undefined in strict mode

    File: c2runtime.js, Line: 302, Column: 85

    I also have higher version of visual studio installed than construct2 uses, could this affect my project

    Expected result:

    Share Canvansnapshot

    Operating system & service pack:

    win 8 64 bit

    Construct 2 version:

        r132

  • Can't reproduce, works just fine for me. Have you tried r133 and have you made sure you're using the latest version of Visual Studio?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Yes, I am using the latest version of visual studio, it says, that I am having newer version of Visual Studio installed than the running project and that it is working against the debugger. I get error every time I start debugging that WWAHost.exe could not start. I think this is the root of the problem.

  • I got this to work, I downloaded r134 and used no Minify script. Very wierd thing indeed. You can close the topic.

  • I believe all versions require you to not minify the script on export for windows

  • BluePhaze - no, minifying the script should always work and never cause any new bugs by itself, especially with all the built-in features (some third party plugins have problems with the minifier though).

    Ah, I managed to reproduce the issue just now, not sure what I did wrong last time. The issue should be corrected in the next build.

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