Aphrodite ahh I see, I understood it like you were talking about all "buyers" from the initial release .

In that case I see no reasons to not agree with you.

Expectations for native comes from scirra.com main page itself - "Build Once. Publish Everywhere. True multiplatform support. Build your game in Construct 2 and publish it to all these platforms." statement.

Don't know why but people these days forgot how to read and use their logic. Instead of finding out more info about the product their will go ahead and download/buy it. And only after that they realize that this is not exactly what they thought it is. Free user have a bit better situation because they can only export to the web, so all is fine here. How game will work will mostly depend only on the browsers. But people who bought it before reading/thinking will hit the wall right away. So yeah scirra should really figure it out.

Also i noticed some part of my previous post did not show so I'll put it here again.

Web export. Yes. For me It's like an Image Editor. Add it, if it work leave it, make some occasional fixes and small additions, forget about it. There's so much stuff missing I don't even know where to start...

And just like Construct was Construct 2 will never be called a finished product. Complete product have some kind of a road map that goes from A to B and either as a developer you can make and release a full product - like most people used to do in the past. Or release it as a very popular these days "early access" scheme . Which is not bad (well not in every case) because it lets you play with it while devs have time and money to finish it up. But it still means there is a point B somewhere. Unfortunately there was only point A with C2 (and CC) there is no point B and will never be. And i don't really like it cause I don't know what to expect in the future.

With some sort of a to do list we could tell what and when to expect from it, What was done, what is in development and what are the plans for next months. But not here. It's all just one big experiment. If Ashley is in good mood he may fix some issues, if he is not then he will say "it's not compatible with our UI library"

C2 will end up just like CC did. One day they will announce "This is C3. We will no longer support C2 from this day. Buy C3 or stick with old unfinished C2"

To be honest I will not fall into that trap again. I will get C3 only if I see some sort of a road map or to do list with time tables, that will let me know what and when to expect from it. I will not spend my money on something I was told I will get just to read many months later "yeah, sorry but no" again

...I do not mind the absence of native exporter at all (even though some people seems to have missed that part when buying it, entirely their fault of course but it could maybe have been clearer)...

I'm not sure i can agree with you on that "entirely their fault of course" part cause it kind insults me

I bought a licence somewhere in the middle of 2011, just because I loved using Construct and I knew that by supporting the team they will make C2 far more superior (with all of the features yet to be added to the engine and idiotic things and bugs from Construct fixed).

Then few months later Construct 2 r62 comes out with a blog post saying:

"As I mentioned, we're hard at work on our HTML5 features right now. However, one of our long term plans is the possibility of releasing an Exporter Development Kit (EDK) in the long term future. (I must emphasise that's the long term future - please don't get too excited just yet!)"

I did not mind that and probably no one did at the time, because C2 was still in early stage and we were all busy with Construct projects. So I waited, doing my stuff and playing/learning with new C2 releases.

10 months lates C2 r100 introduced Windows exe export by using Awesomium, which was total crap saying it lightly. 5 months later (C2 r115) Awesomium was dropped and node-webkit was introduced as a replacement. We all know the rest.

Sometime later EDK died completely with a brief post "...we're most likely not going to provide an EDK".

You might be the one who actually bought C2 just for its html5 capabilities and can't blame you for that. C2 was and still is the best and easiest tool for making web games and probably only C3 will surpass it. But don't forget there are people like me who bought it very early not only for html5 but also for other export options (especially native exe was always in high demand) we were told we will get after some time

All we get after 4 years is Node-we...sorry "NW.js" which still works like a cra...chromium

imaffett

Again, thank you for your assistance and the speed on solving that issue!

But if I may asking you one more question, about that XDK Debugger thing from this post

https://www.scirra.com/forum/crosswalk-intel-xdk-experiences_p908852?#p908852

It used to work fine with my phone but in current XDK version (and previous one too) it just stopped and keep telling me to install this app on my phone. But after downloading it just gives me a "fail" screen.

Debugger option is the closest thing I could get to test my projects on my phone without doing the build - quality and performance is almost the same in debugger and proper build.

And XDK Emulate never worked as good as debugger.

doomredmage yes 11 and 12 are safe - only 7 is somehow affected. And that was a reason of my question above, wanted to update my game from 7 to 12 and apparently it's not possible...

