|
|
Post by beckami on Aug 9, 2008 8:21:37 GMT -5
I upgraded to 1.0.1.0.1 and while I haven't experienced any crashes yet, I am incredibly annoyed with how the game is behaving now. I consistently get the low memory message, even if it is the first and only app I have running after turning my phone on (16gig 3G). Also, no matter where I'm at in the game when I quit, I always come back to the wild fire puzzle when I load the game. This skill now shows up 4 times in my list of skills. It is accurately saving my progress besides that, though. I don't know... for an update that supposedly fixed so many bugs, it certainly seems to be working more poorly.
|
|
|
|
Post by Danielle Cassley on Aug 10, 2008 2:05:28 GMT -5
The low memory message is just a note to let you know that the app may get closed by the iphone so that it can regain memory. Things in the background (email, updates, network connections) change the amount of memory available. When we get low memory warnings we save your game so that you do not lose data in the case that the iphone takes over and stops the game.
As for your game repeatedly starting in th puzzle that is crazy and I havent heard that before!!! If you PM me with more details maybe I can help out!
|
|
|
|
Post by mrsmiley on Aug 10, 2008 18:30:18 GMT -5
It's a shame that AF uses so much RAM, especially considering how little the iPhone/iPods have. I'm curious as to why this happens so much with AF, but not with other games that use full graphics engines like Monkey Ball or Crash. It's still great that you have it save the game before it crashes, but it is kinda annoying that it happens so often. :S
|
|
|
|
Post by ebronte76 on Aug 12, 2008 10:40:02 GMT -5
I agree. I never get memory errors with any other app, only AF. And only since the last update. It never actually crashes but I get a warning message pretty much every time I start mining. 16 gb 3G 1 week old iPhone.
|
|
|
|
Post by mlos on Aug 12, 2008 12:45:51 GMT -5
I can live with the crashes, as they are few and far between, and I have yet to lose any data. When comparing to Monkey Ball or Crash, keep in mind that AF does not have a multi-million dollar game studio behind it. For what the game is, and the potential it holds, I can deal.
|
|
|
|
Post by mrsmiley on Aug 12, 2008 13:33:39 GMT -5
I can live with the crashes, as they are few and far between, and I have yet to lose any data. When comparing to Monkey Ball or Crash, keep in mind that AF does not have a multi-million dollar game studio behind it. For what the game is, and the potential it holds, I can deal. Excellent point. This is just two people! That leads to another question... will a game studio get smart and pick up what these 2 geniuses are doing? Would be awesome to see them make some $$$ of this, and get a larger dev team behind them!  |
|
|
|
Post by theconfuzed1 on Aug 15, 2008 3:57:53 GMT -5
Here's a thought...
The low memory error triggers a save, which is good, but no one yet seems to have actually experienced a low memory crash.
Would it make sense to simply have whatever triggers the error, just trigger the save without displaying the error?
That way, the game is saved, which is the objective, but the end user doesn't have to interact directly with it.
|
|
