glerikud's Forum Posts

    Wow, already 5 pages of suggestions. I think the users like this new interface very much. My question is this: Since one user can only vote 10 times, does one get back the votes after a suggestion has been accepted/denied?

  • As I've seen many people uses OwnCloud or NextCloud. It would be nice if C3 supported those as well. But as things are currently standing the sub-folder and iCloud support is top priority in that regard imho.

  • I guess it's clear now that the users need more blog posts like this (technical information posts). This post brightened my day too and it's great to see many positive feedback on the forums again.

  • While I probably won't have time to join such a jam, I like the idea. It would be also a good marketing approach right after launch. Maybe Scirra is also interested in this, and could make this official.

  • Any idea why I have post notifications in this thread but when I check nothing exists? Did some posts get deleted or something? I see Lamar got banned but the posts weren't from him.

    It's probably a bug in the forum software. I also have this problem from time-to-time.

    I like the direction where C3 is going. While I think that a bit more technical blog posts were needed before, I feel confident in it after reading today's post.

    C2 made it possible for me to develop games and I've learned soo much from it. While I'm also trying out new engines it's not because I want to leave Construct, but rather to widen my perspective. I'm still in love with the event system and I'll never forget what world Scirra opened for me with their product. I'll definitely subscribe for Construct 3. I'm sure about that in 200%: 100% for it's a promising and great product and an other 100% for that I bought an early adopter license for C2 and I feel like it's time to support Scirra again.

  • They can't have an unlimited editor out in the wild. It could be copied endlessly.

    I guess that's right. We saw that happen with C2.

  • Customers would expect bug fixes, and retro fixes for breaking changes. This would be a headache to maintain. Secondly, support would become mired in difficulties with everyone running different versions.

    I understand that. However it's either you don't provide these frozen versions regardless of how much users want it to feel safe for their projects or you'll put up a big warning sign that says something like "This version is no longer supported officially. We'd strongly encourage you to update to the latest version for new features, bug fixes and official support."

    There will be always people who'll post topics with later versions, not understanding what that sign says. But since you constantly get questions for native exports and 3D support, I don't think that this would be such a big problem. Also, what about the offline versions? Say, an educational institute installs offline versions on their computers which don't have internet access and therefore can't be updated. When they ask for support, isn't this the same situation as someone using a frozen version?

    There has been numerous examples of companies posted in different topics who do this frozen version thing. I don't think that they constantly support 100s of versions, yet they still can provide the frozen versions for their loyal subscribers. Just an idea: Make the user subscribe for a year, than only provide the frozen version when they renew their subscription. This would eliminate the problem of using old versions (since the user would update), but still would give them something to hold on. In my eyes the frozen versions' purpose would be to ease the community and give them something that can open/edit/export the projects that they made with the previous versions. The frozen version is not something that would need to be supported later on. I think anyone who is asking for such knows that, since you can't expect even a large company to support outdated versions of their software. However, providing these (at least in my eyes) would align with the open minded philosophy of Scirra.

  • It's really hard to do frozen updates. The free edition is always kept up-to-date, as it's really part of our marketing and we want to make sure there's the latest and greatest version for people to use. So this approach means for some users, you sign in and then it has to downgrade you to an older version than you're already running. If that downgrade doesn't work or is blocked, you get the latest update anyway. Plus I think on the off-chance there's a Chrome bug that breaks even just very old versions, currently that doesn't matter, but with frozen updates it will cut some people off. I think that would work out very badly: either we have to effectively fork our support and maintain multiple different versions of the codebase for essential fixes, which is a big drag on development, or we just tell users sorry, we're not patching it, and then I'm sure they'll get upset anyway because something they once paid for no longer works.

    It's a great deal easier and simpler just to keep everyone up-to-date.

    In my eyes this problem is simple to solve:

    • Just provide a frozen version for the offline edition only.
    • Keep only the newest versions supported. Warn the users that if they are going to use the frozen version, they won't receive support till they re-subscribe and update again.

    This way you would solve the problems you mentioned in your post and also ease the souls of those who fear the lockout (myself included).

    (Again, I do think it's a pretty unique thing that you actually can talk directly to the founder, but I'm starting to see the appeal in disappearing behind a corporate team page...)

    I understand your point, but please stay. It's one of the reasons why I like Scirra so much. The team members are very active in the community and I think it poses as an example for other companies. I know reading through topics like this is quite discouraging, but I'm sure I'm not the only one who appreciate your work and your involvement in this community.

    Wow, a 22 pages long topic. While it was an interesting read, I have to admit that after 12 pages or so I had to just scroll though the pages, since it takes ages for me to read all posts through (hats of to those who do that). But one think caught my eye and I'd like to tag Ashley for I think it's a great suggestion:

    A page with Scirra tested benchmarks for each platform

    (PC/Mac/Linux with PC specs, Android/iOS with model, wrapper vs browser

    ) with a Construct 2/3 version of the exported test file would work wonders in giving people an idea of how relative their current devices are to the test devices. If the benchmark demos even had an option to "submit your results to Scirra!" on it that would help aggregate consumer side data for a wider range of devices than the ones you can afford

    (but I do recommend having an official list of test devices that you can have physically)

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • I just wanted to drop this here, since my Avast just alerted me for a potential infected domain regarding the Construct torrents. I often download the new releases as torrent files just to seed them for a while and it seems that the btzoo.eu tracker (according to qBittorrent) behind those files is infected.

  • Great suggestion. I'd love to hear Scirra's opinion on this.

  • They're doing awesome work indeed.

  • - Why can not I name a sprite before I create it? In C2 if that could be done, I do not know because now I have to create it and rename it later.

    +1

    - C2 splash screen?

    +1

    Please, if you flex a bit the quota policy, I can continue using C3 if I stop paying, up to the version that I paid, I have no problems with the subscription, but I find it abusive not being able to use something that I have already paid, At least until the version of the last payment.

    +1000