Game works fine on preview player. Bug when testing on device.
LucidFuel
Member, PRO Posts: 28
I saw a few people bring it up before. I expected it to be a bit different. However, I still have a problem.
My game is nearly complete. Just need to add, iADs and its should be good to go. However, when im testing it on my iphone. I noticed it crashed after the 2nd time you die in the game. It just freezes. I can't recreate it in the working file.
When i check the code, it's pretty clean. I bases it off something Deep blue app's created. I took the basic template and extended it with new code and add all new art work. Deep blue has a really good reputation so i'm not sure whats wrong with this app's code. The code i added was clean and and simple.
I thought game salad was great because of how easy it was to pick up and suited designers. However, my frustration is (unlike using real code) I cant exactly back track and pick up where the bugs are. Everything looks perfect.
Its a simple intriguer. 0 for starting the game. 1 for when you touch the hero and start dragging it. Then 3 for when your hero dies and the game over screen comes down and you can restart. Hitting restart obviously bring the game back to 0. This is the part where it seems to have problems on my iphone.
It works fine the first time. It only crashes on the second time. Not sure where to begin to debug this bug on devices. Not prepared to pay for premium support, since when i just upgraded to pro. I thought there was going to be a upgrade in support. Then i realized theres no real difference between pro and basic support. And premium wasn't pro.
Where do i start to debug this one bug? The game is nearly perfect other than this one major glitch on the device.
Comments
Hmm, might contact the guy from Deep Blue apps. Really hard to say without having the code to look at.
You're making a lot of assumptions:
If the template you purchased worked fine, then something you added is causing the crash. Time to start debugging! Without Log Debugging support in an adhoc build, you'll need to be a bit more clever with your use of Display Text behaviors and what I call "adhoc log debugging," where you "log" data to a table and then use Display Text behaviors to display that data live.
There may be an attribute you've forgotten to reset if it's working once but not after restarting.
If you don't know where to start, but you have some idea about where the crash occurs (e.g. on the second scene after the start button disappears but before the first obstacle) then put your log behaviors before and after that and start narrowing down until you find the cause. Debugging is a slow process... I think that's probably true in any programming language.
And generally, template sellers are the ones to contact for support questions.
New to GameSalad? (FAQs) | Tutorials | Templates | Greenleaf Games | Educator & Certified GameSalad User
A Pro license includes priority technical support. From http://gamesalad.com/creator/pricing:
"As a Professional GameSalad Developer, you also receive priority technical support. Priority technical support requests will receive an initial response within 24 hours on business days, and additional assistance troubleshooting projects."
Were you not aware of this when you purchased a Pro license?
New to GameSalad? (FAQs) | Tutorials | Templates | Greenleaf Games | Educator & Certified GameSalad User
Yes I was aware. However, if you look closely.
>
>
>
>
>
Basically I can ask about gamesalad the actual program. But the premium is for the actual game trouble shooting at $200 each issue. Which to be honest, is pretty fair in most cases. Because if i had a more complex game. It would be very much worth it. But for a simple game. I'll see if theres a work around. There not pages and pages of code and theirs a limited number of actors. However, push comes to shove. Sometimes you just have to eat the frog as they say.
Im going to check with the guys who came up with the base code. I'm hoping they may have a solution or maybe a more cost effective option for help trouble shooting.
In objective C i can code in parts i want to get info from. I dont really have that option in GS that i know of. I'll look into the adhoc option as well. I'll try trouble shooting it more later.
Found the issue. When i changed the game over screen, i miscalculated one of the expressions when compared to the graphics. The GS testing seemed to be more forgiving then the real thing.
But... it's FIXED! hehe