Xenon pack bugs

[Baron Rubik]

Got the usual high speed ball meshing bugs, where high speed objects pass through solid items.
Here the ball went the wrong way through the tube exit gate and got jammed through the upper gate bar.

Had to abort the game as further balls jammed in behind it.

Also still has awful lag on a Samsung Note 4 SM-N910F running LP5.0.1 Xenon being particularly bad. Lag is when camera pans from table to plunger lane and sometimes during fast shots.
Works well on a 3yr old N7 though with Kitkat.
Is it Lollipop or an ART issue?

 

[strells]

Is there a bug with the xenon bonus standard goal? I've gotten my bonus way above 20000, but I have not gotten the achievement. Do I have to get it to exactly 20000 and then drain?

Steve

 

[Extork]

Ball keeps getting stuck at the upper right slope near the hole. When the ball is slowly rolling near the very top, it'll get stuck but its nothing that can't be nudged.

Live catching is awesome!

 

[Baron Rubik]

Ball keeps getting stuck at the upper right slope near the hole. When the ball is slowly rolling near the very top, it'll get stuck but its nothing that can't be nudged.

Live catching is awesome!

Yeah I'm getting the same issue. Nudging releases it though.

I can't get the Xenon 20k goal to award either. Lit all 10 lights then deliberately drained, but no goal.

 

[Extork]

Is there a bug with the xenon bonus standard goal? I've gotten my bonus way above 20000, but I have not gotten the achievement. Do I have to get it to exactly 20000 and then drain?

Steve

It worked for me, but 20,000 must be a typo. I think they meant 200,000. So during a really good first ball, it registered.

What I'm wondering though is if it's normal for the extra ball knock to be going off so much. It's kind of annoying actually

 

[Extork]

Weird... Just went to start a new game after clearing the standard goals and as soon as it loaded up it said goal 5 complete. I didn't even plunge! It was the 230,000 bonus goal, so yeah, there's something jacked up going on there. I bet they have those two goals flip flopped. Still doest explain the wizard goal registering without even doing anything.

Edit: didn't realise I was posting to the Android bugs thread. But usually android and iOS have similar issues

 

[strells]

Well even if it's supposed to be 200000, that means it has to include the 4x since the instructions say the max bonus is 58000. But even if that is the case, I'm still not getting the achievement.

 

[Extork]

Well even if it's supposed to be 200000, that means it has to include the 4x since the instructions say the max bonus is 58000. But even if that is the case, I'm still not getting the achievement.

If it helps any, it happened for me at around 2.5 mil on one ball. And multiball was going. It just popped up out of nowhere. I've been in your shoes before. Espescially when cue ball wizard came out. And no matter how many times I saw the animation for one of the goals, it still wouldn't work. But yet a lot of people were saying it worked for them

 

[Baron Rubik]

Still got some serious glitches in Landscape mode
Switching between Landscape and Portrait often results in app crashes.

Also seen ball with no texture, just black. And hud flickering, then had strange characters all over it instead of the normal display.

 

[Baron Rubik]

Menus are glitching too.
They occasionally display without their backgrounds and are non responsive, responding only to the back button. Go into same menu again and it works and displays normally.

No background

With Background

 

[Baron Rubik]

Today's play store update has broken Xenon.
Each time you exit the table, and try to go back in it tells you an improved version is available, and forces you to re download each entry.
Completely deleting the table via the table manager doesn't cure the issue either.

 

[Russell Bergman]

I'm having the same issue also. Hopefully it will be fixed soon...I'm addicted to Xenon!

 

[jaredmorgs]

Today's play store update has broken Xenon.
Each time you exit the table, and try to go back in it tells you an improved version is available, and forces you to re download each entry.
Completely deleting the table via the table manager doesn't cure the issue either.

Fixed now. Thanks for the quick fix, Scott.

 

[Reagan Dow]

It worked for me, but 20,000 must be a typo. I think they meant 200,000. So during a really good first ball, it registered.

What I'm wondering though is if it's normal for the extra ball knock to be going off so much. It's kind of annoying actually

Me too! It must be an android thing.

 

[strells]

Well, I finally got it.

I'm not usually a fan of the older tables, but Xenon is strangely compelling. Nudging to get the ball to keep landing in the upper saucer to get this goal (and the wizard goal of max bonus) was fun.

Steve

 

[Baron Rubik]

Have F2K Camera angles always been this bad, or did something change recently?

I can't remember, but was quite surprised to see how bad it was on a recent replay. Lots of top and bottom edge wasted screen real estate.

Tables should be set so at the bottom edge the centre post is just visible, with the top set so the upper playfield edge is below the HUD. And zoomed so the outlane extremities are visible bottom left and right edges.

 

[jaredmorgs]

Have F2K Camera angles always been this bad, or did something change recently?

I can't remember, but was quite surprised to see how bad it was on a recent replay. Lots of top and bottom edge wasted screen real estate.

Tables should be set so at the bottom edge the centre post is just visible, with the top set so the upper playfield edge is below the HUD. And zoomed so the outlane extremities are visible bottom left and right edges.

This is how the game was when released.

 

[Baron Rubik]

This is how the game was when released.

Thanks Jared. I couldn't remember.
Stands out having not played it for a long time.

 

[jaredmorgs]

Thanks Jared. I couldn't remember.
Stands out having not played it for a long time.

Camera angles across all tables need a baseline coordinate set, from which minor adjustments are made (depending on the features of the tables and what is obscuring critical parts of the view).

This would be a great continuous release activity to apply to each DLC in season 1 and 2. I don't think Season 3 onwards was affected like this with camera angles, but it would be worth reviewing anyway for consistency.

Thoughts on this idea [MENTION=3799]FlippyFloppy[/MENTION] and [MENTION=4573]Scumble373[/MENTION] ?

 

[FlippyFloppy]

Camera angles across all tables need a baseline coordinate set, from which minor adjustments are made (depending on the features of the tables and what is obscuring critical parts of the view).

This would be a great continuous release activity to apply to each DLC in season 1 and 2. I don't think Season 3 onwards was affected like this with camera angles, but it would be worth reviewing anyway for consistency.

Thoughts on this idea [MENTION=3799]FlippyFloppy[/MENTION] and [MENTION=4573]Scumble373[/MENTION] ?

I've been working on adjusting cameras so that they are more uniform across all tables and like you said, some tables depending on features require adjustments. Wide body tables such as Genie would not have the same angles nor would tables that have a raised playfield such as Black Knight. If there are reports of cameras being horrible broken, I'll make it a priority to fix them so feel free to let me know.

When I do adjust Flight 2000, the cameras will be a bit more pulled out for portait to fit the entire table in. Heres an example of what camera four will look like.