Arrays Don't like Negative Numbers
In editor the cocos2D graphics engine is active. The entire canvas is the live game engine. Plus every action you take is being saved which are constant read/writes.
These two things affect battery life.
@Murtaza You can stall the cocos2D graphics engine. It doesn't need to constantly refresh at 60fps when nothing is happening. That's one of the key design points of its actions based nature, and the same reason the early versions didn't have a traditional game loop.
Oh, why didn't we think of that before! You're a genius! Thanks. You've single handedly solved all of our problems.
Sarcasm noted. Invert this approach to stop rendering when it's not necessary, see Brad Larson's answer:
@Deeeds if you’re unhappy with our progress, ask Apple for a refund. We’re trying our best and it doesn’t seem to be good enough for you and that’s okay. We’ve been pretty attentive and patient with your arrogance and bullying but unfortunately, you’ve taken it too far and we’re putting a stop to it. Future posts where we don’t appreciate your tone will be removed.
@Hamed "arrogance and bullying"...
Where's the bullying?
Who feels bullied?
I am prone to arrogance. Not going to contest that. But bullying is something else, entirely. Please share an example. I'm very curious.
Aidan Oxley last edited by Aidan Oxley
@Deeeds You’re making the devs feel bullied, the way you keep judging this app and they way they run and make it. You’re the first person to ever do this (at least on the forums). It’s like you know better, even though they’ve been working on this for over 6 years.
@iTap-Development Well played, maestro!
Thecheater887 last edited by
@Aidan-Oxley I used to do that. Might check my post history, some pretty bad things are probably on there. Four times as much on the old forum, I'm betting, too.
Then I started programming. I need to invest in Raid library.
Anyways, I understand where @Deeeds is coming from, his methods match how mine used to be, and probably still are - very defensive and willing to push back.
That being said, no three-man team, all coders mind you, that I know could ever pull this off. Period. I'm rather surprised they made it this far, and root on any and all progress they make.
In fact, if I ever manage to get my pea brain to understand C++ or Swift and get a (decent) Mac, I may apply (as a volunteer initially) to help them out.
(Speaking of which @Murtaza, are you guys open to third party application development? I'm interested in trying my luck at a windows player, asset manager, screen mirror, game analytics, or anything else that may be of some help if apple and you guys are open to it, or have an API until I get a decent Mac.)
I do have to side with the @administrators, though. I'm not quite certain how it descends to it, but the bicker and banter isn't helping anyone. The more time they spend here with fire extinguishers, the less time they can spend there with flashlights and bug zappers.
TL;DR: When a community and team are this small, it's a LOT harder to manage and expand the people and the product, and that's before the blood moon rises.
Sorry guys, had to have my daily dose of nosy :)