100 Chambers (re-done in 3.0)

Progress through lots of chambers filled with puzzles, brainteasers and minigames in this “Escape the Room” adventure!



Android - Google Play Store:
https://play.google.com/store/apps/details?id=de.codinsoft.ohChambers

Android - Google Play Store - Free with Ads:
https://play.google.com/store/apps/details?id=de.codinsoft.ohChambersFree

Android - Amazon App Store:
http://amazon.com/gp/mas/dl/android?p=de.codinsoft.ohChambers

iOS - Free with iAds:
https://itunes.apple.com/us/app/100-chambers-free/id560509503?ls=1

iOS - Paid:
https://itunes.apple.com/us/app/100-chambers/id554305803?ls=1

Thanks for reporting your experience with 3.0. It's encouraging to hear that even with some unresolved and unfinished work, we're seeing multiple games reach Google Play and the App Store just in the past couple weeks.

It's also interesting that this game has no issues with the reference table entries that mguido's game did, despite this one having twice the actor count and many more resources overall than his.

It's also interesting that this game has no issues with the reference table entries that mguido's game did, despite this one having twice the actor count and many more resources overall than his.

Grrrrr - that's exactly what I was thinking when I was reading these numbers. Still having issues on android with resources on my game I think I'll try and do some more testing.

It's also interesting that this game has no issues with the reference table entries that mguido's game did, despite this one having twice the actor count and many more resources overall than his.

The first version was converted from 2.x but didn't even start under Android due to a heap memory overflow (although it built successfully). So the decision was made to re-create everything from scratch in 3.0 to have a clean setup.

With all the existing assets it took only a few days and now it's running smooth

Awesome! How does performance compare with the previous version?

Awesome! How does performance compare with the previous version?

No performance/memory issues so far. Even on iPod4 it's running fine now (it used to crash nearly instantly which is why it got some bad reviews in the AppStore).

I think this is mainly because of 2 things:

1. The new atlas system which allows every scene to have its own atlas, holding just the stuff it needs in memory.
2. The reduced size of the GFX assets due to pngquant.

Apple approved everything in ~12 days.
Amazon took ~4 days.

Sales on Android are going smooth with already a few hundred in Google's Play Store

EDIT: I updated the initial post with the store links.

Jens, did you do ANYTHING AT ALL differently that may have fixed the Android crash as you were rebuilding your game? I'm close to done rebuilding mine in 3.0 from scratch and just tested on my Nexus 7 and it's crashing again from the same memory overflow error. Of course, it was working not long ago, but I've added a lot of resources in the past few days.

Jens, did you do ANYTHING AT ALL differently that may have fixed the Android crash as you were rebuilding your game? I'm close to done rebuilding mine in 3.0 from scratch and just tested on my Nexus 7 and it's crashing again from the same memory overflow error. Of course, it was working not long ago, but I've added a lot of resources in the past few days.

There are 2 differences that come to my mind:

• The attribute type called "game attribute" wasn't available for scenes back then (it was re-implemented recently, after some months) - so a global string was used to keep track of the current level
• The number of overall sound effects was reduced
  

IIRC the heap overflow on Android happened during the upfront loading of sound files. Reducing them could be worth a try.

Yeah, it was the number of sounds I had labeled as sound effects, instead of removing them I changed some to music and that got it working again. So when you removed those sound effects that must've been the fix for you

Great that you figured it out! I hope your game is back on track now
In case it allays your pain a bit: The error drove me also nuts and re-creating everything (to see at which point it might break) was a desperate last option. I had no idea why it worked

Great debugging work, folks!

I know performance/memory limits differ by the types of devices we use.

But can anyone give us a rough idea of how many pieces of music/sound effects you have in your game and roughly at what point (count of music pieces) that the game breaks (such that it necessitates switching sound effect to music). I also assume this is dependent on the length of the sound effect pieces. Just a rough number please, anyone?

Right now my music to sound effect count is 21 to 48. Before changing them around it was 7 to 62. I'm not exactly sure where the threshold is in there, but it's obviously somewhere in between there.

Updated with new levels and optimized for iPhone 5.
It's also available now in the Opera App Store.