Thank you for all your feedback on the 0.9.7 release. We were really excited to bring new features like iOS keyboard, device time, and the de-bugger to our community of users.
However, we are aware that with the 0.9.7 release we unfortunately introduced a serious issue in regard to Game Engine Memory within the GameSalad Viewer.
Here is how we defined this issue internally:
GS Viewer: Game Engine memory constantly increases with each scene change
Basically, projects will have a memory increase every time a scene change happens (size of increase depends on how massive the project is). This means that eventually the project could crash on the device due to lack of memory.
This is a critical bug and we have been working hard to resolve this issue immediately. We apologize and completely understand your frustration.
We are happy to announce that we will be releasing a fix for the bug TODAY with a 0.9.71 release.
Along with this release, we will also be integrating new templates (iOS keyboard and device clock) into Creator for your use.
MagoNicolas said: That Was Fast! Congratulations! this is how this should work for this kind of bugs
agree... seems like the GS engine is finally started cranking, keep up the momentum guys. sooner or later you'll have your first news mention of a 14 year old becoming a millionare using GS, and the rest will be history.
I tested a scene in 9.6 memory usage 47mb then in 9.7 memory usage 57mb now with 9.7.1 it 70mb!!!!!! its not leaking memory but the memory per scene has gone up so much! how high can it go before it crashes my iPhone 4?
marcgreiff said: There is an unquestionable memory increase and has grinned my project to a halt. If anyone one out there knows how to revert a project that was originally created in 0.9.6, then saved in 0.9.7, back to 0.9.6 please let me know (marcgreiffdev@gmail.com). Any help, from the dev team or gs community would be greatly appreciated. I am on a tight deadline for this particular project.
Thanks in advanced
It won't help you, the publishing servers will have all be undated to the 0.9.7 version.
while the memory fix is not perfect from any stretch of the imagination,you have made a difference,we are back to square one before 0.9.7 update.so well done for fixing the ram issue which you caused in the first place.we can only go up from here.i think woop woop.
Someone know if the memory leak only appears when you created a hole new project with Gamesalad 0.9.7 or if this also happen if you only make a little change with the project in 0.9.7 but you worked like 99 % in 0.9.6?
gameARN said: Someone know if the memory leak only appears when you created a hole new project with Gamesalad 0.9.7 or if this also happen if you only make a little change with the project in 0.9.7 but you worked like 99 % in 0.9.6?
It will still be the same problem as the whole game engine is replaced with an update. your project file is just a set of instructions telling the engine what to do.
I was looking at the release notes, and I saw this: "Resetting the game multiple times will now continue to generate random numbers"
Does this mean the random function will make a new random number each time (I assume with the clock) rather than following the same sequence each time? If so, this seems like big news. If I'm wrong, someone please correct me, but I wanted to bring that to everyone's attention.
That's not a debugger, it's just a log viewer. A debugger would let us set breakpoints, inspect variables, etc.
Don't get me wrong, the log viewer is a nice addition, but it's not a "feature" it's just a log viewer. Handy, but not a debugger. A real debugger would be really nice!
Asymptoteell said: I was looking at the release notes, and I saw this: "Resetting the game multiple times will now continue to generate random numbers"
Does this mean the random function will make a new random number each time (I assume with the clock) rather than following the same sequence each time? If so, this seems like big news. If I'm wrong, someone please correct me, but I wanted to bring that to everyone's attention.
Asymptoteell
I would like the option of seeding the random number generator with the system clock or with my own seed. Sometimes I want the behavior of a deterministic random pattern and sometimes I want a truly random pattern. Seeding with my own value lets me create the same play experience each time. Seeding with the clock lets the system give the illusion of true randomness.
GS Devs: Just add a behavior: RandSeed that takes one parameter and if RandSeed is not present before the first time random() is called then fall back on the system clock for the seed. Isn't this programming 101 stuff?
Photics said: Wow... it's too neat. I thought there would be like a unix timestamp. Instead, it's broken down by category. That's useful for certain things, but that makes things harder for something like farmville. If I want to check that 60 minutes has past, that means I have to check for the minutes, hours, days and years to ensure a proper value.
I strangely agree. GS, could you add one more param please to the Clock attribute? EpochSeconds? It's handy sometimes to just have the whole "time" value summed up in one number.
RKS said: I think it would be great to have the text boxes not pop up and take up the whole screen, just a normal text box please? PS: @Calvin to spice up your signature with custom text links, do this (a href="http://link.com") Custom text here (a) but make sure you change ( to < or ) to >. I will turn out like: _______ RKS Games GSBar!
this is really unacceptable , why the performance got that slow , at least i lost 10 fps after updating to 0.9.7 , start getting real mad now after waiting over 2 months for fixes , and now performance major drop down
hich4m said: this is really unacceptable , why the performance got that slow , at least i lost 10 fps after updating to 0.9.7 , start getting real mad now after waiting over 2 months for fixes , and now performance major drop down
Yep, it's stopping me making any updates as I'm not publishing versions that perform a lot worse than the previous.
Did this not show up in testing? You would think so, and it was somehow deemed acceptable?
I think this version should be rolled back to 0.9.6 until they actually get it to work.
Comments
I guess i'll wait until we get this fix for me to keep on working and take the afternoon. I'm off to the Golf tee everyone. Happy coding
Shadows Peak is an atmospheric psychological horror that explores the dark side of a player.
Send and Receive Data using your own Server Tutorial! | Vote for A Long Way Home on Steam Greenlight! | Ten Years Left
The 0.9.71 patch is now live. There is really only one release note for the patch, posted below:
Fixed an issue that was causing the GS Viewer to stack memory with a change of each scene
Thanks to everyone for their patience and understanding while we got this fix out the door!
--Yodapollo
Roy.
J
then in 9.7 memory usage 57mb
now with 9.7.1 it 70mb!!!!!!
its not leaking memory but the memory per scene has gone up so much!
how high can it go before it crashes my iPhone 4?
woop woop.
"Resetting the game multiple times will now continue to generate random numbers"
Does this mean the random function will make a new random number each time (I assume with the clock) rather than following the same sequence each time? If so, this seems like big news. If I'm wrong, someone please correct me, but I wanted to bring that to everyone's attention.
Asymptoteell
Don't get me wrong, the log viewer is a nice addition, but it's not a "feature" it's just a log viewer. Handy, but not a debugger. A real debugger would be really nice!
GS Devs: Just add a behavior: RandSeed that takes one parameter and if RandSeed is not present before the first time random() is called then fall back on the system clock for the seed. Isn't this programming 101 stuff?
PERFORMANCE! PERFORMANCE! PERFORMANCE!
Please focus on that.
I still has a question, is there any way to stop the player cheats when I use the clock
Calvin
Did this not show up in testing? You would think so, and it was somehow deemed acceptable?
I think this version should be rolled back to 0.9.6 until they actually get it to work.