Missed the party - I'd already gone to bed when the download became accessible.
First up - Nice Job Ryan and team!
(Initial impressions after a half hour of play - more later, promised my son a trip to Southport Splash World)
Taxi now plays real nice, massive performance improvements, and camera angles are good now. (Only had a couple of quick go's - but love this table!).
Not noticed any improvement in BOP or FH but these played ok for me before (even with hud on) as long as textures were on normal, so I guess this is device specific.
CFTBL is no longer as easy to get ball trap after a fast loop, so feels more realistic.
Love the new Black Knight Magnasave button position, and that they do something now!
Only initial negatives are...
BK - after plunge, hold right upper flipper out, ball deflects off, rolls up the left upper flipper and hits some invisible stop near the upper left flipper pivot point on the upper level playfield.
BK - multiball hud display doesn't switch back to show score after multiball finish.
HD - still got a lot of lag during multiball. (get a better device I guess).
FH, BOP, Taxi - stretched HUD display.
BK - Would it be possible to have semi-translucent buttons for magnasave? (just being picky)
Taxi - Had one off instance, where on plunging the third ball, camera panned to spinout camera, then didn't pan back and ball drained unseen. I noticed the camera select button was showing locked mode though (padlock), despite not being selected, and was panning around table before the lockup. Unticked lock camera option and not had problem since. Will report if seen again.
Will try out more in depth later today hopefully.
Thanks again Ryan - made up I can play Taxi on my little old droid now!
I've noticed a trend that may be a key to performance issues. It may be total bollocks, but hey, I'm putting it out there for discussion.
==Theory==
I think the in-game performance you're seeing may have something to do with the state your device is in at the time you start the game.
==Evidence==
For example, I had a smooth game last night after the tablet was sitting idle for a while.
At lunchtime today, I powered up the tablet and shortly after seeing the homescreen, I started the game, and a game of TAXI.
Jittery-city in this instance.
So try closing all open apps and turn off GPS (like another poster confirmed).
==Theory==
I think TPA on Android bases gameplay performance and delivery at the time and circumstances it is instantiated on the device. (I am not a developer) It may be allocated threads by Android Dalvik based on device load at the time of starting.
==Evidence==
On the TF300T, you can adjust the device from "Balanced" mode to "Performance" mode from the tray menu. When you do this in-game, it has no effect on GPU performance concerning frame rate.
It's a case of "Ev-ry day I'm Stut-ter-in'" (sorry, long day for me today)
However, when you activate this mode before starting the game, you see butter-smoothness in all Alpha-numeric display games.
Ryan may be able to clarify this, as might other Android devs who are on the boards.
Just found a crazy bug. So far I have only done it on BOP.
If you play the game in portrait mode and get a high score it works as expected. If you play the game in landscape mode and get a high score, it will ask you to enter youur initials, but the high score will not take effect.
I have taken pictures and can post them if needed. So far this has happened twice. Have not had time to test this on other machines yet.
Is there a serious problem involving the four red flashers towards the top of the playfield on Medieval Madness? These four flashers have never worked on the Android and possibly iOS versions of this table.
While playing a long session on Monster Bash I've got plunger camera activ
ated during a multiball, only left flipper worked and I quickly lost all the balls. Then it returned back to normal.
I've noticed a trend that may be a key to performance issues. It may be total bollocks, but hey, I'm putting it out there for discussion.
==Theory==
I think the in-game performance you're seeing may have something to do with the state your device is in at the time you start the game.
==Evidence==
For example, I had a smooth game last night after the tablet was sitting idle for a while.
At lunchtime today, I powered up the tablet and shortly after seeing the homescreen, I started the game, and a game of TAXI.
Jittery-city in this instance.
So try closing all open apps and turn off GPS (like another poster confirmed).
==Theory==
I think TPA on Android bases gameplay performance and delivery at the time and circumstances it is instantiated on the device. (I am not a developer) It may be allocated threads by Android Dalvik based on device load at the time of starting.
==Evidence==
On the TF300T, you can adjust the device from "Balanced" mode to "Performance" mode from the tray menu. When you do this in-game, it has no effect on GPU performance concerning frame rate.
It's a case of "Ev-ry day I'm Stut-ter-in'" (sorry, long day for me today)
However, when you activate this mode before starting the game, you see butter-smoothness in all Alpha-numeric display games.
Ryan may be able to clarify this, as might other Android devs who are on the boards.
@Nik - transparency on the buttons would possible hurt performance on these fillrate bound devices so it was a design decision.
No worries, I love it as is!
Hope you're feeling better now. Thanks again!
Lower playfield bumper on BH is invisible. Collision detection works though.
First I have heard of this, and I know we didn't change the table file... is it reproducible?