Android Beta 1.31

[FlippyFloppy]

Beta 1.31

This is an old build.

http://androidfiles.pinballarcade.com/beta/AndroidPinballActivity1.31BETA.apk

----- For Testers -----
• Goals are in and ready for testing
• Coin door operations may not be working correctly
• Audio is in but their might be sound priority problems.
• Most major Tuning is in. The stir bowl is still undergoing some changes.
• Leaderboards are in.
• The pop bumpers are always lit and do not flash at the appropriate times. (Investigating whether this happens during certain events.)

----- Mobile Bug List -----
• High Scores are not in
• Slingshots are not animated
• Flashers are not lit correctly
• Plunger activates on every right flipper activation.
• Ball is not aligned in the plunger
• Initial entry starts on the 2nd character.
• Cameras need to be updated.
• The scoreboard on the backglass is not scaled properly and doesn't fit in the cutouts.
• The scoreboard on the hud at the top of the screen needs to be centered.
• The plunger faceplate on the front of the machine currently has no texture and should be chrome.
• The clock on the hud is covering the E-A-T lights on the back wall of the table. The clock may need to be re-positioned somewhere else other than below the scoreboard on the hud.
• The plunger cover graphic is also visible under the plunger box.
• The off-state of all three red flashers are a bit too dark.
• The "Dinetime" lamp on the playfield never lights up as well as Today's special.
• The orange rectangular cover caps at the top of the criss-cross ramps have sharp edges and the textures look flat. They should have more rounded edges and have a bit of shine to them.
• The screw attaching the left transparent plastic ramp to the backwards L-shaped chrome bracket is missing.
• Playfield looks flat and needs baked-in lighting like High Roller Casino currently has.
• Sound priority issue when VO is cut off by left inlane rollover.
• Several lamp textures need to be updated.
• The juke box is missing it's front texture/lamps.
• Several plastic covers lack transparency.
• Extra Ball goal is not rewarding in every scenario.


----- End Tester Notes -----
• HRC: The ball is not set properly in the plunger lane
• HRC: Plunger is clipping through the stern plunger cover
• Stern Tables: Stern logo needs to be enlarged on all three stern tables.
• CV: Judges are all the same in Cirques Voltair
• FP: Firepower sometimes does not end the game correctly after draining three balls.


----- What's New -----
• Table of the month is Fun House.


----- What's Fixed -----
• HRC: a sound file is corrupted when hitting the coin collect target.
• Placeholder needs to be updated.
• The E-A-T lights on the back wall of the table do not light up.

 

[rob3d]

Awesome! I love that these android betas are now dropping the same day as the pc beta. Thank you very much

 

[jaredmorgs]

Thanks FlippyFloppy

Before *anyone* starts to whine and moan about "quality of android betas", read the Mobile Bug List section and make a personal decision whether you want to be involved with testing on what is definitely an Alpha testing candidate.

Please and thank you.

 

[jaredmorgs]

Before I even begin testing, can I please make a request to realign the package numbering of the Android builds with the actual DLC pack release number

So this build should really be numbered 1.29.1, and when it is released to Google Play, it should be 1.29

Any post-GA patches for Diner should be 1.29.x

Not sure if the Android Development Console lets you pull version numbers down and re-upload again. But if possible, it would keep things consistent.

This is the pedant in me speaking. Please ignore if the request is considered too anal.

 

[rob3d]

1st thing I noticed was the diner clock needs to be moved. It's obstructing the EAT letters so you can't tell which letter to light for the rollover. Either the far left or the far right would be much better.

 

[jaredmorgs]

1st thing I noticed was the diner clock needs to be moved. It's obstructing the EAT letters so you can't tell which letter to light for the rollover. Either the far left or the far right would be much better.

Please read the OP for known issues.

 

[jaredmorgs]

Some transparency issues...

Plastics:

- Return Lane oval plastics transparency.
- Return Lane slingshot covers transparency.
- Left ramp plastic cover where the ramp loop is.

Basically wherever there is grey or white on the plastics.

 

[switch3flip]

Only time for a quick test, first impression is Wow, great physics, very promising. Love how ball bounces less on flippers. More realistic feel, best table physics wise so far. Great to see constant improvement.

Got all standard goals rewarded except the goal for extra ball for scoring 6mil, but got the extra ball goal when collecting extra ball for consecutive left ramp shots.

 

[Mad07]

First short test, here is what does I've seen:
# the first standard goal (Skillshoot#1) must be reached 2 times, before the goal is tagged
# after game, the function to insert the 3 char for the HC works the first time, after that it's stopped immediately, so that only 2 char can be insert
# the last standard goal was not tagged (Extraball), but I could play him (now 3 times) OK, get it, looks like, that is the extra ball in the upper area

I don't know how I should description this one:
The camera moves during play looks like have an impact of the performance/frame rate. After time the ball looks like with a jitter (or frames missing/stuttering) and/or simular the table during movement. It is much faster/stronger if the event cam is on, too. Visible every time during 4player game, if the ball doesn't drain so fast. Work around: restart TPA. seen on a brand new Samsung Note Pro LTE / rooted and disabled unneeded app in the background
Edit on
Maybe it has something to do with the EnergySaverMode. I'll observe this one with/-out this Mode
Edit off

 

[kinggo]

Beta 1.31

----- Mobile Bug List -----
• Ball is not aligned in the plunger
• Initial entry starts on the 2nd character.
• The E-A-T lights on the back wall of the table do not light up.