The error message is correct ("Scripts may close only the windows that were opened by it"). Web pages cannot arbitrarily close windows that the user opened. They can only close windows that were opened by a script. I think browsers actually have a more complicated set of rules than that to determine if a page is allowed to close its own window, but basically you can't really rely on it.

Yes I understand that. But this page we are talking about here is a paged opened by C2 preview (or exported from c2).

And if I can't rely on Browser.Close then how can I exit the app from NW or Crosswalk? :/

imaffett or whoever is now from Intel on forums

I opened up my project in XDK (1912) changed: App Version from 1.0.4 to 1.0.5, App Version Code from 5 to 6 and Crosswalk Version from 7 to 12 (due to this idiotic SSL situation).

But after successful build now I can't upload it to google play anymore because for some reasons this little changes I made have changed my signed certificate!

crypticblonde

1-2k event's are not that many if you think about it. My small - medium small games are around 500-700 events (without event repetitions).

But it all depends on the way you make them. One will use 20 event to move sprite forward, other one will use only 2 event.

jlwinn8

It's always a good idea to split your code (groups, evens sheets, different variable values...) mainly for your own sake. It's easier to maintain and find what you are looking for if your events are nice and tidy.

As of the initial question, I would say yes. You can always include a event sheet (or turn on the group) only for stuff you want to happen. If something is not needed at current time in the game there is no point making C2 run through all of these events

This is probably the browser security that avoids been able to close the window programmatically. If you can make another page that you control launch the game then you should be able to close it from the parent. Sending a signal from the game to it.

What do you mean?

It used to work fine on every project in the past. It works fine with every new projects I made. Only in the project I'm currently working on for some reasons this is not working. There is nothing different between this project or any other projects.

It's just a simple action. on sprite touched -> close window

EDIT: hmm and now for some other strange reasons it starts to work properly... without me doing anything

Ashley I'm getting a strange issue with Browser plugin and "Close" action.

After triggering "Close" in preview or export nothing happens and Chrome Console (and also FireFox console) gives me :

Scripts may close only the windows that were opened by it.[/code:12y266ql]

which point to Browser_plugin.js:

[code:12y266ql]Acts.prototype.Close = function ()
	{
		if (this.runtime.isCocoonJs)
			CocoonJS["App"]["forceToFinish"]();
		else if (window["tizen"])
			window["tizen"]["application"]["getCurrentApplication"]()["exit"]();
		else if (navigator["app"] && navigator["app"]["exitApp"])
			navigator["app"]["exitApp"]();
		else if (navigator["device"] && navigator["device"]["exitApp"])
			navigator["device"]["exitApp"]();
		else if (!this.is_arcade && !this.runtime.isDomFree)
			window.close();  ***<- Points here exactly***
	};
	[/code:12y266ql]

I though it got to do something with @hmmg  LayoutTransition plugin.   But then I recreated it in couple of new project, with all plugin I use with my main project (official and third party ones).  and it works fine there.

My code is very simple:

[ul]
	[li]Touch: On touched Sprite -> Browser: Close[/li]
[/ul]
nothing more. And for Third party plugins I use only two: LiteTween and LayoutTransition. But like I said it works fine in new projects, only this particular project I'm working on is affected by this.

Any thoughts?

"the character fits nicely on a 64x64 tile."

For C2 sprite sheeting on export it will be better for you to not use 64x64 textures. Use 62x62 instead and don't forget to actually put 1px empty border around your sprites.

"upper body animation in 32 directions."

You will need to rethink that. 32 directions Is a lot for plain 2d game. It will use quite a bit of memory but that's not important. Most important thing is you will need to edit them frame by frame in C2s Image Editor - hotspots, image points, collisions. It will take a LOT of time and especially patience to do that

I thought I'm gonna lose my mind while I was setting this up. C2s Image Editor is not helpful at all in doing that

https://www.scirra.com/store/royalty-free-graphics/isometric-soldier-72

Oh well... Black is probably better than nothing at all

First thing - you got a little typo on first page. Just below "CREATE A BACKUP" should be "V1.2" instead of "V1.1".

Second thing - would it be possible to do something with that black background between transitions? Change the color or put some image preferably?