How do I FInd a bug in the game related to the Engine bug?

0 favourites
  • 4 posts
From the Asset Store
Use this game pack to create your own game, modify the existing game or simply take a look and see how it was made.
  • I caught some annoying bug that leads to the black screen

    It happens randomly, and I can't find what is the issue, the code seems okay, and the bug related to the render of COnstruct, something wrong happen in the render process

    Uncaught (in promise) TypeError: Cannot read properties of null (reading 'GetZElevation') at SortByInstZElevation (layer.js:2:218) at Array.sort (<anonymous>) at Layer._UpdateZIndices (layer.js:40:74) at Layer.Draw (layer.js:57:260) at Layout._DrawLayerList (layout.js:55:107) at Layout.DrawMain (layout.js:52:113) at C3Runtime._Render (runtime.js:103:144) at C3Runtime.Render (runtime.js:101:226) at C3Runtime.Tick (runtime.js:86:418) SortByInstZElevation layer.js:2 _UpdateZIndices layer.js:40 Draw layer.js:57 _DrawLayerList layout.js:55 DrawMain layout.js:52 _Render runtime.js:103

    I saw the same issue on github, which was closed because it can't be reproduced and I can't reproduce it as well. I can't share the project sadly, it is not only mine.

    So, are there any ideas on how to resolve this kind of issues?

  • And by the way, in this log, we see the error with ZElevation, but I doesn't use any 3D objects, all layers are in 2D and 3D is disabled.

    Really weird

    Possible reason - the object created with hierarchy

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • Without the steps to reproduce, there isn't anyone can do I suppose.

    Are you using hierarchies? Do you create/destroy them in runtime? Are there objects with Persist behavior in hierarchies? And do you use System Save/Load actions? From my experience, a combination of these things can sometimes cause similar errors..

  • Without the steps to reproduce, there isn't anyone can do I suppose.

    Are you using hierarchies? Do you create/destroy them in runtime? Are there objects with Persist behavior in hierarchies? And do you use System Save/Load actions? From my experience, a combination of these things can sometimes cause similar errors..

    yes, I understand, it is hard, I just want to understand how to resolve this kind of bug, the methodology, the fastest way

    disable actions one by one, or maybe something else

    And yes, I think it happens because of created objects with hierarchy enabled and then destroying it

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