"I can't believe Scirra chose a HTML5 runtime instead of Flash. It just doesn't make any sense. Everyone is doing everything in Flash so obviously that was what they should have done. Also they have started charging money when Construct Classic was free, especially when C2 is so early on at this stage of development compared to CC. Obviously this will drive away users. I think I'll choose another tool. HTML5 also only runs in Chrome and Firefox right now so it seems needlessly limited, and we don't know if other browsers will ever support it. It seems like it was a desparate afterthought. It's sad to see Scirra making such crazy choices. It seems like they'll just fade in to obscurity to be overtaken by other tools. Too bad they're doomed."

- Everyone in 2011

And obviously, mocking your user base isn't going to drive them away either.

As a quick aside, by far the most prevalent commercial use of Animate is in the creation of banner ads and rich web media content, of which HTML5 and canvas are the dominant background tech thanks in no small part to the fact that Animate is the amalgamation of several Adobe programs, namely Flash, Edge and Edge Animate.

With this in mind, it relies on the much more modern holy trinity of HTML5, CSS3 and JavaScript.

I think it would be a misrepresentation of Animate to lean too heavily on it's ActionScript and Flash aspects; whilst these do exit, in my opinion they're grandfathered in to capture the userbase left behind when Adobe discontinued Flash - and even these features are heavily dependent on AIR to survive in today's world.

God I miss Fireworks. I miss Fireworks so much.

I agree with you. Animate CC is not Flash anymore. My point is that Flash is not completely dead yet. Although, I think it's near there now. My other point was that without Apple, Flash would still be pretty strong. I remember numerous companies coming out against Apple's decision to drop Flash and it was even a selling point for many competitors, that their devices can still view Flash. Eventually though, Apple users didn't miss Flash and other companies finally came a round.

I think I'm really just trying to put all this in perspective. When everyone disagrees with Ashley, he brings up the point that he predicted HTML5 would replace Flash, so we should just blindly trust his decisions because we just don't see it yet. I think that is a weak argument.

"I can't believe Scirra chose a HTML5 runtime instead of Flash. It just doesn't make any sense. Everyone is doing everything in Flash so obviously that was what they should have done. Also they have started charging money when Construct Classic was free, especially when C2 is so early on at this stage of development compared to CC. Obviously this will drive away users. I think I'll choose another tool. HTML5 also only runs in Chrome and Firefox right now so it seems needlessly limited, and we don't know if other browsers will ever support it. It seems like it was a desparate afterthought. It's sad to see Scirra making such crazy choices. It seems like they'll just fade in to obscurity to be overtaken by other tools. Too bad they're doomed."

- Everyone in 2011

I think that was a good decision to switch to HTML5, but I don't know why you take so much credit for predicting that? I think a lot of us made that prediction about HTML5 being easier to use than Flash and it would eventually replace Flash. Maybe not on these forums. I wasn't around here then, but this was a popular opinion among us working in the web.

It was really Apple that gave a huge blow to Flash. I don't think too many people predicted that. (Thinking back, it makes sense. Apple does this often.) I think a lot of us thought that eventually people would switch to HMTL5, but it would be a long, and slow process. When people become comfortable with a product, it's harder for them to switch.

Flash isn't entirely dead yet either, btw. ActionScript is still being used, there's still games sites dedicated to Flash games, CNN and other major news sites still use Flash to show videos, there are still Flash ads around (IMDB), etc. Flash is now called Animate CC, but you can still use ActionScript in it. The only thing is really dead is Flash websites. I haven't seen any of those for a while. But it was always bad practice to build a website entirely in Flash.

All those people who tried to convince you to use Flash, they probably haven't gone very far. Obviously, they aren't here, but I wouldn't be surprised they are still using Flash somewhere, if they haven't switched to HTML5 by now.

Discuss your concerns all you want. After awhile, you'll realize you're talking to a brick wall and may start to wonder "haven't I read these concerns a hundred times already?" No amount of concern-having is going to change anything is all I'm saying. If that were the case, C3 would have come out with all the features that were asked for. It wasn't, and it might later. Maybe.

You might be right, but I'm an artist too, and brick walls are my canvas. I'm going to continue to paint.

(btw, I also use to work in greeting cards)

Nice tutorial. Another great use of Construct.

Eat my shorts, Moot. I can post in any thread that you can. And if you wonder why I'm still "here," it's because I paid for the program I still use as a prototype tool, that's why. I have the freedom to say what I please and to reiterate the fact that people should learn to program and stop griping about the direction C3 is going as much as you have the right to repeat yourself verbatim.

Relax, I didn't say you had to "embrace it, or leave it." I would never say something like that...

Post away! Tell us more how we shouldn't discuss our concerns with C3.

C3 isn't what anyone was hoping for. But it is what it is. Embrace it, or leave it. It's pretty much that simple. If you're not a pro who makes a living off this thing, why bother? Serious question. For all those who keep regurgitating the same points over and over: learn how to program, use a serious development tool, and make games. Or move to an engine that supports your workflow and ethics. There are plenty to choose from. I've made the move from Unity to Godot now. C3 is good for what it is.. a web engine for browser games.

No one is really asking you to read and participate in this thread. If you tire of reading about the same issues people are having with C3, maybe its best to avoid threads like this. There's a feel good thread somewhere on this board. I think it's called, "Positive Vibes."

And if you already moved on to Godot, why are you still here trying to order people around? It makes no sense.

I wonder what the specs are for the Macs Scirra is using to test C3? A lot of us Mac users are having issues.

I'm also concerned about C3 being Chrome exclusive. Where's the logic in that? The whole point of making games for the web is that your content is accessible by anyone with an internet connection. As of right now, it's only reasonable to test your games in Chrome. And who knows, maybe our games only work well for those Chrome users have the latest build of Chrome installed. This frustrates me.

Moot

Can you post the .c3p file that is giving you trouble? Maybe there is a problem with one of the behaviours you are using.

It's just two 64x64 sprites, one with a solid behavior and the other with a platform behavior. The sprite with the solid behavior is stretched to make the ground. Everything else is just default settings. No events. Super basic.

I'm using the most current stable version of Chrome and an iMac.

Mac Specs:

macOS Sierra Version 10.12.4

iMac (Retina 5k, 27-inch, Late 2015)

Processor 3.2 GHz Intel Core i5

12 GB 1867 MHz DDR3

AMD Radeon R9 M380 2048

I can't even make a simple platform with two sprites without running into problems. After moving the player sprite back and forth for a couple seconds, the player sprite starts to sputter across the screen. In debug mode, it's says it's 60 fps, but it doesn't appear that way. Maybe it has something to do the preview window.

If the problem is Chrome, I don't see how Ashley can fix that. We are kinda at the mercy of Google.

Have you tried "compare touch speed"? I can already make a fruit ninja game with that.

I don't think I have, but I already found what works best for me. I basically use a floating analog stick for 8 direction movement.

I think this is the tutorial I used, but since adapted it for personal use:

https://www.scirra.com/tutorials/398/to ... ers/page-1

Quote Ashley referred to in his blog post:

"And chrome is a hog. Its huge and complicated. It uses ram and CPU like nobody's business, and it totally thrashes your battery life."

This statement is absolutely true, at least on a Mac. I posted my findings in the now deleted Official C3 information thread about this. Chrome is no way optimized for use on a Mac, and it's even missing features the PC has. Google simply doesn't care. I'm surprised they have a Mac version at all, because Apple is not friendly to Google. Apple is all about protecting user's privacy, and Google is all about taking as much information from you as possible and then selling it.