|
Post by Cory Trese on Jan 15, 2013 1:30:54 GMT -5
I've gotten two e-mails about problems with the "Ghost Ship" skirmish level. The report is that the game crashes after beating the level. I've played through 3 times with 3 different squads on three different devices and ... no crash Can any random TA player rip through that level and see if Victory works for you?
|
|
|
Post by overseer on Jan 15, 2013 2:58:04 GMT -5
victory ... I played it several times and it may mean nothing but if you move all your TKs into the squares and quickly press 'turn' without waiting for the victory screen the game sorta trips out but my device didnt crash don't know if that would contribute to a crash event on some device? but that's the only thing I could get to happen out of the ordinary.
|
|
|
Post by vindalloo on Jan 15, 2013 3:05:58 GMT -5
no probs at all!
|
|
bobsoup
Exemplar
[ Elite Supporter ]
Posts: 453
|
Post by bobsoup on Jan 15, 2013 12:34:36 GMT -5
Works on galaxy ii
|
|
|
Post by slayernz on Jan 15, 2013 17:28:56 GMT -5
Finished it about 5 times successfully on the bus ride into the office. Didn't realise you wanted me to check it so seeing this was an added bonus. I've got it down to 7 turns - can't seem to get it any faster than that.
|
|
|
Post by Cory Trese on Jan 15, 2013 21:57:50 GMT -5
The concerned player reported that the "Victory" button crashes, but on further investigation it looks like it may be related to some type of Motorola issue.
Still investigating, hard to do without the ability to respond to the crash reports!
|
|
bobsoup
Exemplar
[ Elite Supporter ]
Posts: 453
|
Post by bobsoup on Jan 15, 2013 22:30:27 GMT -5
What does he mean by crash? Is it something he can replicate?
I've noticed sometimes when I get a text message or notification it freezes TA for a minute or so- just when I'm about to give up it comes back... Doesn't happen everytime or even often but it happens occasionally and game does continue eventually. Could same thing have happened to him?
|
|
|
Post by slayernz on Jan 15, 2013 23:38:56 GMT -5
The only time recently that I had a "force close" was when I was in the middle of a game and someone had the gall to PHONE me ... you know, actually CALL me! sheesh, it was as if I were carrying around a phone or something ridiculous like that.
Anyway, I got the dreaded Force Close (which I acknowledged to get to the phone call). As soon as the call ended though, the phone took me straight back into the game and turn (not even presenting me with a "Resume" prompt). It was as though it didn't crash.
Not that this story helps with the problem above. Man, I think it was talking about being a 4,000 year old captain that has made me ramble on with stories .....
|
|
|
Post by Cory Trese on Jan 15, 2013 23:50:36 GMT -5
Android will FC any application that takes too long to get out of the way of a phone call. This might be a performance issue in saving the game state to a file for resuming later.
We're storing it out to a temporary file so that, like Trade Exchanges in Star Traders, the TA game will last across reboots and Android application termination.
I suspect the game terminated (FC) during the phone call (performance) but was never cleared from phone memory, so it came right back to the map.
|
|
|
Post by slayernz on Jan 16, 2013 0:08:06 GMT -5
Yeah I guessed that too - was pleased at the result.
|
|
|
Post by overseer on Jan 16, 2013 0:22:19 GMT -5
ok I did get it to crash (force close) as I eluded to if you mash on the end turn button after the last TK is in the orange the loop comes undone and FC
|
|
|
Post by Cory Trese on Jan 16, 2013 0:33:23 GMT -5
ok I did get it to crash (force close) as I eluded to if you mash on the end turn button after the last TK is in the orange the loop comes undone and FC Interesting. The crash report comes from the Vae Victus button. I will investigate button mashing issues in TA, great point.
|
|
|
Post by overseer on Jan 16, 2013 0:37:46 GMT -5
when you have mashed turn button and the loop catches up and it displays vae victus button when you press it then you get the FC the fatal button combo ends with the vae victus button. I'm thinking device lag is a big faxtor because it seems the end turn button and the victory button are pretty close to on top of each other on my screen .would that condition also put the victory button the last reported in a end turn button tapping?
|
|
|
Post by Cory Trese on Jan 16, 2013 1:04:30 GMT -5
Problem in the code is probably that the buttons are accepting input while the SurfaceView (map thing) isn't ready for additional commands. Shouldn't be too hard to fix (so I say now.)
|
|
|
Post by overseer on Jan 16, 2013 1:15:54 GMT -5
as long as you don't push end turn button it runs like a top! (captain to troopers) : just get in the damn shuttle and don't touch nuthin! I can't take you guys anywhere!
|
|