@steve86 said:
I´m still taken about how this passed QA. I understand its impossible for the internal team to caught all the bugs, and sometimes need our help. But they just need to work with the client for 30 minutes to realize this is not a stable release candidate.
It took me around 30-40 hrs of usage to get any crash from this build. Guess every individuals milage may vary.
As we seem to have big issues with stable builds and creator automaticly locks you out of using a previous version when opened and saved in a higher version number. Can you not provide a quick program that will "rewind" projects. In still running on 0.12.20 because of what happened when you went from a stable 0.11 to a "stable" 0.12 and then pulled it back off the shelf when you realised it wasnt stable at all. Now we have jumped from 0.12 to 0.13 with the same "not so stable" release. The issue us devs have is you tell us its stable and its not (for many reasons im sure, but I assume its a not so thorough QA system in place) then you push a notifaction to us when we login on our current stable version and encourage us to upgrade to the new version. We click yes (why wouldnt we, you are releasing a new "stable" version with new features) and then save our project to find out we now have a bug (and serious bugs at that) and we cant rewind the project as you lock us out of it.
A few threads have been opened and there are ways to rewind the projects by changing and deleting sections in the xml files of the projects, but I wouldnt recomend doing this to anyone as its quite complex for many users. Can you guys not quickly knock up a rewind program to allow us to covert projects back in case of such QA failures and when we find out that the "stable" version is once again not so stable afterall?
I love GameSalad and I use it daily upto 12 hours a day for my job but I fear every new release as it always turns up a new bug and then takes so long to fix. I understand these things take time to fix but as a end user, we shouldn't have access to these releases. They should stay RC until tested and if you do make a mistake and release a unstable version by accident (we all make mistakes) allow us to roll back our projects easily so we can continue to use the last stable version while you fix the bugs.
Im confident that you boys can knock up a XML editor in a day that will roll back any project to version. Lets make it happen and bring back some confidence in the product we are all paying for.
I spent most to of the day fixing Mac crashes and we are going to put out an Release Candidate build in about an hour or two. Please report any crash that you find help us stabilize the build. If all goes well we could have a more stable build out next week.
Braydon_SFXMember, Sous Chef, Bowlboy SidekickPosts: 9,273
@BlackCloakGS said:
I spent most to of the day fixing Mac crashes and we are going to put out an Release Candidate build in about an hour or two. Please report any crash that you find help us stabilize the build. If all goes well we could have a more stable build out next week.
@BlackCloakGS said:
I spent most to of the day fixing Mac crashes and we are going to put out an Release Candidate build in about an hour or two. Please report any crash that you find help us stabilize the build. If all goes well we could have a more stable build out next week.
Thank you for your effort. I appreciate the hard work. I will keep sending crash reports.
The new RC is up. Please give it a try and let me know what crashes still need fixed. If you do get a case please click the send button on the crash dialog so we get the crash report.
Comments
It took me around 30-40 hrs of usage to get any crash from this build. Guess every individuals milage may vary.
Follow us: Twitter - Website
@BlackCloakGS
As we seem to have big issues with stable builds and creator automaticly locks you out of using a previous version when opened and saved in a higher version number. Can you not provide a quick program that will "rewind" projects. In still running on 0.12.20 because of what happened when you went from a stable 0.11 to a "stable" 0.12 and then pulled it back off the shelf when you realised it wasnt stable at all. Now we have jumped from 0.12 to 0.13 with the same "not so stable" release. The issue us devs have is you tell us its stable and its not (for many reasons im sure, but I assume its a not so thorough QA system in place) then you push a notifaction to us when we login on our current stable version and encourage us to upgrade to the new version. We click yes (why wouldnt we, you are releasing a new "stable" version with new features) and then save our project to find out we now have a bug (and serious bugs at that) and we cant rewind the project as you lock us out of it.
A few threads have been opened and there are ways to rewind the projects by changing and deleting sections in the xml files of the projects, but I wouldnt recomend doing this to anyone as its quite complex for many users. Can you guys not quickly knock up a rewind program to allow us to covert projects back in case of such QA failures and when we find out that the "stable" version is once again not so stable afterall?
I love GameSalad and I use it daily upto 12 hours a day for my job but I fear every new release as it always turns up a new bug and then takes so long to fix. I understand these things take time to fix but as a end user, we shouldn't have access to these releases. They should stay RC until tested and if you do make a mistake and release a unstable version by accident (we all make mistakes) allow us to roll back our projects easily so we can continue to use the last stable version while you fix the bugs.
Im confident that you boys can knock up a XML editor in a day that will roll back any project to version. Lets make it happen and bring back some confidence in the product we are all paying for.
Thank you in advance.
Damien
I spent most to of the day fixing Mac crashes and we are going to put out an Release Candidate build in about an hour or two. Please report any crash that you find help us stabilize the build. If all goes well we could have a more stable build out next week.
Thanks for your dedication, Alan!
My GameSalad Academy Courses! ◦ Check out my quality templates! ◦ Add me on Skype: braydon_sfx
Also if creator ask you if you want to send the crash report please say yes.
Thank you for your effort. I appreciate the hard work. I will keep sending crash reports.
The new RC is up. Please give it a try and let me know what crashes still need fixed. If you do get a case please click the send button on the crash dialog so we get the crash report.
Keep up the great work!
Any updates on using the new RC is it more stable ???