dissapointing android performance

240/250 and 11 what? (Sorry, have to check!)

And yes - you’re correct - the back button isn’t currently usable in .591. [import]uid: 52491 topic_id: 12129 reply_id: 57588[/import]

Sorry, the code above was to show the memory usage and texture memory usage, I put this in the enterFrame runtime event listener, so 240/350 was the memory usage and 11 was the texture memory usage.

It might just be the build i’m using is slow when pushed to android, could it be to do with using 60fps and antialias?

Glad to know about the 591 build, i have the code in place and it doesn’t work… I didn’t think there were any problems with the actual code :slight_smile: [import]uid: 72726 topic_id: 12129 reply_id: 57592[/import]

Hey Kevin,

Just to make sure we’re on the same page can you please use the following code and post results?

[lua]local function monitorMem(event)
collectgarbage(“collect”)

print( “\nMemUsage: " … (collectgarbage(“count”)/1000) … " MB”)
print("Texture Usage " … system.getInfo( “textureMemoryUsed” ) / 1000000)

return true
end

Runtime:addEventListener(“enterFrame”, monitorMem)[/lua]

Let me know results.

Peach :slight_smile: [import]uid: 52491 topic_id: 12129 reply_id: 57726[/import]