Can not run win32 exports on Win 7 (64bit)

0 favourites
  • 7 posts
From the Asset Store
Full game Construct 2 and Construct 3 to post on Google Play
  • Link to .capx file (required!):

    dl.dropboxusercontent.com/u/108799982/TheOrphanage.capx

    Steps to reproduce:

    1. I export the .capx using Node-Webkit

    2. I go to run the .exe it creates

    Observed result:

    It crashes with the following wall of text:

    Game.exe has stopped working

    Problem signature:

    Problem Event Name:      APPCRASH

    Application Name:      game.exe

    Application Version:      0.0.0.0

    Application Timestamp: 517b467c

    Fault Module Name:      game.exe

    Fault Module Version:      0.0.0.0

    Fault Module Timestamp:517b467c

    Exception Code:      80000003

    Exception Offset:      001ab730

    OS Version:           6.1.7601.2.1.0.256.1

    Locale ID:           3081

    Additional Information 1:     0a9e

    Additional Information 2:     0a9e372d3b4ad19135b953a78882e789

    Additional Information 3:     0a9e

    Additional Information 4:     0a9e372d3b4ad19135b953a78882e789

    Expected result:

    It should run, like it does when I play it on Win 7 (32bit) machines

    Browsers affected:

    N/A

    Operating system & service pack:

    Windows 7 Ultimate (64bit)

    Service Pack 1

    Construct 2 version:

    R130

  • Seems to work fine for me on Windows 8 64-bit. Are the system's graphics card drivers up-to-date?

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • I'm using Win 7 64 bit, and the exported exe worked fine for me, although I never used minify, as I refuse to install such bug-ridden crapware as JRE in order to minify :/

    Note to Ashley: Please come up with a better way than having to install JRE :)

  • My drivers are the latest and greatest NVIDIA have to offer <img src="smileys/smiley1.gif" border="0" align="middle" />

  • Have you tried deleting your old export folder? I had the same thing with post-R126 updates and deleting it worked for me.

  • That did the trick ErekT. Thank you :D

  • Closing as issue worked around.

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