Ashley's Forum Posts

    • Post link icon

    The model we're launching with is based on analysis of sales and customer data for the past couple of years. Please be aware that if you've not done any such analysis and you're still throwing out ideas, they may well actually be the kind of idea that likely ruins the company. It's also easy to like other people's ideas if they mean you pay less, but it's still not such a great idea if we end up firing people to try to stay afloat because the model significantly reduces our revenue. One of the risks of the "pay once" model that Construct 2 has always faced is that we could have tens of thousands of active users, and still go out of business, because the support for long-term existing users is entirely funded by new user sales, which there's a chance could end up tailing off. So if you are interested in the long-term viability of Construct and our ability to expand Construct to new areas to make it better and more powerful (of which hiring new staff and paying their salaries is a significant part), some kind of subscription or on-going payment is actually good way to do that.

    On the one hand we have users baying for major new features ranging across broad areas like animation, 3D, teamwork/collaboration, modularity, even scripting or new styles of drag-and-drop system; on the other we have people who want everything cheaper, lower-cost, less investment. You should also remember you can't have it all: if the product is cheaper or less sustainable, you can assume many of those ideas will be postponed far off in to the distant future, rather than something we could conceivably approach at some point, or even actively start planning.

    • Post link icon

    It's like being in a cell, you can still look what's beyond the bars, but you are still behind them.

    That's ridiculous. It's a product for sale, not incarceration.

  • Not right now I guess, I think I'll need to put better error checking in C3 to report where exactly it happened.

    • Post link icon

    Only but a few want to support a sub for C2 in a browser.

    Unless you have actual reasons why you don't want to use a browser, why does this point of view matter? The browser can do a great deal of what native apps can do now, e.g. offline support, use local projects, import C2 projects, hide browser UI by adding to desktop, etc. etc. Usually "I don't want to use a browser" comes down to incorrect assumptions like "I don't want to have to be online", when it already works today offline, and so on.

    [quote:2e7gh1j9]And this thing will always only run on chrome, just try open C3 in any other browser and read the notice you get.

    Perhaps you missed our progress on the Firefox port.

  • I think our existing suggestions cover most of this.

    • Post link icon

    I think some people are trying to say you're locked out of your project entirely. That's not the case. You mainly have edit and export access taken away.

    As I've said before, we're looking in to adding a special option for people who have had exported projects in the past, so they won't have to sign up for another full year just to export again or make a few quick changes. Assuming we have something like that in place, I don't think it's fair to say any work is "held hostage" either.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • I do comprehend, but what do you expect me to do about it? Do you want me to go and fix your WAMP install? It's the same thing with graphics drivers.

  • I've seen in a couple of bug reports that there's a slight incompatibility between C2 and C3 in validating expressions. C2 actually allows some invalid expressions; C3 correctly rejects them, but then this causes problems opening projects that happen to use these invalid expressions.

    I think one case is using a global number variable, and putting it in an expression that expects a string. So for example you might have done something like tokenat(NumberVariable, 0, ","). It's invalid to use a number variable for the string parameter, but due to an oversight C2 lets you get away with that. It's not something I'm keen to make C3 allow as well, since stricter error checking is better - that's a mistake that you probably want Construct to tell you about.

    So I'd review your project for all uses of 'tokenat' and make sure they're really valid.

    • Post link icon

    Nobody is "locked out" of their projects. When your subscription expires, it will be the same as opening a project in the free edition of C2. You can still open it and run it, you can see your events, open sprites and extract your artwork and animations, and even preview it to play it. The main thing you can't do is edit it or export it. You can see exactly how it works by opening Kiwi Story in the free edition of C3. It exceeds the free edition limits but you can still look around the project, access all the artwork and assets, and preview it. Your own projects would work similarly if your subscription was not renewed.

    I think people talking about being "locked out" or "holding projects hostage" are deliberately trying to make it sound worse than it is. It's the same as going back to the free edition of C2.

  • There is not enough information to help you. The best thing to do is to provide a minimal project file that demonstrates the problem.

  • > So does this issue still happen with r239 if you install it now, whereas it previously worked? If so it's likely the driver or OS and not C2 itself.

    >

    Ashley ..... You guys are really incredible..... You'd do anything to cover your bugs right? You will never admit that it's C2's fault? I have found a topic on Steam where someone has the same problem, and you gently make him understand that it is his fault, his graphic drivers problem and not at all yours.....

    This kind of feedback is totally unhelpful has no place in a bug report. I asked that question as part of my routine approach to fixing bugs. I asked a simple question to try to identify exactly what is happening with which C2 versions, and I still don't know what the answer is, so I still can't consider this bug report any further until such information is clear. As usual I also speculate on possible causes to help inform people of my thoughts and give them pointers in case they want to keep looking in to the issue further. I did not directly blame drivers, I only said likely, because until the issue is actually properly diagnosed, we don't know. At this point even saying "likely" is simply a guess, and I am frequently wrong, but bug reports lacking information often force me to guess.

    If my approach to diagnose a bug simply ends with ranting, then I don't see any reason why I should try to help you any further.

  • Safari on iOS does not support WebGL 2 yet, but Apple are working on it.

  • Are you using the latest version of C2? We regularly make compatibility fixes, and if you're using an old version you might be missing those fixes.

  • So does this issue still happen with r239 if you install it now, whereas it previously worked? If so it's likely the driver or OS and not C2 itself.

  • Our latest blog post details our thinking on this, including a run-down of some of the downsides of WebAssembly.

    Don't ignore those downsides and tell us to do it anyway, that's not useful feedback.