10.2 Beta, what's going on???
TimBOSSDev
Member Posts: 44
Hi there,
I developed a music app a long long time ago, and because of the app's overuse of RAM (>300MB) I waited and didn't publish my game to the store... I even sent it in and rejected it 2 times because It just took too long to load (around 40 seconds) and then after a few minutes of going crazy on the app (playing all sounds, tapping all keys, etc) it used to crash. I thought it would be a good idea to wait and see what happens with the new Lua engine and hoping to have my app released soon. So many of my friends and fans are now disappointed by this delay It's a really really nice app; I could show a video if anyone wants, but unfortunately no one was able to help me fix it and after months of waiting... a version of GS (10.2) that was just released has completely ruined the app. It now loads for around 18 seconds and into loading, it just crashes right away before even the intro music comes on.... So is GameSalad truly upgrading or downgrading?
Someone mentioned that it could be poor coding... well if it was due to poor coding, it wouldn't have worked before, but it did and now it just completely crashes. So at this point, fellow GS users, I have no idea what I should do I tried optimizing the images, the sounds, the code, the attributes, art preload, so on and so forth.... but it's actually only getting worse if not stayed the same. I would really really be appreciative of some feedback on this, especially from the engineers of this amazing software, which I only wish was upgrading earlier than it is, or perhaps give some hope to users, which is what I see a lack in. Sorry if I bore you through reading this rant/text but I just wanted to let some fellow GS users know about my feedback and ask for others to give back some feedback on this.
Thanks, I would appreciate it
I developed a music app a long long time ago, and because of the app's overuse of RAM (>300MB) I waited and didn't publish my game to the store... I even sent it in and rejected it 2 times because It just took too long to load (around 40 seconds) and then after a few minutes of going crazy on the app (playing all sounds, tapping all keys, etc) it used to crash. I thought it would be a good idea to wait and see what happens with the new Lua engine and hoping to have my app released soon. So many of my friends and fans are now disappointed by this delay It's a really really nice app; I could show a video if anyone wants, but unfortunately no one was able to help me fix it and after months of waiting... a version of GS (10.2) that was just released has completely ruined the app. It now loads for around 18 seconds and into loading, it just crashes right away before even the intro music comes on.... So is GameSalad truly upgrading or downgrading?
Someone mentioned that it could be poor coding... well if it was due to poor coding, it wouldn't have worked before, but it did and now it just completely crashes. So at this point, fellow GS users, I have no idea what I should do I tried optimizing the images, the sounds, the code, the attributes, art preload, so on and so forth.... but it's actually only getting worse if not stayed the same. I would really really be appreciative of some feedback on this, especially from the engineers of this amazing software, which I only wish was upgrading earlier than it is, or perhaps give some hope to users, which is what I see a lack in. Sorry if I bore you through reading this rant/text but I just wanted to let some fellow GS users know about my feedback and ask for others to give back some feedback on this.
Thanks, I would appreciate it
Comments
Send and Receive Data using your own Server Tutorial! | Vote for A Long Way Home on Steam Greenlight! | Ten Years Left
The improvements to load times have come at the expense of an increase in memory. if you experienced high memory usage with your app previously, then chances are, with the 10.2 update, your project is now maxing out the memory on the device, and crashing.
Its been acknowledged by the GS team as an issue... but its also not a bug as such, as it was a calculated decision, to trade memory usage for faster load times. Theres been mention of looking at it again, to see if they can improve/reduce the memory footprint, but as you know by now... could be a while before you see anything.