My first impression - C2 in a browser.

I would prefer a normal downloadable version.

I have pressed them on a desktop version and they said they would have a free version available but maybe not until after the game jam.

My first impression is that this is actually an alpha build and not ready for public beta testing yet. I'll probably be checking back in a few weeks to see where the development is at by then.

Hey Burvey!

Haven't seen you around the forum much. Hope all is well.

Yes I have to agree and with only 40 events and no features that were hyped to test I can't see how this is helping them to sell people on C3 and may do the opposite.

This should have been run with experienced apha testers instead of a public release I think.

Im pretty sure this should be on a tshirt:

LOL- did you try to change your profile pic too?

Today is the release of the free Beta of C3 and if you have not tried it here is the link:

https://editor.construct.net/

I gave it a try this morning and had a few problems getting the demo's to run until I turned off adblocker and enabled pop ups.

Then I tried a few of my current C2 games that don't have alot of events and no addons but couldn't get them to run.

Finally got one game that has only 20 events to run so I could test it a llttle and it worked fine.

Noticed some significant lag when I frst ran C3 and after posting a bug report I checked my platform settings and discovered I was running Chrome 32 which came on the 64 bit computer I purchased a year ago so I updated to Chrome 64 and that seems to have solved some of the lag problem so C3 was useful in that respect.

I have not tried designing a game in C3 yet and will probably try that tonight but if you have and you want to share your experiences or first impressions of C3 I would be interested in your impressions.

Try to keep it civil and remember this is a Beta test so bugs are expected for awhile.

Chrome also has a business and education versions that have more security features and limits users from changing settings and destroying history.

Those are not updated very often so something to consider if you plan on using C3 in one of those versions.

Couple ways to do it:

You can use a blank sprite pinned to your blocks or you can check if blocks collide with ground or another block and then set a variable to turn off the crushing event.

I prefer the variable trigger instead of creating a bunch of extra sprites but whichever works for you.

You can use a button to add a number to a global variable and the run an event based on that number.

Global variable NUMBER=0, Global Variable TRIGGER =0

On Key Pressed: Add 1 to NUMBER, Set TRIGGER = 1

On NUMBER = 1: do something, Set TRIGGER = 0

Triiger = 1

I have to agree that a very limited C3 version is not going to be an adequate test for bugs or how the system operates under load with lots of events, sprites and effects running.

If this is what the free version after the beta test is going to be I don't see much use in using it but maybe other people will.

I would suggest a full version with limited events to 100 like Scirra did with C2 so we can really dig in and see if it is worth paying a subscription for.

The goal is to stamp out as many bugs as possible before we start selling it - we think people would be more upset buying buggy software.

Hey Tom- I think I figured out the Chrome cache issue and I posted it in the bug reports.

I have a 64 bit system that came with chrome installed so I assumed it was the 64 bit version. Turns out it was 32 so I updated to 64 bit and lag seems to have went away but have not tried it enough to know for sure.

May be an issue other users have so you probably want to look into it and tell users having lag to check their Chrome version and update.

Hope that helps!