R155 Error

Post reply

❤Follow Topic(4)

0 favourites

7 posts

From the Asset Store

7 Errors

$15 USD

7 Errors is a game where you have to find the 7 mistakes before time runs out. Can you find all 7? Have fun looking.

BassoGames

- rhg1968
- - Joined 6 Jun, 2014
  - 35 topics • 191 posts
- 1
- 20 Jun, 2019
- Quote
I have to do a little more research to see if I can create a small example of this issue I am seeing and post in the bug tracker.

I have coded a large portion of my game in java script and it has been working well in R154 and stil does. As soon as I switch to r155 I get the following error in the console after it navigates from my boot layout to the title layout.

layer.js:1 Uncaught (in promise) TypeError: Cannot read property 'Apply' of null
at C3.Layer._DrawInstance (layer.js:1)
at C3.Layer._DrawInstances (layer.js:1)
at C3.Layer.Draw (layer.js:1)
at C3.Layout.Draw (layout.js:1)
at C3.Runtime.Render (runtime.js:1)
at C3.Runtime.Tick (runtime.js:1)
_DrawInstance layer.js:1
_DrawInstances layer.js:1
Draw layer.js:1
Draw layout.js:1
Render runtime.js:1
Tick runtime.js:1
async function (async)
Tick runtime.js:1
_tickCallback runtime.js:1
requestAnimationFrame (async)
Tick runtime.js:1
async function (async)
Tick runtime.js:1
Start runtime.js:1
async function (async)
Start runtime.js:1
Init runtime.js:1
async function (async)
Init runtime.js:1
self.C3_InitRuntime runtime.js:1
_InitDOM domSide.js:1
Tagged:

javascript
script
Try Construct 3

Develop games in your browser. Powerful, performant & highly capable.
Try Now Construct 3 users don't see these ads
- rhg1968
- - Joined 6 Jun, 2014
  - 35 topics • 191 posts
- 1
- 20 Jun, 2019
- Quote
I went back to an old version of my game without any JavaScript scripting and I get the same error.
- rhg1968
- - Joined 6 Jun, 2014
  - 35 topics • 191 posts
- 1
- 20 Jun, 2019
- Quote
I posted this comment on the release comments so not sure if I should leave it here. Let me know if I should delete it.
- Nepeo
- - Joined 8 Mar, 2016
  - 5 topics • 730 posts
- 1
- 21 Jun, 2019
- Quote
A minimal replication on the issue tracker would be appreciated, as it hasn't been reported yet.

Generally it's not that useful posting crash reports on the release notes. If the problem is common then posting a brief description of it with a link to an issue on the bug tracker can be useful to point other users our reponses. That way they can find the status of the issue and find out when it's resolved.
- rhg1968
- - Joined 6 Jun, 2014
  - 35 topics • 191 posts
- 1
- 21 Jun, 2019
- Quote
ok, thanks.

I will try to create a small project to see if I can duplicate it and file a bug. I know someone else has run into this issue also. I'll see what I can come up with.
- carlajiji
- - Joined 20 Jul, 2018
  - 0 topics • 1 posts
- 1
- 5 Jul, 2019
- Quote
That will be great, thanks.
- rhg1968
- - Joined 6 Jun, 2014
  - 35 topics • 191 posts
- 2
- 5 Jul, 2019
- Quote
Sorry I never added to this thread.

The issue for me was taken care with R156 as shown in the release notes for that version.

Possible runtime crash creating instances not placed anywhere in project (regression in r155).

In R155 I fixed the issue by putting instances of all my objects on the layout and then destroying them on the start of the layout.

Hope that helps.