----- End Tester Notes -----
• HRC: The ball is not set properly in the plunger lane

-for me, initial entry stops after the 2nd character. On a very first game I was able to enter all 3 letters but later on only first two.
EDIT: nevermind, of course it ends after a 2nd one when it starts at 2nd one
-E-A-T lights works here just fine
-regarding missaligned ball...... if that is considered as a bug (and it is) and you plan to fix it on this two tables, how come that it is still present on so many older tables?

that's all for now after 3 or 4 not very good games.

 

[Baron Rubik]

-for me, initial entry stops after the 2nd character. On a very first game I was able to enter all 3 letters but later on only first two.

Same issue - confirmed (Nexus 7 2012 KK 4.4.4 stock OS rooted).

 

[kinggo]

-high score shown before 3rd ball is always #4

 

[Scumble373]

Before I even begin testing, can I please make a request to realign the package numbering of the Android builds with the actual DLC pack release number

So this build should really be numbered 1.29.1, and when it is released to Google Play, it should be 1.29

Any post-GA patches for Diner should be 1.29.x

Not sure if the Android Development Console lets you pull version numbers down and re-upload again. But if possible, it would keep things consistent.

This is the pedant in me speaking. Please ignore if the request is considered too anal.

Hey Jaredmorgs,

You are absolutely right. We may release the next two tables as 1.31.x so that we can get back on track. Sorry about that!

 

[Kratos3]

Fun table!

 

[Baron Rubik]

I know the clock is a work in progress, but the rear animated disk with white background, isn't aligned with the cyan bezel.

Nexus 7 2012 KK 4.4.4, camera view 3 Portrait orientation.
It's most obvious when the clock resets.

 

[FlippyFloppy]

-
-regarding missaligned ball...... if that is considered as a bug (and it is) and you plan to fix it on this two tables, how come that it is still present on so many older tables?

that's all for now after 3 or 4 not very good games.

Because it was either overlooked or it may not have been carried over on all platforms. Thats why im sending constant reminders to the programmers to get these fixes in and it's easier to do that by providing the Beta data.

 

[kinggo]

well, on android this is present on most tables. Not equally obvious but stil, it is there. In some plungers ball goes L/R so it's not always the same, sometimes it is in the center others isn't. I'll look better into this. Do you want me to post it here or somewhere else?

 

[Baron Rubik]

Another table I know - but as Black Knight doesn't look like it's getting rom emu'd any time soon, I figured maybe one last go at getting the one we have a little better.

The upper playfield, has an invisible object which appears after about 3mins of play, or once multiball is started.

Description -
Do a full strength plunge, and hold out the upper right flipper. As the ball rolls over the outheld upper right flipper it should roll across the upper playfield, rolling smoothly past the upper left flipper and up the lower edge of the upper playfield, roughly until it gets to the left edge of the table.

When you first start TPA, and start Black Knight, this is indeed how it works. But... After about 3mins of play (or once you have started multiball), it breaks.

In it's broken state, you plunge full strength and hold out the upper right flipper. As the ball rolls across the permanently outheld upper right flipper, when it rolls across the unenergised upper left flipper, as it gets to the upper left flipper pivot, it hits an invisible object in its path.
Once broken, it remains this way, even across new game starts until you exit the table.

Devices - happens on all device's.

Additional - this table used to always start in the broken state, up until about 6 months ago when Ryan did an update to the table.
Since then, it starts OK, but breaks after about 3mins or after multiball is started.

Here is a quick video to show you this happening.
Black knight - Invisible upper playfield object: http://youtu.be/RXlbCckSEis

Thanks guys!

 

[FlippyFloppy]

well, on android this is present on most tables. Not equally obvious but stil, it is there. In some plungers ball goes L/R so it's not always the same, sometimes it is in the center others isn't. I'll look better into this. Do you want me to post it here or somewhere else?

You can post it here or send me a message and I'll put it in our database.

 

[FlippyFloppy]

Another table I know - but as Black Knight doesn't look like it's getting rom emu'd any time soon, I figured maybe one last go at getting the one we have a little better.

The upper playfield, has an invisible object which appears after about 3mins of play, or once multiball is started.

Description -
Do a full strength plunge, and hold out the upper right flipper. As the ball rolls over the outheld upper right flipper it should roll across the upper playfield, rolling smoothly past the upper left flipper and up the lower edge of the upper playfield, roughly until it gets to the left edge of the table.

When you first start TPA, and start Black Knight, this is indeed how it works. But... After about 3mins of play (or once you have started multiball), it breaks.

In it's broken state, you plunge full strength and hold out the upper right flipper. As the ball rolls across the permanently outheld upper right flipper, when it rolls across the unenergised upper left flipper, as it gets to the upper left flipper pivot, it hits an invisible object in its path.
Once broken, it remains this way, even across new game starts until you exit the table.

Devices - happens on all device's.

Additional - this table used to always start in the broken state, up until about 6 months ago when Ryan did an update to the table.
Since then, it starts OK, but breaks after about 3mins or after multiball is started.

Thanks guys!

This occurs because the wall collision sticks out into the left upper flipper. Normaly the ball bounces off of it and rolls back to the left upper flipper. However something is causing the trajectory to or the ball speed to slow down enough so that it hits the wall collision that makes it appear to hit a flat wall. I'll put it in our database.