Did you set the seamless mode in the tilemap setting?

No event picks any jullet for the changing direction. So all are affected.

I suggests to set the angle in the same event the bullet is created.

You can also have a loader layout, which will appear when the assets it contains are loaded

"Cocoonjs is a clunky exporter that scirra cannot control in any way possible"

not counting memory management issues, this clunky exporter is still better than Crosswalk. Yes or No?

I think it is unstable on some devices, and if we are going to not count the memory management issue, we might as well not talk about the performances issues of crosswalk, except for small games.

At the end cocoonjs is a fine product by itself, but it should not be advertised as a c2 exporter, which is what depreciating it means

Ps: also i think ludei wants to make cocoonjs compatible with the html5 export itself too, and since cocoonjs should support html5 apsp, and not the other way around, it is fine.

"Maybe giving the open source plugin more attention and release an official CocoonJS plugin for C2 with a small support is still the best option?"

Seems familiar... oh right, there was an official cocoonJS plugin, but ludei did not a great job at keeping scirra knowing informations to maintain it properly

Then ashley gave it to ludei so they do it themselves correctly, they released it as an open source plug in so they won t have to do it.

It was also a broken plugin when it became open source.

Cocoonjs is a clunky exporter that scirra cannot control in any way possible, so they shpould not support it in any way, also it is not really that compatible with c2, at the end, depreciating it is the best thing they could have done, it is clunky, if users wants to use it, sure, they can, but this is a responsability scirra should not take since if cocoonjs fails once again, then scirra will be hurt by it another time, with no control over it.

It is just too big of a risk, and a decision that was not immature, they kept supporting it for years, always dissapointing, crosswalks and ejecta were added just to have a valid alternative to cocoonjs, but right now cocoonjs is still preferred over them (which also implies small games are mostly made, since the memory management of c2 is incompatible with cocoonjs).

At the end, if you have problem with cocoonjs, you may want to talk to ludei directly, it is them that maintain the wrapper.scirra cannot do anything nor guarantee it will work, only for that it should not be listed inside the exporters.

However, it should not be completely dropped (it is not completely dropped here so it is ok)

Edit:since this topic is for people wanting it back, It might not have been wise to post here as the post count would increase, if this post disturbs someone, I can delete it.

— I think you can still export to cocoonjs using the beta, it is a depreciated exporter, which means it is accesible via a right click on the exporter list.

Phonegap will be nice with ios8 and android L, not before, for now, we have to rely on crosswalk, cocoonjs (still working), and ejecta

Not that stable, not compatible with c2 memory management, not fully compatible wit some of c2 basic features, conflicts between scirra and ludei that finally lead to have the community itself take care of the plugin since ludei did not enough work from their side, better exporter for android, phonegap that will take the lead at the end for both iOS and Android, the surprising popularity of cocoonjs despite the fact it is kind of unstable, that updates of cocoonjs tended to be plain broken, and that scirra had to endure the support to their user since they were proposing it.

Now scirra will not have to take responsability if it is broken once again for a long time period.

I think that sums up it partially.

The thing is you are setting some " around the expression's value

It does not have a timeline, but you can mesure the time and use timers on objects, I don t know if that is enough for what you want though.

I would say the free edition may be enough to try things out

Also I think there exist a timeline plugin somewhere in the forums, but not sure what it actually does.

The statement is correct, the event run, on all selected (0) instances, but it runs

I wonder, maybe using timescale*player.dt/dt would work?

I could be wrong, but it seems like C2 is now at a turning point, features are working pretty nicely, the exporters aren't as big of an issue as before (mainly because alternatives to cocoonJS exists), it seems more like now is the time to improve what has been done and also improve the IDE itself.

My personnal suggestions:

-The image editor would like a little more work on it

-Even though I know it will not be done, the ability to change the framerate is still an important feature

-array and dictionnary behavior, as well as events sheets for the objects themselves rather than the layouts (not nessecary, but nothing is really needed when you think about it, it is just really helpful to have, and that could be a great help for new users)

-depreciating cocoonJS, and working on the functionnalities for ejecta, crosswalk, phonegap, also make the box2D physics engine uses it's full potential, since I think it is partially nerfed because of the cocoonJS physics engine, which is really not acceptable

-the arcade, right now it is just hurting this website!

-If possible, doing a node webkit fix for the problematics OS, I know it is not your job, but it is directly included inside C2 itself and on the front page of the site so it should work.

-theorycally an official wiki, could be nice to have, since forum topics can be lost in the crowd, and tutorial are not in the community edit spirit

-other things that this thread highlighted

-having the known issues listed inside the manual, I am not sure I have saw the family+container issue listed somewhere in the manual for example.

-I think the facebook plugin is not up to date.

Just suggestions of course.