glerikud's Forum Posts

  • Honestly, I have been around the web development world a bit, and Construct is, by far, the most expansive, standards-compliant, bug-free, easy-to-use web development platform that I have found. This software trivially easily exceeds GameMaker in HTML5 game development, and has the potential to match Google Web Toolkit pound for pound in critical enterprise applications if developed in that direction.

    I, and my team, have nearly two years of time and effort invested into Construct, and we have never looked back. We tried a number of platforms before selecting Construct, including Google Web Toolkit, GameMaker, D3, raw HTML5, and none were as easy to learn or as quick to demonstrably perform our most intensive graphics requirements without overloading our test machines. Our test litmus program involved generating one hundred thousand objects and displaying all of them in screen in a fully zoom/pannable dynamic user interface at once. GameMaker was not able to do this without stalling and freezing our test machine.

    No, C2 is one of the most unbelievable pieces of software that I have found in the web development world, and we are very anxiously awaiting C3.

    It's always good to see these kind of satisfied posts.

    This is the price we pay for having a great and intuitive game engine.

    True. Adopting new technologies is never an easy road. We have a great, intuitive, fast and fun to work with engine, but on the other hand, we have to accept the problems HTML5 brings with itself now. I don't dare to guess where HTML5 will be in a few years. It's very promising even now, despite the wrapper problems and more and more devices include the support for it as a way to make standalone applications on their system. They may have stated that HTML5 is a ready and released tech, but there's definetly space for improvement on the integration part.

    I wouldn't judge anyone for dropping C2. I know sometimes frustration reaches the limit and you simply say "ahh f*** it!". Moving to Unity or something like that would probably give you better performance and feeling of stability, but surely development won't be that fun as with C2.

    No one should be judged for dropping any software that doesn't fit their needs. FMFM You might find what you are looking for in Unity, UE4, etc., but as I said before it will never be bug free. Every software has it's issues, we just happen to see on the issues comes with Construct 2 because we are using it.

    I can see the discouragment and dissapointment what was caused by these issues and it's unlikely that these will be fixed soon, since it's out of Scirra's hands. I don't see it as an excuse, since in the end, we still have to face those bugs be it whoever's fault. But I still won't leave Construct 2, because despite these problems it still has many advantages over other engines which makes it the best choice for me. I have some hope that these problems will be fixed in the future, and I also have big hopes for Construct 3, even if it will still use the same runtime.

    Sometimes people just have to take a break. FMFM If you do leave, please, after a few months come back here and tell us how the change turned out for you.

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads

  • A more customtizable textbox has been asked from Scirra as a future feature numerous times. I hope they make it for Construct 3.

  • I'm not trying to defend anybody, but I can completely understand both sides. No one writes code that doesn't rely on other people's code these days and you can't hold someone responsible for other people's mistakes in their code. The approach Scirra takes to rely on big companies' work is a good one IMO, because it ensures that the libaries they use will be supported for as long as possible. I guess with bigger companies come more users that can end up in delays (sometimes extreme delays) regarding some bugfixing.

    However I can see your frustration as well — A bug is a bug whoever's fault it is and if you don't have any control to fix it, you are basically stuck.

    ...We should be growing again soon as well.

    That's good news, congratulations

  • Did you try assigning the fullscreen requesting actions to an user input event? For ex. on "F" key pressed. As far as I know you have to rely on user inputs for requesting full screen (except in NW.js). This is a browser limitation.

  • I'd like to ask for opinions and experiences from teachers who taught Scratch and Construct 2 as well for students (in all ages). What did you experience? Which method did you find more effective for teaching algorithmic thinking? How did the students respond for that kind of programming classes?

    I'm continuing my research on the topic of how to make programming teaching easier and more effective using visual programming methods. So if you happen to have experience in teaching both Scratch and Construct 2, your feedback would be very valuable. Thank you.

  • 150 updates+ over 5 years of post release development for a one time payment from what amounts to a one man coding army while also maintaining relatively constant community presence and responsive feedback on these forums?

    Not to mention he gave away pretty much full functionality to I'd assume a majority of users who's projects never make it over 100 events.

    I'd say it was well worth it just provide a very low barrier to entry and exposing a large amount of people to programming and thinking through algorithmic logic, but I'm not the one who needs to feed himself with software sales.

    So yeah I believe in what Ashley is doing.

    +1

    There's nothing stopping you from experiencing/using multiple tools and sticking with what works best for you. In fact I highly recommend exposing yourself to all the tools available to you to be able to properly compare experiences rather than just through general impression based on a software's public forum.

    I also believe that a good developer knows more tools than just one. Go ahead an experiment with well known ones (for ex. I still use C2, but in the meantime I'm also learning to use UE4). But don't forget: There's no such thing as a perfect tool. Construct 2 has issues, yes, but all the other engines do. You just haven't discovered them yet. I'd advise you to leave Game Maker alone and go for either Unreal Engine 4 or Unity for a more professional experience.

    Thanks for the quick answers and also for the tips in the save game topic.

  • 1. Does size of the collision elements/bounding boxes matter? And if so then is it faster when the object is bigger or smaller?

    2. Does C2 calculate collisions faster if bounding box is rectangualr (4 points, 90 degrees) shape rather then some fancy (many points) shape?

    +1 for these questions.

    Did somebody do some testing with the new NW.js version (v.0.13.0 beta 6)? Is it working or it's still broken?

    Also, this is some sort of noob question, but if I want to make a game for Steam, the only thing I'd need this plugin are the achievements, right?

  • Well, you can always go for other ad services if you still want to make money out of ads. Or you can sell your game on Steam (taking the Greenlight way you mentioned). There's also the possibility to include IAPs (In App Purchases) into your game. Or you'll find someone who wants to buy HTML5 games, I mean like a sponsor, a reseller, a company.

  • Good to know about this. Thanks.

  • I think you have the right to repost all of you creations, so I don't think you should worry. Or are you worried about the Android logo?

  • Welcome to the Construct 2 Community

  • I set up a basic system for you, hope this will be useful:

    https://dl.dropboxusercontent.com/u/166 ... teste.capx

  • Here's the thing, let us be the judge, if the tool can do it, let us decide what's better for our games. It's an entirely different matter if the engine cannot do it, in this case, it looks like a browser conflict is preventing you from getting it done, as I said, fair enough.

    I can't agree more.