Yeah agreed, but let's not give them cool titles. They are just filthy criminals - nothing more nothing less!

No, HTML anything is flawed because it relies on browsers - for the most part Chrome.

Chrome is flawed because Gogle doesn't care about anybody else - the least of all C2.

So stop developing C2 - it is flawed because it is HTML5.

Start work on C3, and go back to targeting the OS, Win\Mac\Linux.

Start C3!!

I absolutely love C2, use it every day, but I really think it is a dead end - sadly.

For the most part C2 relies on Chrome, and is all too often broken because of it, has been for months and possibly for a few more - really!!!

Mobile is awash with crap apps, and is largely a waste of time imo.

Stop working on C2 because it is flawed due to third party reliance (we don't care about anyone else vendors), and as we all realize by now, it will not get any better - that is the way of the web, always has and always will.

Start working on C3. Use what you have learnt from CC and C2 to build a better desktop development game tool. Build it with 3D and 2D development in mind, and with exporters for Win\Mac\Linux.

Forget about google, and all the other web environments - they don't care, period!

No one blames google because your game runs like a slow motion picture with added jerkiness. No they blame you the game dev - as far as they are concerned you can't make a good game, after all even your simple 2D game doesn't run smoothly on a super machine that runs Far Cry or Need 4 Speed at 1920 x 1080 with every option set to high...!?!?!??

Start the crow funding now Ashley - I'm in already....

Hmmmmm.......

Most people rely on chrome for c2 games.

Chrome is broken, for some months already. This means for most people, that c2 is broken because chrome is broken. And the best we can do is wait a few more months for chrome to be fixed so that c2 is no longer broken!

That is of course if the next chrome release fixes it.

This is of course - as noted in other related topics - becoming a familiar scenario.

There is a song you may be familiar with: video killed the radio star.

Our song could be: chrome killed the video game star (c2).

This not a good way to start 2015....

This is a very hot topic in other posts, and has been for a long time.

We are talking about Google here... They break something and then fix it when, they, are ready (or at least we hope they will). Hopefully the fix will come early 2015.

The question is: How long till they break it again, and how long till they fix it again.... and again....and again....

Yeah, noticed that myself... I think something is broken. But we will have to wait for the Scirra boys to com back from well deserved rest.

Probably better posting this thread in Website Issues forum....

To me the best way would be to finish running the event sheet (which includes finishing the trigger events, so basically stopping the sheet) THEN destroy all objects and change layout.

Definately makes sense to me as well.

Since it is not classed as a bug, maybe it would make a good feature request.....

xfinigames

zenox98 is correct.

If you sign in to your account and then go to the store, and on the left panel toward the bottom select Your Downloads. from there you can download your licence file and underneath the download button is the hyperlink to download your assets....

Happy coding

—

Chrome is the dominant browsers, for Win 7/8, so its the goto browser for testing for most of us.

True indeed, but given the size of Google and the resources at its disposal you can't help but ask why this ongoing issue has not been solved already, options:

Can't fix it Don't care - the fix can wait till google is ready HTML5 is not ready for serious workloads - like games

This isn't a C2 problem but... it is a C2 problem in the end, because we rely on these end tools to export.

Not a C2 problem, but a C2 flaw, because it is 100% reliant on third parties who simply aren't concerned enough to give priority to the bugs they introduce.

HTML5 is designed for the web, fine, we get that, but this situation is critical because the web (Chrome & Firefox being the bulk) currently is broken for HTML5 games.

Sadly this problem is inherent to the web. Browser wars, inconsistencies, and unfixed bugs, have always been the way of the web. It is not likely to ever improve....

So atm, here's the export options:....

The way I see it, the only export option right now is Win8. All the other options are broken.

szymek

There's nothing unsolvable here, we should see improve through 2015 and beyond

Now that does sound familiar....

Saddest part:

Construct 2 is easily the best 2D game dev tool around (imo) - excellent work flow, frequent updates, prompt bug fixes, new features continually added.

But it constantly gets broken for the most part - if you want the world to play your game - by third party dependencies!!!

This kind of thing is always going to be an issue, has been in the past, is right now, and will again be in the future.

The only option we have, each time the other party creates a bug, is to wait for the other party to fix the problem...

Of course in the meantime you cop the 'what a crappy game' from the would-be player\customer - well that is good for business...

Been following the numerous threads on this whole chrome stutter thing.

Since we target Windows 8 we use IE for all testing.

Now due to the holiday break I decided to run one of our games in Chrome, and - the stuttering, whaattt!!! - Chrome is completely broken.

The fact that this has been going on for months now, and still hasn't been addressed by the big guns does not (IMO) bode well for our chosen dev tool - C2.

Either Google don't care, can't fix it, or the problem lies only with C2 builds - either way it leave all Devs in this circle in a precarious position.

Sadly since Node depends on Chrome, export to desktop is also flawed.

This is a crying shame, give the brilliant work-flo of C2, and its very quick update cycle, only to be ruined by third party requirements.

This could be the first time in history, where you have to display a banner in your game that reads: "You are running your game in Chrome. Please note that this game requires IE for smooth performance!"

Just an update to confirm this issue is also present on Windows 8.1 using R192....

Re-Posted here from General forum as requested ASHLEY.

This isn't a bug with the C2 Engine, but a glitch in the Styles for the Editor, hence no capx.

Just wanted to let you know that Office 2013 styles do not retain the style for the tabs.

This is how the tabs appear when the style is loaded using View\Themes\Style options:

[attachment=1:3rc60sf2][/attachment:3rc60sf2]

This is how the tabs appear when you restart C2:

[attachment=0:3rc60sf2][/attachment:3rc60sf2]

So you have to reselect the style every time you start C2 so that the Tabs are consistent with the style.

And on a side note the status bar is always Blue, it would be nice if it would match the selected style. For example, as a suggestion when using the Office 2013 Dark Gray style the status bar should match the Window Title area.

Just a minor thing but would love to see it fixed.

Just in case it makes a difference this issue is with R191, on windows 10 preview. Don't know if it was present on 8.1, I was using a different style before.