|
|
Post by starfixer on Jul 10, 2012 16:23:57 GMT -5
When I press the surveilence/blockade button repedetly, the game wil freeze as I countinue mashing and eventually all the water fuel will disappear, all the noifications will go up, all the time will pass, and all the encounters willhappen at once. Well I mashed surveilence too many times to th poin where I not only lost all my water fuel but my moral went down to the point where I had mutiny. I choose to "fight", and then another mutiny came up right after! 10 mutinies in a row and by the time mutiny signs stopped showing up one rght after the other I had -6 health! I figured it was a glitch as I wasn't dead, so I started to go to the nearest planet to heal myself. But on the way, I had an enounter, pressed ignore, and right after it said I had been killed! This has been the second time I've died because of repeted mutiny signs and negative health. Please fix.
|
|
BlastGT1
Templar
[ Heroes of Steel Supporter ]
Turning ships into shards with Alchemy
Posts: 920 
|
Post by BlastGT1 on Jul 10, 2012 19:38:25 GMT -5
This is your punishment from the Q for creating a rift in the time-space continuum.
Actually, try slowing down, then you won't die from going to hyperspeed without plotting a course first, Han Solo. :-D
Launched from Torpedo Bay 1 of my MetroFLASHed HTC Droid Incredible
|
|
|
|
Post by fallen on Jul 10, 2012 21:31:03 GMT -5
starfixer - the best thing is to stop mashing so much. It is important to wait for the game feedback to occur and deal with each item. Pick a nice, reasonable, rhythm to push the button and stop every couple of seconds to see if there is any feedback that you need to handle (such as a mutiny). Also, this is not a good strategy, btw. I'm not marking this in as a bug.
|
|
|
|
Post by starfixer on Jul 10, 2012 22:04:16 GMT -5
The thing is though,I hae a ship wih 228 hold (with upgrades). When I go to blockade, it'll take an exruciatingly long time if I blockade a few at a time, as oppoed to mashing which still takes a while.
|
|
|
|
Post by Cory Trese on Jul 10, 2012 22:09:18 GMT -5
The thing is though,I hae a ship wih 228 hold (with upgrades). When I go to blockade, it'll take an exruciatingly long time if I blockade a few at a time, as oppoed to mashing which still takes a while. What device? The game is trying to use the Android OS features to keep the button disabled while the game play thread is running. If that OS feature isn't working correctly in your device/version that the side effects would be hard to predict. Perhaps the performance issue you're perceiving has the same room cause as the button becoming re-enabled to soon. |
|
|
|
Post by starfixer on Jul 10, 2012 22:31:45 GMT -5
The thing is though,I hae a ship wih 228 hold (with upgrades). When I go to blockade, it'll take an exruciatingly long time if I blockade a few at a time, as oppoed to mashing which still takes a while. What device? The game is trying to use the Android OS features to keep the button disabled while the game play thread is running. If that OS feature isn't working correctly in your device/version that the side effects would be hard to predict. Perhaps the performance issue you're perceiving has the same room cause as the button becoming re-enabled to soon. I have the latest version. My device I the galaxy epic 4g. And I. Agree with you that disabling the reactivation of the blockade/patrl/surveilence button while the game play thread is running would fix this glitch as well as others such as multiple encounters at the same time. |
|
|
|
Post by Cory Trese on Jul 10, 2012 22:33:29 GMT -5
You'll be getting ICS in a few days anyway ... then your buttons will probably work like mine.
|
|
|
|
Post by starfixer on Jul 10, 2012 22:50:15 GMT -5
You'll be getting ICS in a few days anyway ... then your buttons will probably work like mine. What's ICS? Will everyone be getting this? |
|
|
|
Post by Cory Trese on Jul 11, 2012 0:58:01 GMT -5
ICS = Ice Cream Sandwich, the Galaxy Epic 4G device is probably receiving the ICS 4.0.x update push on July 12, just a few days from now.
It's a big change, fundamentally altering the OS environment. Might help your ST experience, might not. Very hard to predict Androids.
|
|
|
|
Post by starfixer on Jul 11, 2012 0:59:51 GMT -5
I just thought of something. It would be really cool if there was something in the options menu allowing you to choose how many times you preform an operation every time you press an operations button. For example, one person may want it so that they blockade a sector for 10 weeks after pressing blockade, while another may want it so that they surveil a area 2 times when pressing surveilence. Though there would be the problem of multiple mutinies/encounters in a row. Maybe you stop blockading when you hit an encounter/mutiny, and after the encounter/mutiny is over you have to press bockade again. Like for example, if I make it so I blockade a sector 20 times in a row when pressing blockade, and I'm suposed to get an encounter after 5, then after 5 blockades I will stop bockading, Id face the opponent and when I destroy the ship, it will be as if I blockaded the sector 5 times. Then Id have to press blockade again to countinue blockading and blockade the sector for 20 times (unless I get another encounter or mutiny before then)
|
|
|
|
Post by Cory Trese on Jul 11, 2012 1:02:52 GMT -5
Might be better to have a pop-up prompt asking for the number of weeks to blockade ... and then, as you said, reduce the remaining count to zero on encounter or mutiny. I'll look into it  |
|
|
|
Post by starfixer on Jul 11, 2012 1:08:40 GMT -5
Might be better to have a pop-up prompt asking for the number of weeks to blockade ... and then, as you said, reduce the remaining count to zero on encounter or mutiny. I'll look into it I agree it might be better as you'd want to blockade more when you have 100 water fuel than when you only have 20 water fuel. Plus it might solve the mash problem. |
|
Fenikso
Templar
[ Star Traders 2 & Elite Supporter ]
Nobody expects the Rychart Inquisition!
Posts: 753
|
Post by Fenikso on Jul 20, 2012 3:30:42 GMT -5
Hmmm. I have just noticed that the Blockade / Surveillance / Patrol feedback is much slower that in the days I was playing ST before (few months ago). In the time I played on HTC Desire, the result of the button was nearly immediate so it was very hard to mash the button so fast to actually overload the game.
Now on Galaxy Nexus it is much easier. It takes like 0.5 second to evaluate one button push. May it be caused by skinned buttons, increased complexity of the game logic, or is it (again) caused by ICS / JB?
|
|
|
|
Post by fallen on Jul 20, 2012 8:58:55 GMT -5
Most likely ICS. The Galaxy Nexus is the most troublesome device on the list right now.
|
|
|
|
Post by Cory Trese on Jul 20, 2012 14:22:58 GMT -5
I have been working on fixing the issues with the buttons to get them to slow down to the speed that the device can handle.
It is not related to any graphical changes in the buttons, no.
All of the ANR reports that have come in via Google are from the Galaxy Nexus. It is possible that in addition to the graphics performance stuff that Google is working on in ICS they also have some File I/O performance issues to address.
I have sent in a support request to inquire about that to see if they have it on the known issues list.
I will be working this week to finish the button disable / sleep-time code so that the game cannot be overloaded with a queue of tap events that cause ANR.
That may mean that some devices have faster button response and that some have slower response. However, it will mean that universally the button response will match the device's capability to calculate, store and draw the results.
|
|
