Ashley's Recent Forum Activity

  • For what it's worth, I'll point out we've been maintaining the HTML5 runtime for years, and cases where Chrome updates it are very rare, and most of those were deliberate changes by Google that they warned everyone about for months. Any browser maker's job is to stay compatible with all the billions of websites on the Internet, so they tend to be extremely cautious with any changes that are not 100% backwards compatible.

    And in any cases that slip through the net? Simple, we just fix it! We have done in the past - and can do in the future - same-day updates to fix any critical problems like that.

    The desktop builds are entirely independent of the Chrome update process, so those will be the same regardless of what happens to Chrome updates. But we'll still be issuing regular updates of those as well, so the option to stay up-to-date is there.

  • I just got sent a .capx this week, so I'll look in to it. To say we're busy right now would be an understatement though! It won't last forever and I'll get to it.

    I must emphasise yet again that the bug report guidelines are there to make it possible for us to fix the bug. If you ever think it's taking too long to fix a bug, read the guidelines and try to follow them even more closely. In this case it took me three months to get anybody to send me a .capx, which adds three months to the time it takes to fix it.

    • Post link icon

    its the first time im seeing this you sell a product for years now theres 3-4 major things community wants like crazy but you dont care that much

    From my point of view, multiplatform support was definitely one of those 3-4 major things the community was asking us for.

  • As per our usual bug report guidelines we much prefer if you can send a minimal project, and the bug report guidelines include a guide on how to create that if you have a full project. If that doesn't work out though you can send a .capx to - ideally at least with all third-party plugins removed.

    • Post link icon

    I also don't think that anyone was asking for this.

    Mac and Linux support have been top feature requests for years - so I absolutely do think people were asking for this capability. We did it via the browser, and as we just announced, we will also be doing desktop builds - although they are almost identical to the browser version! Using a folder-based project (e.g. with Git/SVN) is pretty much the only feature you have to use them for - you can do everything else with the browser-based version.

    I know it's not really relevant if you use a limited number of Windows-only machines, but we did aim this at what people have been asking us almost daily for years. And as I say, there's still a ton to come.

    • Post link icon

    you should have given us the bad news up front like you did, AND give some features that people can get excited about. Even one major feature.

    We did! It runs in the browser. That's a huge feature. Maybe some people are sceptical, but it works beautifully. You can't get the feel of it from screenshots, you'll just have to wait for the public beta.

  • I'm not going to keep making the same points about native engines, I wrote a whole blog about it already.

    You should probably come up with a different name to talk about exporters - I equate "native exporters" with "native engines". I think you mean built-in exporters or something like that?

    • Post link icon

    I honestly think if we did what many are suggesting - and post all the features first and hype it up even more, then make the same announcement - it would have gone down worse. Everyone would have accused us of being deceptive, pulling some kind of bait-and-switch scam. We knew this would be a shock to many people, the only question was when to say it. So we chose to say it first, so you know from the start. I'm not surprised, I get the frustration, but I think this is the most transparent and up-front way of doing it.

    I'm not sure how to even reply to everyone - for example some people are saying we should have been upfront, and I genuinely think we were, in a way many other companies wouldn't have been. Lots of people are saying we should have announced features - and we did, but they were largely ignored (which we kind of expected). Multiplatform is huge. Chrome OS is huge. I get it, not a big deal if you're already happy with Windows, but that is still aimed squarely at the persistently top feature requests for years - Mac and Linux support. And there's a ton more. We have weeks and weeks of announcements lined up still.

  • We've been clear on this for a long time - we're not doing native exporters. I wrote about this in detail here: https://www.scirra.com/blog/ashley/28/the-case-against-native-engines

    In many cases, doing a native engine won't actually get people what they're asking for - e.g. it won't improve GPU-bottlenecked games. We've also been clear that 3D amounts to a different product so we're sticking to 2D. There's nothing new about any of this.

  • Modern browsers have multiprocess architectures that ensure tabs are isolated at the operating-system level. So other tabs shouldn't affect the performance or stability of Construct 3. It even means crashes in other tabs are isolated and won't take down C3 as well.

    If you open 100+ tabs, you're giving your computer a huge amount of work to do. It's like opening 100 different apps on your desktop. You have a finite amount of computing resources available, and it's amazing it can even handle as much as some people throw at it.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • One-off payments are not really a viable model for web-based services. In fact it's only a viable business model for C2 because we get a steady enough stream of new users buying it that we stay in business. With that model, if we stopped getting new users, we'd go out of business, even if we had tens of thousands of active users.

    For the years I've been working on Construct 2, users have routinely asked for simultaneously more features and lower prices. We have to draw a line somewhere.

  • chaimg - this thread is about 5 years old and all the technology has changed since then. You should start a new thread and include full details about what you're doing.

Ashley's avatar

Ashley

Early Adopter

Member since 21 May, 2007

Twitter
Ashley has 1,776,358 followers

Connect with Ashley

Trophy Case

  • Jupiter Mission Supports Gordon's mission to Jupiter
  • Forum Contributor Made 100 posts in the forums
  • Forum Patron Made 500 posts in the forums
  • Forum Hero Made 1,000 posts in the forums
  • Forum Wizard Made 5,000 posts in the forums
  • Forum Unicorn Made 10,000 posts in the forums
  • Forum Mega Brain Made 20,000 posts in the forums
  • x126
    Coach One of your tutorials has over 1,000 readers
  • x74
    Educator One of your tutorials has over 10,000 readers
  • x5
    Teacher One of your tutorials has over 100,000 readers
  • Sensei One of your tutorials has over 1,000,000 readers
  • Regular Visitor Visited Construct.net 7 days in a row
  • Steady Visitor Visited Construct.net 30 days in a row
  • RTFM Read the fabulous manual
  • x42
    Great Comment One of your comments gets 3 upvotes
  • Email Verified

Progress

32/44
How to earn trophies

Blogs