docs.google.com/file/d/0B0V2EvCXNzYULTNyWkZZTWNHbXc/edit

Here is the capx where pausing does not work.

Also FYI. I removed "First Animation". "mainmenu" is the only animation in the scml so far.

wookalar

Does this work with Phonegap support?

Well if Java is not your most familiar language. Game Closure has a way to use C++ and GC uses the NDK(Native) for compiling C++ code for Android apps.

Of course maybe C++ isn't your native language either :| If it's not. Then never mind. Actually what language is your preferred?

Looking forward to it. I thought PhoneGap would have run on C++ and you were using the NDK and ODK bridge.

You mentioned last that you had good performance with PhoneGap. Is that just from careful game design and the natural PhoneGap speed on Ouya or are you using Pender?

Made it too page 3 with no reply and I'm still stuck :P

This is a bump, but I think I'm going to try another way of moving the block on a limited access. Maybe that will be easier to trying to fix what went wrong with this one :D

Alright. So I have been tinkering with the basics of trying to do a sliding tile based puzzle game. Currently it's rudementary and trying to just get the tiles sliding.

The problem is that I can't get it to work right :(

docs.google.com/file/d/0B0V2EvCXNzYUMzJYQ3FiQlZqbjg/edit

Here are the problems based on the capx

1. The tile selected slides right though other tiles 50% of the time

2. The tile moves the opposing tile out of the way 50% of the time

3. The organized tile setup goes wack at the startup

I've tried to tinker with it, but just made more of a mess :| Can anyone please help. I'll keep tinkering, but it's just not working yet.

Physics doesn't and can't use dt effectivly

The nature of Box2D is that it's performance is dependent on the binary it's running on. Which means that the amount of CPU cycles spent on the physics determine the results.(cough why cutting down the fps to a desired level can influence our logic time cough)

However Box2D has a had a few tutorials to fix the timestep for it to work across different cpu/binaries

gafferongames.com/game-physics/fix-your-timestep

unfortunantly C2 implementation lacks enough functionality exposed to be able to manually do this in an event sheet. From what I can tell :|

Yes it's doable... um I'm not an export on this however.

scirra.com/forum/flashlight-effect_topic49676.html

Just modify and edit the principles as needed. Don't use black. use a triangle sprite....

Actually I agree with the OP how it should work. Containers shold work like along the lines of a parent -> child model. However it doesn't.

Container is a collection of objects(that can't share in other containers :( ) that are related to each other. Theoritically when one object in the container get's triggered for use. All the objects in the same version should. however that doesn't seem to happen all that often either.

For now. Just continue to use PIN. Not the best, but it at least works. C2 does many things great, but it's lack of a Parent/Child and it's simple PIN behaviour are it's weakest points so far :(

Otherwise fantastic tool :)

Just as an update.

* Pause animation playback, doesn't do anything :(

* "Set playback speed ratio"(for pausing, so 0) needs to be after "set animation" or else it will error on line 1295 of the plugin

* Can there also be AnimateToKeyFrame(frameNumber). I find using Spriter to scroll a menu up and down for a controller to be really nice. Rather than using set speed ratio. Animate to frame would be way better.

* as a temporary update for Spriter into C2. You can copy and paste the SCML file into the C2/File folder. It does work. This however doesn't take into account new objects. Now I'm not sure which part is responsible the plugin add object or the plugin itself. It would be great that on startup of C2 the Spriter Plugin can go over the spriter event sheet, and images and put them where they should be.

* It would be great that Spriter Plugin handle it's own XML parsing rather require other technology. That way C2 Spriter can be moved to different platforms and not have to wait for other technology to provide the DomXMLParsing shim.

yeah. i'm glad some one at GC found a solution. Knowing the in's and out is easier to create the bridge.

I'm looking forward to seeing how GC and PhoneGap will be for Ouya come end of March and I can start testing on my own device :)

yes, still looking forward to import/export event sheets.