Ashley's Forum Posts

  • Closing, please report C3 bugs here, and follow all the guidelines or your report will be closed again.

  • Yeah, we want to do that for the Scirra Arcade.

    • Post link icon

    it would be nice if a person is allotted time instead of limited amount of edits.

    That's impossible to police. With options like changing device, renewing IPs, signing up new accounts, clearing browser storage, and changing the system time, people will easily figure out ways to use it indefinitely.

  • This sounds more like a general CSS question you could post to a site like StackOverflow rather than something specific to C2.

  • Our latest blog explains our near future plans in detail, as well as new features it should cover.

  • You only need one touch to unmute sound. Once sound is unmuted you can play sound at any time. It's easy to do with a title screen or "Play" button or similar.

  • The point is if you want major new features to be added, the business needs a stable income to be able to develop them.

    I threw in a few major feature requests to illustrate the point. The fact I mentioned them is not necessarily a statement of our roadmap.

  • We can do this on some platforms, like the Scirra Arcade, or mobile (to the extent that you get an APK back for example). But for uploading to the web overall, it's hard to get a one-size-fits-all feature. Some people use FTP, others remote desktop, some by SSH, some use a special web interface provided by their host, etc. I don't think it's clear how we could feasibly cover all the possible cases.

    • Post link icon

    I think it's pretty obvious if you ask a question which amounts to "do you want to pay more or less?" people are going to click the "less" option. Or if you ask "what other payment models should Scirra use?" the answer will be "the one I hardly have to pay anything at all". The business has to also at least survive, and ideally be able to keep improving the product.

    • Post link icon

    There's only so much of posts saying things like "go use a different product" or "they're dumb lol" that I'm willing to take on the forum, and I also feel this thread has run its course. It's already going in circles with the same points being made. With Construct 3 we made some bold changes and yes, those changes may not be for everybody, but we are going to stick with the plan for the time being. That's not to say we'll stick with it forever, there's always scope to make changes in future, but we want to at least see how things work out with our current plans.

    We are thinking about a way to allow previously subscribed users to more easily use Construct 3, so they don't have to pay a whole year subscription for some light maintenance. We don't want to make any firm announcements right now so we can keep our options open, but I am keen to provide something on this front. I must also emphasise that even with an expired subscription, you can still access your project and all its artwork, sounds, music and so on, so you can extract that and use it elsewhere if you want to.

    I'd also add that as a subscription, I think Construct 3 is still great value. You can use it for years and years accessing all features and all exporters before it gets close to the price of the all-exporters price for other tools. It's also cheaper than the subscription for PhoneGap Build alone. So not only are we going to provide a build service similar to PhoneGap Build, but it's also cheaper, and comes with an entire game development IDE as well. The pricing isn't just for one feature, it covers everything, but I think that perspective does show - it's still not a particularly expensive product.

    Remember that if you're keen to see major new features like 3D, timelines, modularity or collaboration, we're very much limited by our resources, and it's difficult to make the jump to hiring new developers if we have a less stable income.

    Finally I'm sure some people are going to point at this thread and accuse us for shutting out discussion of the topic. I'd like to point out that this thread has been open since February 1 - over three months - and has nearly two hundred replies, including several from myself. After this time of allowing all this discussion I believe there is little else to be gained from allowing this thread to continue. I have read nearly every post in this thread, and as many as I can from the Construct 3 forum, and often posts from other forums and websites. We have heard everyone's points, in some cases I've directly responded to them, and now it has simply come down to re-hashing the same things. Even if it doesn't make sense to anyone else, we have a clear plan and a vision for where we want to go. I'm confident in time our decisions will become clearer, much as the choice of HTML5 over Flash originally mystified many but ended up being the right way to go. I'd like to thank everyone for their energy and feedback, and please be assured we'll still be listening and posting here on the forum, as we continue to develop Construct 3 in future.

  • It's almost impossible to do anything about bugs that I can't reproduce. Step 1 is to reproduce the problem, so I'm still stuck on step 1.

    I'm not sure what the OpenGL traces prove if anything; C2 ought to be making the same rendering calls across all systems. If they're different, that just adds to the mystery, because they should be the same.

  • Those conditions are intentionally hidden in some circumstances. Since you ignored the bug report guidelines I can't check what you've done, so I will assume it is working correctly. Closing.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • All early software releases have some stability issues, this is just how software development goes. The purpose of the public beta is to sort out these issues.

    However we can't fix issues from posts like these. We need at least the information in the crash report dialog, and ideally the steps to reproduce, as per the bug report guidelines. Otherwise there is simply nothing we can do about it.

  • You could try again later - Chrome on Windows is supposed to have a software-rendered WebGL implementation, which is slow but at least works. I think it's downloaded in the background the first time you need to use WebGL so it might not be immediately available.

    As a last ditch effort you can enable "override software rendering list" in chrome://flags, but since your graphics driver is known to be unstable, it could cause crashes or glitches.

    • Post link icon

    Make a plan to release major new version release on a yearly basis. Make it clear that no further updates and support to old versions will be available once the next version is released. Only a downloadable last stable will be available for old C3 once C4 is released.

    Business-wise it is not feasible to drop all support, especially for a relatively new software release. Customers hate having support for their product dropped. For exactly this reason, we are continuing to maintain Construct 2 for the foreseeable future. We could never say we'd dropped support for it - there would be a huge backlash.

    I am sure the same thing would happen if we dropped support for the product every year and asked people to pay again. It would be a regular, annual backlash. I dread to think of that. I am certain we would be forced to maintain old versions at least a couple of years. Maintaining multiple versions would cause a significant engineering overhead and considerably slow down our ability to progress with new features.