Construct 3 any news?

> Also sometimes the code doesn't do what you expect it to do which require strange workarounds.

>

Well, if you have concrete examples that may be considered as C2 bugs, please report them, following the bug report guidelines.

If indeed some events are not working as they should because of the way C2 is programmed it first needs to be reported for it to be fixed.

> Still not actually figured out how break points work or what they do in spite of having read the manual!

>

When you set a breakpoint for events in the event sheet and debug your project (not just run the regular preview), the execution of the code/program will stop when the breakpoint is reached and allow you to explore further the objects/values in the debugger.

Ahh, believe it or not, I haven't used the debugger yet

It would be a huge project for any programming tool to add non-programming support anywhere near as sophisticated as C2's - there is an absolute ton of features in there ranging from top-level features like functions and loops down to unique internal optimisations to make it run fast enough, all built up and tuned over a period of years. I would be super surprised if anyone could get anything remotely comparable even after say a year, if they are starting from scratch, and they'd have to have a 100% focus on it the whole time.

It would be a huge project for any programming tool to add non-programming support anywhere near as sophisticated as C2's - there is an absolute ton of features in there ranging from top-level features like functions and loops down to unique internal optimisations to make it run fast enough, all built up and tuned over a period of years. I would be super surprised if anyone could get anything remotely comparable even after say a year, if they are starting from scratch, and they'd have to have a 100% focus on it the whole time.

Ashley you are right on that for sure but it is a bit different on their end.

The Godot team is not doing everything by themselves, they also seem to "outsource" a lot of their work kinda like C2 does with plugins.

I don't mean to say that C2/C3 should be open source and free for any kind of community modding, what I mean to say is that they have more people actively working on their engine, which obviously results in less time of development for whatever feature they are looking forward to add to their engine.

Besides from all that, I think what the community would like to see is some more information about C3.

I fully understand if you don't want to share explicit information about features you work on

because of the risk that people could steal those and make their own thing out of it.

The thing we would like to see is for example some sort of monthly progress report like you already do all the time about awesome new technology and updates, perhaps is there a reason for the lack of information for the last couple of months?

Are you not allowed to share further information? Is C3 already in a state were it's about to get cancelled?

Even though I started with C2, I can clearly see that the development of C1/C2 really got pushed by the help from the community.

When you plan to take out the help of the community from C3's development (I highly doubt that you would plan to do so), then what is the point of waiting for C3 for the next years in first place when others offer something equally good with more community integration?

This is why I think that any kind of information regarding the current state of C3 would be nice and well appreciated by the community.

We are basically working full-time on C3 and it's been our focus for over a year now. It is certainly not going to be cancelled or anything like that. We are just not ready to share any information yet for a few reasons:

• C2 is still a great product and actively maintained, and we think it's best for users to keep focusing on C2 instead of sitting around waiting for C3 (especially since we still don't know when it will be ready)
• we don't want to say something and then end up delaying, modifying or ultimately removing any particular feature we talked about - right now everything is still subject to change
• public information about the state of C3 could affect our competitive edge, especially since we're doing some pretty interesting stuff
• we don't want to ruin the surprise!

Rest assured we are working daily to get C3 ready as soon as possible, and we will share more information when we're ready.

We are basically working full-time on C3 and it's been our focus for over a year now. It is certainly not going to be cancelled or anything like that. We are just not ready to share any information yet for a few reasons:

- C2 is still a great product and actively maintained, and we think it's best for users to keep focusing on C2 instead of sitting around waiting for C3 (especially since we still don't know when it will be ready)

- we don't want to say something and then end up delaying, modifying or ultimately removing any particular feature we talked about - right now everything is still subject to change

- public information about the state of C3 could affect our competitive edge, especially since we're doing some pretty interesting stuff

- we don't want to ruin the surprise!

Rest assured we are working daily to get C3 ready as soon as possible, and we will share more information when we're ready.

At first thank you very much, for the information and the great support towards the current engine Ashley !

This really helps me out the least and explains why we heard nothing from C3 for the past time.

Even if you think that information like this is vague and not necessary to be shared with the community,

I can assure you that every bit of information like this is appreciated and helps us to get a point of view for the current state of C3.

Feel free to post any "not blogpost worthy" information regarding C3 in the forums instead of keeping

it secret in future too and thanks again for all the work you do on the forums daily for the Construct community.

- public information about the state of C3 could affect our competitive edge, especially since we're doing some pretty interesting stuff

- we don't want to ruin the surprise!

