Game not working after r190 update :-(

Problem Description

Game not working after update to C2 r190

Attach a Capx

https://dl.dropboxusercontent.com/u/167 ... attle.capx

Description of Capx

Game inspired by Mario battle

4 player game

Steps to Reproduce Bug

• Updated to C2 190
• test the game and it doesnt work

Observed Result

Stack trace:

Error

at Error (native)

at assert2 (http://localhost:5000/preview_prelude.js:16:10)

at Runtime.loadProject (http://localhost:5000/preview.js:1090:41)

at XMLHttpRequest.xhr.onload (http://localhost:5000/preview.js:376:10)

common_prelude.js:39 Project model unavailable

preview.js:1094 Uncaught TypeError: Cannot read property 'project' of null

Affected Browsers

• Chrome: YES
• FireFox: YES

Operating System and Service Pack

windos 7

Construct 2 Version ID

Construct 2 r190

Your project uses the third-party MagiCam plugin. As per the guidelines, can you submit a .capx that reproduces the problem and does not use any third-party addons at all?

Thanks Ashley for the quick reply <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":-)" title="Smile">

I removed the magicam plugin and still haves the same problem <img src="{SMILIES_PATH}/icon_e_sad.gif" alt=":-(" title="Sad">

here is one without 3rd party plugins

https://dl.dropboxusercontent.com/u/167 ... gicam.capx

and here is a link to the last version i i exported before i updated it to r190

so you can see how it works

https://dl.dropboxusercontent.com/u/167 ... index.html

press 1 and 2 to select two players and space to start or try it with xbox controllers <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":-)" title="Smile">

keyboard player one

wsad

i to run fast

o to jump

keboard player 2

arrows

2 to run fast

3 to jump

Escualo - the real problem is the project is corrupt - somehow an invalid character has worked its way in. There is something in the project called "player_1_select" which actually contains an unprintable ASCII character like this:

player_1[INVALID CHAR]_select

The invalid character is an unprintable "unit separator" (US) ASCII value 31. I've no idea how it could have gotten in to the project.

What is there in the project called player_1_select and if you rename it does it fix it?

I get the same error when updating to r190 and installing NW for C2, just by running the project that ran perfectly on r184. No plugins used, no changes made to the project. When I switch back to r184, everything is back to normal again.

1) Start preview with NW. NW loads.

2) Javascript alert:

[attachment=2:2y9fir10][/attachment:2y9fir10]

3) Javascript alert:

[attachment=1:2y9fir10][/attachment:2y9fir10]

3) NW fails:

[attachment=0:2y9fir10][/attachment:2y9fir10]

Same thing happens with Chrome, Firefox and IE, with the additional info (from FF):

[quote:2y9fir10]Assertion failure: Project model unavailable

Stack trace:

assert2@http://localhost:50000/preview_prelude.js:16:10

Runtime.prototype.loadProject@http://localhost:50000/preview.js:1090:3

Runtime.prototype.requestProjectData/xhr.onload@http://localhost:50000/preview.js:376:5

Subsequent failures will now be logged to the console.

makebelieve - the problem is not in C2, it's in the project. The latest C2 update made a change which exposes the problem with your project. Did you try renaming "player_1_select"? What is there in the project that is called that? I found an object but renaming it did not fix it, perhaps there's some other variable or something else with that name?

Ashley i changed the name of the object "player_1_select" and it still doesnt work.

the same error keeps coming up

Escualo - is there anything else in the project using the same name?

Ashley yeah i changed every object with the or similar name and it dind´t work.

I have installed r184 again and i works fine.

Escualo We haven't been able to preview or export since 185 or 186 I believe. Similar issue. We just stayed on 184 to do our game updates.

damainman Escualo - are either of you able to strip down a .capx to the minimum possible which still reproduces the problem? This would make it a lot easier to investigate.

Actually never mind, I found a fix for the next build. So should be working from r192+.

Ashley Thanks! It did indeed fix the issue. 192 is letting us preview in Firefox, and export to node webkit. Even seems faster and less jerkiness too... Will do more testing Good job! And thanks!

Ashley sorry the delayed reply. I have been very busy at work.

everything works fine and thank you very much for the help

Though an old thread, I came upon this recently and the the issue was that one of my sprites was corrupted (0 bytes).