Development halting bug encountered in newest update. This needs to be fixed ASAP.

0 favourites
  • 3 posts
From the Asset Store
You can become a REAL game developer. Learn the basics and get resources that will let you get profits from your game!
  • Every minute or so in preview mode, the preview screen as well as the editor screen goes black for a few seconds, and then when it comes back, there are many objects missing on screen. This repeats every time the project is previewed.

    It then gives me this:

    Here is the copied text from the error message. Hopefully it can help the Construct devs fix it. As of right now I cannot continue development until this is remedied. Thank you.

    Error report information

    Type: unhandled rejection

    Reason: Error: Error compiling fragment shader: null Error: Error compiling fragment shader: null at lka (https://editor.construct.net/r368/main.js:458:104) at async bk.Sb.R6a.Pd (https://editor.construct.net/r368/main.js:1998:64) at async pk.Sb.Q6a.Gkb (https://editor.construct.net/r368/main.js:2208:492) at async Promise.all (index 0) at async pk.Sb.Q6a.vea (https://editor.construct.net/r368/main.js:2203:14) at async pk.Sb.Q6a.r8 (https://editor.construct.net/r368/main.js:2225:418) at async Fcb (https://editor.construct.net/r368/components/editors/layoutView/layoutView.js:49:335)

    Stack: Error: Error compiling fragment shader: null at lka (https://editor.construct.net/r368/main.js:458:104) at async bk.Sb.R6a.Pd (https://editor.construct.net/r368/main.js:1998:64) at async pk.Sb.Q6a.Gkb (https://editor.construct.net/r368/main.js:2208:492) at async Promise.all (index 0) at async pk.Sb.Q6a.vea (https://editor.construct.net/r368/main.js:2203:14) at async pk.Sb.Q6a.r8 (https://editor.construct.net/r368/main.js:2225:418) at async Fcb (https://editor.construct.net/r368/components/editors/layoutView/layoutView.js:49:335)

    Construct version: r368

    URL: editor.construct.net

    Date: Thu Nov 23 2023 23:05:30 GMT-0500 (Eastern Standard Time)

    Uptime: 170.5 s

    Platform information

    Product: Construct 3 r368 (stable)

    Browser: Chrome 119.0.6045.160

    Browser engine: Chromium

    Context: browser

    Operating system: Windows 10

    Device type: desktop

    Device pixel ratio: 1

    Logical CPU cores: 16

    Approx. device memory: 8 GB

    User agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/119.0.0.0 Safari/537.36

    Language setting: en-US

    WebGL information

    Version string: WebGL 2.0 (OpenGL ES 3.0 Chromium)

    Numeric version: 2

    Supports NPOT textures: yes

    Supports GPU profiling: no

    Supports highp precision: yes

    Vendor: (unavailable)

    Renderer: (unavailable)

    Major performance caveat: no

    Maximum texture size: 16384

    Point size range: 1 to 1024

    Extensions:

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • If you run in to a problem please file an issue following all the guidelines, as otherwise it's impossible to help.

    I'd point out some problems like this one may be an issue with your graphics drivers, system, browser extensions, or other third-party software on the system - it's not always Construct that is causing the problem.

  • If you run in to a problem please file an issue following all the guidelines, as otherwise it's impossible to help.

    I'd point out some problems like this one may be an issue with your graphics drivers, system, browser extensions, or other third-party software on the system - it's not always Construct that is causing the problem.

    Ok Thank you. I will do that. I will check every other possibility that could be causing it first. This hasn't happened with any other update, just the most recent one. Hopefully it's one of the things you mentioned

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