Nice, voting! :)

cesisco - would you mind pming a link to the game and capx so I could poke at it?

With how it's set up so newly received pm's are hidden in the drop down menu, pm's can sit there unnoticed. Considering how long it's been since I've sent some out, I think other people have gotten some and not realized it as well.

Could it be made so pm's are added to the number notifications in the top right corner of the page the same way that getting a — does, so it's immediately apparent you have one rather than it being hidden? Or some manner like how it was previously.

You both said you're running version 2 of android - how old are your devices? Performance gains have been dramatic in the mobile area, so even having a device that's even a year and a half old can make a big difference. Also, as I've heard android 4 got a significant html5 speed boost as well.

Can you post your games? Did you at any point add physics to your project, even if you removed it later? You can try making a backup then deleting code and sprites bit by bit to find out what's hitting the frame rate. You can also try ranma's performance tips in the tutorial section (use the search in the tutorial section for performance).

That's weird, I get the exact opposite. With my projects, preview on LAN has terrible performance compared to the exported HTML on a website (like 100 sprites at 60 fps via preview vs 400 sprites at 60 fps via export).

It is on an ipad 3 though, I wonder if that makes a difference.

You, R0J0hound, are awesome. :)

Ashley - awesome, thanks so much for implementing it!

Perhaps you should post something in the help wanted section like "will pay for cc plugin/or fix to a cc plug in."

You could try contacting people who developed previous cc plugins like rojohound or arsonide, they might be able to add a "unload from memory" action (I can't speak for them though, but even if they can't they might be able to guide you to someone else who can help).

You could also post to other forums where c++ programmers reside, and hire someone to fix the plugin for you (probably quicker/cheaper than making a whole new one).

I realize you said there isn't time for you to implement a workaround, but in case it could potentially help anyway, what I would recommend (without knowing the specifics of your project) is putting the animations in separate objects and having those objects all in a family so you have one set of code controlling them. You can then pair up those objects with the base object used for gameplay via uids or the pairer object.

Unless it would require a thousand objects or something. Then I would recommend putting multiple sets of animations in each object, but still splitting them up to reduce usage, and determining what set to use based off of variables:

Set animation to: sprite('type') & "Default"

Results in: "spritetypevariableDefault"

—

Thanks, that seems to help confirm the theory that it is in fact a problem with it going over the 2048 texture size rather than being an issue with going over the display resolution.

Ashley - Please! :D I should have added the -1's to the height as well though, as this bug can happen if the canvas is 2048 pixels tall as well.

Edit: — - err... Hmm. Have you been able to get better performance with other projects in retina mode on that device? Does that device even get affected at all by the retina setting? As mentioned, the first test is unmodified. I'm not doing anything unusual with the test, though it does wait for 30 fps to create sprites, and deletes them below 30 fps. Is your device/browser's rendering capped at 30 fps? I think I've heard of some devices doing that, though I'm not sure.

That said, your device doesn't have the weird screen size reporting issue that mine does (the ipad 3 registers it's retina display at 1024x768 even though it has 2048x1536 - that's why the -1's on ipad 3's actually shrink the texture by 2 pixels and on your device it only shrunk it by 1), I'm not sure if that would have anything to do with it, though.

Tom

Oh, I didn't realize that, thanks for clearing it up. You sure it's a good idea though? We might get people changing other people's declarations of their love for Ashley to themselves. Or something. :D