Win8 Export VS Error

Post reply

❤Follow Topic(2)

0 favourites

3 posts

From the Asset Store

Gif

Game Template - Error 404 Game Found?!

$3 USD

Use this game pack to create your own game, modify the existing game or simply take a look and see how it was made.

xanderwood

- michael
- - Joined 24 Dec, 2012
  - 36 topics • 337 posts
- 1
- 11 Oct, 2013
- Quote
Link to .capx file (required!):

Not required: just use Scirra Win8 project template

Steps to reproduce:

1. Create Win8 project using built-in template

2. Export using the VS 2013 option and an open in VS 2013 Preview

3. Attempt to build the solution

Observed result:

This error is returned:
Unhandled exception at line 292, column 458 in ms-appx://fbe66f5d-7300-4fd7-8818-6a58e2371133/c2runtime.js 0x80070005 - JavaScript runtime error: Access is denied. If there is a handler for this exception, the program may be safely continued.

Expected result:

Run the game...

Browsers affected:

Chrome: yes/no

Firefox: yes/no

Internet Explorer: yes/no

Win8 VS Compiled App: YES

Operating system & service pack:

Win 8.1

VS 2013 Preview

Construct 2 version:

R147

Edit: I might be missing something here, but I have done everything I usually do when building VS app.

Ashley thanks in advance for checking this...
- michael
- - Joined 24 Dec, 2012
  - 36 topics • 337 posts
- 1
- 12 Oct, 2013
- Quote
Bit more info:

The line in question is where the "In Test Mode' banner is displayed.

If you export the game with Win8\Test mode turned off it compiles and runs as expected.

There are other issues also:

1) Mouse object doesn't work as expected.

2) Snap no longer works

However I have not had time to look more into those issues as yet....
Try Construct 3

Develop games in your browser. Powerful, performant & highly capable.
Try Now Construct 3 users don't see these ads
- Ashley Construct Team Founder
- Moderator
- - Joined 21 May, 2007
  - 667 topics • 30,052 posts
- 1
- 18 Oct, 2013
- Quote
Can't reproduce, works with the RTM build of VS2013 which will be supported next build. So closing as assuming fixed. Please post separate bug reports following all the guidelines if you have separate issues.