0 Favourites

Construct 3 any news?

  • I can't launch it, even though i have the latest Chrome version and I enabled WebGL

  • No issues so far ... Probably Scirra should put an pop-up info/warning to disable adblocks or other plugins that can interfere with Construct 3.

  • Tom i hope the latest chrome limitation is only for beta? I am one version behind on one machine, and cannot run Construct. You should be able to run it, accepting risk in having an older version.

    Some of my managed computers, don't get the latest version for months, even then sometimes they are updated to an older version and not current.

    I only used it for maybe 5 minutes, the limitations and functionality was too frustrating. I was not a fan of it. There should be no limitations for beta... once that is lifted I can provide some more constructive feedback. But as it stands, I got so frustrated with it I just closed it out.

    I have zero plans to use C3 as my main IDE, as I absolutely hate what it represents (the rental model), among other reasons. But, I will gladly provide feedback.

  • Construct 3

    Buy Construct 3

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

    Buy Now Construct 3 users don't see these ads
  • Tom i hope the latest chrome limitation is only for beta? I am one version behind on one machine, and cannot run Construct.

    Are you one version behind on purpose? You can easily update it unless you're worried about breaking something.

  • > Tom i hope the latest chrome limitation is only for beta? I am one version behind on one machine, and cannot run Construct.

    >

    Are you one version behind on purpose? You can easily update it unless you're worried about breaking something.

    I have several computers, some are managed, meaning they cannot be updated to the main version until they pass strict testing controls. Often, this means they are 10, even 20 updates behind. 99% of the time, they are not on the latest version, unless there was a huge critical security flaw that needs patching.

    If C3 cannot be used on older chrome versions, with no bypass option, this is a huge oversight. I find it hard to believe they would eliminate the corporate world from using C3...I will wait for feedback. I suspect this is just a beta thing, because there is a warning message that implies you can still use it. The ability to however, is not turned on it seems.

  • There is a bug in Chrome detection, try clicking "Launch Anyway" if you are up to date.

  • There is a bug in Chrome detection, try clicking "Launch Anyway" if you are up to date.

    Tom Hi Tom, my issue is with not being up to date. When I click launch anyway, you are blocked on the next screen (the one that the IDE runs in).

  • >

    > > Tom i hope the latest chrome limitation is only for beta? I am one version behind on one machine, and cannot run Construct.

    > >

    >

    > Are you one version behind on purpose? You can easily update it unless you're worried about breaking something.

    >

    I have several computers, some are managed, meaning they cannot be updated to the main version until they pass strict testing controls. Often, this means they are 10, even 20 updates behind. 99% of the time, they are not on the latest version, unless there was a huge critical security flaw that needs patching.

    If C3 cannot be used on older chrome versions, with no bypass option, this is a huge oversight. I find it hard to believe they would eliminate the corporate world from using C3...I will wait for feedback. I suspect this is just a beta thing, because there is a warning message that implies you can still use it. The ability to however, is not turned on it seems.

    Construct 3 is built for now and the future, using bleeding edge features.

    I would also argue that an organisation not allowing updates to browser is a pretty backwards security policy. Unfortunately you'll have to wait for them to allow updates.

  • Construct 3 is built for now and the future, using bleeding edge features.

    I would also argue that an organisation not allowing updates to browser is a pretty backwards security policy. Unfortunately you'll have to wait for them to allow updates.

    Tom,

    That does not explain why you do not allow someone to run it, without being up-to date. Most of the time, all the features you are using do not rely on the latest, or even last 20 Chrome updates. Some minor tweaks, that would not prevent the usage of C3. Sometimes, there would be, and that is something the user should be able to choose to accept as a risk.

    Many large corporations, follow this standard. Are you really planning on only allowing the very latest version of chrome to run C3? Or, is this a Beta limitation?

  • Unfortunately there are some features we're using that simply would take far far too long to refactor. For example, CSS grids are a new browser feature we use for the entire layout of the editor. Grids are designed specifically for this usage in mind, and if we wanted to make it an optional feature we'd end up with div soup.

    I understand your point entirely, but there was a tradeoff here, supporting organisations/users with older browsers, or reduced development time and easier maintenance. Historically we've always gone for #2.

  • oh!my mac mini 2011,run chrome latest(版本 57.0.2987.110 (64-bit)),and open flag:webGL

    but when I try to lunch C3 anyway...it show ...should I buy a new mac?! help!

    Oops! WebGL is not supported.

    WebGL provides high-performance graphics for web apps. Construct 3 needs WebGL support to run, but this browser does not appear to support WebGL.

    Try installing any available system updates, and check for an update for your graphics driver. Alternatively if you have access to a newer device try using that.

  • Unfortunately there are some features we're using that simply would take far far too long to refactor. For example, CSS grids are a new browser feature we use for the entire layout of the editor. Grids are designed specifically for this usage in mind, and if we wanted to make it an optional feature we'd end up with div soup.

    I understand your point entirely, but there was a tradeoff here, supporting organisations/users with older browsers, or reduced development time and easier maintenance. Historically we've always gone for #2.

    Tom, I understand what you are going for, but I am not asking for you to support older versions, but simply let the user decide to try it out.

    Give it this scenario:

    I am a corp that uses managed versions.

    I am 1 week out from my delivery window.

    A new version of chrome is updated, C3 "forces" you to run on it.

    I miss my deadline.

    This is one of the inherent risk of using a browser based IDE, they update and can update often. I use to pitch C2 to some companies, but C3 I simply cannot pitch with the forcing of using the latest Chrome version. Updating your OS to the latest and greatest, versus your browser are two different worlds. Something running in the browser should not be locked down like that.

    Maybe my understanding is off, but you have not corrected my question. Whether or not the absolutely latest version is required, or if this is just a beta thing. By your responses, it sounds like to me, that C3 will always require the latest version of chrome.

    If that is the case, C3 seems kind of...short-sighted. Let me explain what I mean. You are basically saying, C3 is only for the little guys. You have no intention of targeting big corporations, with lots of money to proper development. It gives C3 a bit of a toy-ish feel, as in it is not meant for any serious project. To ignore the managed version control of Chrome, really surprises me.

    That is my 2 cents on it. As mentioned, maybe I am misunderstanding you, but this is how I feel about it and my feedback on it.

  • Ah got you now. We don't see why Construct 3 wouldn't work in all future versions of Chrome - onwards from 57. Also, offline desktop builds will solve the issue you're talking about I believe.

  • Ah got you now. We don't see why Construct 3 wouldn't work in all future versions of Chrome - onwards from 57. Also, offline desktop builds will solve the issue you're talking about I believe.

    That is great news. Thank you for the clarification

  • Sorry for misunderstanding, obviously busy now trying to read everything!

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