That's what I like in techs. The innovations and surprises. I really also think that C3 shouldn't be rushed or any way give out information yet about the new features even if I want to. C2 is still usable and non-obsolete so we can still hold the fort till it's done. Besides it's better to enjoy the license we paid for a little longer .

I don't mean to say that C2/C3 should be open source and free for any kind of community modding, what I mean to say is that they have more people actively working on their engine, which obviously results in less time of development for whatever feature they are looking forward to add to their engine.

This not always end up well. I heard numerous complatints about Unity that they included some 3rd party plugins into the engine which did not fit well into the workflow.

Feel free to post any "not blogpost worthy" information regarding C3 in the forums instead of keeping

it secret in future too and thanks again for all the work you do daily on the forums for the Construct community.

+1

You don't have to post information about features and anything like that. We understand your reasons. But sometimes a little heads up like "It's still under development" is good for the Community.

True, if Godot can integrate a visual programming method that can match C2/C3's then Scirra will have a serious competition.

I think this will be C2/C3 true competitor. 2D, 3D, Event programming or coding. Native exports instead of wrapper, IAP etc2

http://spark.tools/versatile-game-engine/#Code_or_Not

If scirra is taking too long with C3 and spark game engine is released early. I can see a lot of C2 user will jump over.

C2 is already great, really all we need is native export options for mobiles that bypass the wrapper limitations, such as frame rate control and efficiency gains of native vs wrappers.

I feel that for PC, our current options are good enough lately. It's just lacking for mobiles. Yes it's getting better, but those limitations still puts C2 as always the non-optimal solution.

tumira

I read up on Spark, it sounds too much like hype and PR without substance. Will keep an eye on it, but as far as believing their claims, don't put too much faith on it.

Wow, I only just seriously checked out Spark, and that's the closest thing to Construct I've seen in a while! They even have "Event sheets" and "Behaviors" which look very similar to what C2 does. Still, it's unreleased, and they have a smaller team and a lot of catching up to do, but I'll be interested to see what their take on the event system is.

Construct 2 is great for web games and when you use some of the official plugins. But Scirra says: "Build Once. Publish Everywhere. True multiplatform support. Build your game in Construct 2 and publish it to all these platforms." and it's not true. Is not possible to build games for all these platforms only using C2 for it or without a damn wrapper and the majority of the C2 users want publish their games mainly for mobiles. I really like the structure of the Construct 2 and I'm a huge Scirra's fan, but honestly, I think C3 will be a aesthetic update of C2 with some improvements.

tumira: Wow! No more wrappers?? Timeline? Easy in-app and ads implementation? 2d and 3d? Thank you! Spark is very promising!

—: PR without substance? Really? I think that we didn't see the same website.

Here is a demo video I found on their forums.

Youtube Link

What do you guys think?

Spark is going to be released on April : https://twitter.com/SparkGameEngine/sta ... 5288163329

i think i am going to test it and hope using it for my next projects until C3 is out

Ashley i know there is no released date yet , but is there any chance for a closed alpha test next months ?

Imagine since the future of C2 announced 1 Year + 2 month; so let's predict the status with probabilities.

Average: 50 lines of code each days= ~19750 lines. The Result: not finished yet.

But we can expect beta after 20000 lines of code.. This mean july 2016...

This is how i see the future/

ps: However, no one here has yet exploited C2 at 100%.

I am not comparing Spark with Construct 2 negatively but I really think Spark is a dream Game Making Software. With it's event system for 2D and 3D will be it's strongest chess piece into winning the game developers. Not to mention it's native export that is not dependent to any 3rd party Wrappers. A nice forum just like Scirra and fun interface too. The downfall I only see is that the program is new and may contain many bugs, few items in it's asset store, may contain very limited features since it's new, a coding option that will be a sign that the event sheet cannot do everything the code editor can do, so everyone who uses Spark must learn how to code "Haxe" so you won't be left out of other advanced features.

Edit:

I read that the Spark Game Engine editor works on mobile, browsers and etc. and you can also make behaviors through the event system and very automated since you can right click on a sprite and add any behavior. That is very amazing if you think about it except, I think the browser part should be optional. Since the exporter they use is their own then this might just be the answer to all mobile export problems since they can just fix it when they find any bugs, that is if they aren't false advertising. If Construct 3 will have their own native exporter then it will be the end of headaches. <img src="{SMILIES_PATH}/icon_e_wink.gif" alt=";-)" title="Wink">

http://spark.tools/