So What Is Your Second Impression of C3 And Will You Buy?

I havn't had time to play around with it much, so waiting to give my second opinion until I've tried the full version. Not the beta.

But considering what I've seen so far, I'm optimistic. Looks very promising and I'm curious to see what will come in the future.

Latest blog post covered a lot of stuff that sounds very promising, so I hope with a bit of time there will be even more fun stuff to play around with. I really hope they get the community support, so they can staff up, and provide more of those neat improvements, features, plugins, etc we've been missing in C2 even faster.

Please tell us how you will be using C3 if you will be subscribing and if you are a serious game designer, small time game designer, hobbyist, educator or using the engine for some other purpose?

Also please tell us if you are a long time C2 user or new to game design or switching from some other engine to a Sciirra engine?

I'm curious how stuff like Selective Collision for Solids will be fixed in C3 since it was not possible in C2 runtime.

And I've got my answer: https://www.scirra.com/blog/204/the-fut ... -3-runtime

[quote:1q5ancv1]

Please tell us how you will be using C3 if you will be subscribing and if you are a serious game designer, small time game designer, hobbyist, educator or using the engine for some other purpose?

Also please tell us if you are a long time C2 user or new to game design or switching from some other engine to a Sciirra engine?

I still have C2 for prototyping, but as a hobbyist, I will not use C3 because of subscription model. This doesn't mean that is bad. Is definitely cheaper then Cocoon.io's 500$ to remove splashscreen.

Not sure how C3 will handle bigger games, but for web or smaller games, it is still a very good engine.

I did not depend on C2 so is easy for me to switch to another engine. Also, it didn't take too much time for other users to port their progress to Unity. (it is unpleasant, but doable)

I Started out in CC and moved to C2 early on, still working in CC for a while until C2 had matured sufficiently. I work on big, multi-year projects.

At the moment I probably won't subscribe. When the software is a fair bit more mature than C2 currently is I may revisit it, however by then I may have found a more suitable replacement for my needs. I was not even remotely interested in looking at other game creation software before, but now I am actively researching it. If F3, or Godot or Gamemaker or Unity really don't click with me I will probably return to Construct, but unfortunately in its current form it's unappealing to me. Time will tell, but I will probably wait until it matures further and also see if the subscripton is eventually tweaked or discarded entirely.

I won't be "buying" it because you can only rent it. :p

I won't be doing renting, either. I don't feel thrilled with the prospect that if I don't have the money around time to pay dues, I have to put everything I was working with on hold for a month or more.

and then I'm sure they'll get upset anyway because something they once paid for no longer works..

I know, which is why I'm not going to pay into a subscription system because I will be upset the whole thing is inaccessible after I already put money into it, considering the above. :p

lamar

I'm employed in the gaming industry as a Graphic Designer (currently online casino gaming), and have been working at AAA studios, and indie studios in the past.

I have been using C2 on and off for about 3 years, doing my spare time projects for fun, but aiming to release my own games eventually. As a non coder Construct 2 was my perfect tool since I don't have any interest whatsoever in learning any coding language. I feel dyslectic or an anaphabet when looking at regular code syntax, but the Event sheet I can comprehend very easily.

I've tried a plethora of different engines but many of them required code or used some weird state-machine coding which I didn't like either. My main reason for choosing Scirra's product is the Event Sheet. I have failed miserably in the past producing anything even remotely resembling a game in other engines but C2 allows me to take my ideas from paper to actually, interactive games.

I'm using C2 in my spare time for my own projects at my own pace learning as I go, but aiming to release my own professional looking games with it.

I will be subscribing since I like C2, i think C3 looks promising.

Subscription/Web based/Html5/Performance/native or non native -- None of those are any issues to me. As long as they keep the Event sheet and and keep improving by time I'm a happy camper. Without C2 (or the event sheet) I wouldn't be making any games at all probably.

Subscription/Web based/Html5/Performance/native or non native -- None of those are any issues to me. As long as they keep the Event sheet and and keep improving by time I'm a happy camper. Without C2 (or the event sheet) I wouldn't be making any games at all probably.

I guess my biggest reason for not wanting to go along with this is because I planned on going to Unity after I finish my current game in C2, which I already know enough of C# in it to get by. This means I guess I don't have the problem like you and others who are in the same boat, so I don't even have to pay for anything until later to use Unity, and it's just a one-off fee. I just loved using C2 because it took 1/10 the time to get things done, but I guess that gravy train will come to a screeching halt when Scirra stops supporting C2.

I just loved using C2 because it took 1/10 the time to get things done, but I guess that gravy train will come to a screeching halt when Scirra stops supporting C2.

Reading the blog post today that has already happened. Ashley says they are going to write a new runtime so I wouldn't expect any more support for C2 and like Construct Classic it was a great engine that was improperly advertised as an engine for professional game design.

I would hope Scirra puts C2 in public domain and let the people that designed all the plugins work it over and it would probably be a great engine but I doubt that will happen.

> Subscription/Web based/Html5/Performance/native or non native -- None of those are any issues to me. As long as they keep the Event sheet and and keep improving by time I'm a happy camper. Without C2 (or the event sheet) I wouldn't be making any games at all probably.

>

I guess my biggest reason for not wanting to go along with this is because I planned on going to Unity after I finish my current game in C2, which I already know enough of C# in it to get by. This means I guess I don't have the problem like you and others who are in the same boat, so I don't even have to pay for anything until later to use Unity, and it's just a one-off fee. I just loved using C2 because it took 1/10 the time to get things done, but I guess that gravy train will come to a screeching halt when Scirra stops supporting C2.

