> Vasanthi Keep in mind when Ashley says: "Construct 2 does support HD games.", what he means is that you can run true HD games but with severe performance issues or even memory related crashes (mostly on low to medium-end devices).
I just want to emphasise that if you see these issues, it's because you're exceeding the limits of the hardware. Often people try to make a game that uses 10 GB of memory, find it crashes, then think "Construct sucks". Or they make a game with dozens of layers and tons of overdraw and run it on a weak integrated GPU, far exceeding its memory bandwidth resulting in laggy gameplay, and then think "Construct sucks". The real problem is you far exceeded the limits of the hardware in a way a professional designer never would. I don't think you need to fuel these misconceptions.
Well professional game designers probably won't downscale or essentially "cripple" their games so that they work on every desktop PC, since as I've said later on in another post: "Only difference being that most game engines offer more advanced tools in order to work with high-res assets".
What you're basing your whole argument on is the case for beginners and they usually don't know much about memory management at all.
I think you just want the "unload sprite" action? There's no need to proclaim the downfall of an engine over that, the layout-by-layout memory management works fine for many games.
I've said multiple times in many posts in here that I want advanced memory management.
I as a self proclaimed mediocre game designer, don't want to rely on fully automatic loading or management systems and want to have as much control over my game as possible. Again I'm not saying that you're wrong when you state that systems like the layout-by-layout loader work fine for the majority of games but my point is that having more options won't hurt and could even make Construct 3 more attractive for professional game designers.
Any further questions regarding this can be asked here:
I won't say it's the downfall of Construct 3 since that's pretty much assumption based and I have no statistics to prove my point anyway but from what I can see so far is that a number of people don't seem to find enough reasons (cutting edge features if you will), that gets them on the edge of their seat and gives them a reason to switch. If you actually ask some of the C2 Dev's, you will probably find out that they only did or consider doing the switch to C3 because of bugs or limitations inside C2.