spoonman
New member
- Apr 20, 2012
- 1,435
- 3
"Limp Flipper" on Creature from the Black Lagoon + Translucent ball bug still present
I took an extended break from Pinball Arcade on the PS3, and there has most likely been a couple of updates since I've last played this table.
Weird flipper feel
I noticed now that when the ball gets to the very tip of the flippers it doesn't act right when hit. It almost seems like the tips of the flippers don't feel solid. So in most cases when I was trying for the outter lanes the ball just went up the opposite return lanes instead.
I played for a good hour or so and it felt like this for the entire extent if the game.
I haven't yet noticed this issue on other tables that I've tried.
Ball skin bug still here...
Also, not related to this problem, I'm seeing the "translucent ball" issue, where you use a skinned ball, then change to a table with the default ball, it ends up looking super shiny and very hard to see. The only fix for this seems to be quoting the game and restarting. This is a VERY OLD bug which I mentioned here years ago. I really thought this would have been fixed by now.
I took an extended break from Pinball Arcade on the PS3, and there has most likely been a couple of updates since I've last played this table.
Weird flipper feel
I noticed now that when the ball gets to the very tip of the flippers it doesn't act right when hit. It almost seems like the tips of the flippers don't feel solid. So in most cases when I was trying for the outter lanes the ball just went up the opposite return lanes instead.
I played for a good hour or so and it felt like this for the entire extent if the game.
I haven't yet noticed this issue on other tables that I've tried.
Ball skin bug still here...
Also, not related to this problem, I'm seeing the "translucent ball" issue, where you use a skinned ball, then change to a table with the default ball, it ends up looking super shiny and very hard to see. The only fix for this seems to be quoting the game and restarting. This is a VERY OLD bug which I mentioned here years ago. I really thought this would have been fixed by now.