|
|
Post by khearn on Mar 28, 2014 13:55:11 GMT -5
I just started playing TA Elite on my Nexus 10, and the menu button on the map screen isn't working. It works fine on my Moto X. When I press it, the button turns from orange to blue, so I know the touch is being detected, but no menu choices show up along the bottom of the screen.
This is a Nexus 10, running Android 4.4.2.
|
|
|
|
Post by fallen on Mar 28, 2014 15:14:01 GMT -5
khearn - have you turned on any game options that are different between the two games?
|
|
|
|
Post by khearn on Mar 28, 2014 16:20:43 GMT -5
No, all option boxes are unchecked on both devices.
This might be related to the Nexus 10 having a bar at the bottom in landscape mode, with the back, home, and recent apps buttons. Those buttons are on the side when in landscape mode on my phone. Maybe the menu bars are interfering with each other?
|
|
|
|
Post by fallen on Mar 28, 2014 16:38:20 GMT -5
khearn - which menu button are you referring to? The orange one with three dots that we put in the game, or the software buttons provided by the OS?
|
|
|
|
Post by khearn on Mar 28, 2014 17:28:41 GMT -5
The orange button with 3 dots is what isn't working on the nexus 10. The software buttons provided by the OS is what I meant is at the bottom of the screen on the Nexus 10, and on the right side on the Moto X. Sorry if I wasn't clear.
|
|
|
|
Post by fallen on Mar 28, 2014 17:42:46 GMT -5
khearn - I appreciate the extra clarification. Before we go hunting, we want to make sure we are hunting the right tiger 
|
|
|
|
Post by fallen on Mar 28, 2014 17:44:25 GMT -5
I have taken #TA-2388 to look into this one. Sounds like a 4.4 bug.
|
|
|
|
Post by khearn on Mar 28, 2014 17:50:57 GMT -5
I understand. I'm a software engineer, too. I'm really impressed with you guys' responsiveness. I started out playing Age of Pirates a few weeks back, and have already seen several updates with bugfixes for problems that were just reported a few days earlier. I'm just starting on TA, and already like it enough to have bought Elite. I'll probably just start out by buying Elite for the rest of your games when I get to them. |
|
|
|
Post by fallen on Mar 28, 2014 17:56:36 GMT -5
khearn - thanks for the encouragement! We focus a lot on working -with- our community and listening and responding. I am glad that it pays off in happy customers willing to try all of our games. My favorite Google Play comment recently matches your sentiment. From Cyber Knights: "The Trese Brothers put in tons of work adding features and fixing bugs. Several new elements have shown up since I bought this and it makes me wish I could buy it again. They listen to the community so well I usually don't experience the bugs before they're fixed! Well done." Warms the heart and keeps us going 
|
|
|
|
Post by khearn on Apr 4, 2014 17:19:37 GMT -5
I just noticed a similar problem in Star Traders. When I'm on the map screen, if I press the menu button in the lower left (orange button with 3 black dots in a vertical line), on my Moto X I get a black menu with white text that slides up from the bottom. On the Nexus 10, I get nothing. Pretty much the same problem as on the map in TA. In ST, it works in both landscape and portrait mode on the phone, but in neither on the table. I suspect it's the same problem on both apps. Should I put a separate posting on the ST bugs forum, or is reporting it here sufficient? Given that it's probably the same issue on both games, I'm guessing that fixing it on one will fix it on the other.
If you think you have a fix but have no way to test it (what, you don't have one of every phone and tablet on the market?), I'd be willing to install a test build to give it a try.
[edit: This is a Nexus 10 running android 4.4.2, and Star Traders Elite v5.5.1, and a Moto X running android 4.4.2, and Star Traders Elite v5.5.1 ]
|
|
|
|
Post by Cory Trese on Apr 4, 2014 17:25:02 GMT -5
Thanks for the feedback. I have all of those devices on bone stock, and do test with them.
If I can figure out a solution for your configuration, I'll post a note in an upcoming update.
Thanks!
|
|
|
|
Post by khearn on Apr 10, 2014 20:58:48 GMT -5
I wasn't sure if this was one of the "Reported Map Bugs" that was fixed in 2.0.1, so I checked. i can confirm that this is still broken in 2.0.1. I'm now on android 4.4.3, but that doesn't seem to make any difference.
|
|
|
|
Post by fallen on Apr 10, 2014 21:08:27 GMT -5
khearn - we always list items like that in the release notes! Thanks!
|
|
|
|
Post by Cory Trese on Apr 10, 2014 22:29:26 GMT -5
I wasn't sure if this was one of the "Reported Map Bugs" that was fixed in 2.0.1, so I checked. i can confirm that this is still broken in 2.0.1. I'm now on android 4.4.3, but that doesn't seem to make any difference. Yeah we are really hoping that they patch it and looking for a work around for the impacted devices. Good to know it's so few but still bad news for the victims of this Google bug. |
|
|
|
Post by khearn on Apr 11, 2014 12:18:24 GMT -5
Well, it's not fixed in 4.4.3, so it will be a little while before it does get fixed in android. Is this something you're sure that they know about? If not, if you'll give me a good description of what is going wrong, I can file a bug report. I work at Google, not on anything related to android, but I can still file bugs. |
|