As a Graphic designer I need to push this argument: I have no intention whatsoever of becoming a programmer. I am Graphic artist and designer. I don't wanna waste my time coding or learning how to code. I want to make my ideas happen, in an easy comprehensible way as possible, and that's what Scirra is giving me. Learning syntax, coding languages etc etc is a waste of my time. I have no problem using other engines, but that would be when teamed up with coders.

I think Scirra should advertise on pages like deviant art. They would have amazing looking games in their show-off page in no time.

C2 is a perfect solo tool. It's not aimed for teams, they don't have any teamwork functionality, so multiple people can work on same projects easily.

Reading the blog post today that has already happened. Ashley says they are going to write a new runtime so I wouldn't expect any more support for C2

Please don't mis-represent our posts. That very blog post specifically emphasises that we will continue to maintain C2.

I'm an animator and visual effects artist and I've used C2 for hobby/prototype reasons, exporting mostly for desktop.

I do have a current game for desktop/mobile I am developing that I hope to take fully to market. It is a 3D ISO style game which you can't do in any flavor of Construct (I had fingers crossed for C3) so I jumped over to Unity with Playmaker.

I am not a fan of most google products (I know I am in the minority), so I will probably skip C3 and have high hopes for C4.

Reading the blog post today that has already happened. Ashley says they are going to write a new runtime so I wouldn't expect any more support for C2 and like Construct Classic it was a great engine that was improperly advertised as an engine for professional game design.

I would hope Scirra puts C2 in public domain and let the people that designed all the plugins work it over and it would probably be a great engine but I doubt that will happen.

I know, I'm just saying this doesn't apply to me, hence why I would be moving away from C2.

The Construct 2 runtime in the Construct 2 editor (C2): this will see continued maintenance much as we have done for Construct 2 over the past year.

Doesn't look like they plan to dump it anytime soon. I'm just saying when they inevitably do dump it (hopefully) years down the road, that's the end of that.

Ashley Sorry if I'm coming across as a killjoy, I just am highly skeptical of anything that hasn't proven itself to me yet and I did say I would buy into the subscription model if there are extraordinary circumstances, which you've done many times with C2.

I will buy C3 the day it comes out. So excited for the release.

>

> > Subscription/Web based/Html5/Performance/native or non native -- None of those are any issues to me. As long as they keep the Event sheet and and keep improving by time I'm a happy camper. Without C2 (or the event sheet) I wouldn't be making any games at all probably.

> >

>

> I guess my biggest reason for not wanting to go along with this is because I planned on going to Unity after I finish my current game in C2, which I already know enough of C# in it to get by. This means I guess I don't have the problem like you and others who are in the same boat, so I don't even have to pay for anything until later to use Unity, and it's just a one-off fee. I just loved using C2 because it took 1/10 the time to get things done, but I guess that gravy train will come to a screeching halt when Scirra stops supporting C2.

>

As a Graphic designer I need to push this argument: I have no intention whatsoever of becoming a programmer. I am Graphic artist and designer. I don't wanna waste my time coding or learning how to code. I want to make my ideas happen, in an easy comprehensible way as possible, and that's what Scirra is giving me. Learning syntax, coding languages etc etc is a waste of my time. I have no problem using other engines, but that would be when teamed up with coders.

I think Scirra should advertise on pages like deviant art. They would have amazing looking games in their show-off page in no time.

C2 is a perfect solo tool. It's not aimed for teams, they don't have any teamwork functionality, so multiple people can work on same projects easily.

This.

The code was my biggest issue, but we still have to code to get your own plugs, which I thought was to be addressed in C3.

I can't rely on plugs that aren't maintained, and/ or have to be redone for each new runtime.

And official plugs provide just the basics, and yet they discourage anyone from modifying them.

> Reading the blog post today that has already happened. Ashley says they are going to write a new runtime so I wouldn't expect any more support for C2

>

Please don't mis-represent our posts. That very blog post specifically emphasises that we will continue to maintain C2.

Sorry Ashley if I misrepresented it but I was sure the first time I read that blog it said you were going to let C2 sunset?

I remember it because the word "sunset" caught my attention.

Did you edit your blog by any chance?

Maybe I just didn't read what I thought I read?

Regardless, do you have any time frame on these runtimes?

This.

The code was my biggest issue, but we still have to code to get your own plugs, which I thought was to be addressed in C3.

I can't rely on plugs that aren't maintained, and/ or have to be redone for each new runtime.

And official plugs provide just the basics, and yet they discourage anyone from modifying them.

Did you check the latest blog post?

* Modular event features, aimed at capabilities like building plugins out of events

Is this what you mean?

But yeah. We can't have everything right? I barely use 3rd party plugins... very sparsely. The only one I'm using at the moment is Photon Cloud for Multiplayer, and started to use Q3D, exploring the possibilities of making my game fully 3D instead.

Hopefully Scirra will have more time to build and maintain their own plugins building up a library. And I wouldn't even mind if they charged for some of them, if they took a lot of time/manpower to develop.

If I really needed a specific plugin in construct for e serious project and was stuck. I would got to elance.com and get a freelancer to do it, or do a paid request here on the forum, getting someone to do it for me. There's always ways if you really need something.