Since the Christmas update, I've had a fairly consistent problem with the left side gate. When the ball gets saved there, it is supposed to get shot back into the field of play. However, a significant percentage of the time when the ball gets shot out, it immediately changes direction (underneath the treasure chest) and drains. This is pretty frustrating, and I certainly haven't been able to figure out when it's going to work and when it isn't. Has anybody else seen this?

Hey Greggerman,

I have the exact same problem. In Christmas mode, it is indeed a significant percentage of the left hand side gutter balls that bounce back immediately and drain.

The problem occurs less often in Classic mode, but does still happen. I wonder if anyone else found this problem?

Cheers,
fitpapahp

Yes, I am experiencing the same issue with the left gate. I run in classic mode and I would estimate it happens about 1 out of 10 times. And, as others have said, I started seeing this behavior after the christmas update.

By the way, I have also seen the same behavior in JSP. Same left side gate reversal kickback about 1 out of ten times.

Sounds like it's a bug, then. Is there a formal way to submit a bug to gameprom, or can I assume that someone will see it since it's on this forum?

iPhone 3G
OS 3.1.2
not jailbroken
don't know how to save video and show it to you

Cheers,
fitpapahp

also: this has only happen in TDP after the Christmas 'upgrade'.

Very simply: "all" you have to do is sink the ball into the very left hand side gutter. The one that shoots the ball back into play on it's own if the gate is not closed. The problem then is that occasionally, after this gutter shoots the ball back into play, right after it disappears under the "treasure chest", the ball re-emerges very quickly, as if it were powered downward by something under the treasure chest, into the very same gutter. By then, of course the gate is closed and the ball sewers down the middle without any input by the player.

I can't tell you exact numbers on how often it happens since I noticed it happens a lot more often with the Christmas version I stopped playing it that way. All I know is that it was significantly more often than the classic version (in which this did not happen at all until the Christmas update).

Hope this helps,
fitpapahp

It looks like fitpapahp has submitted an excellent description of the problem, and my iPhone model and OS version are the same as his. Has this been officially submitted, or do I still need to email it to info@gameprom.com?

Hey greggerman,

I have submitted the same text to the 'info@gameprom.com' address.

Thanks fitpapahp!

To DavidG from Jan 07:

I have noticed that in JSP this also happens. I believe from the speed and the way the ball sewers afterwards that it is due to the architecture under the helicopter we are not allowed to see. It seems to be an unfortunate "bounce" to me. In TDP, the phenomenon is new (since the Christmas update) and the ball is very unnaturally powered back down, faster than it got shot 'upwards'.

Cheers.

Reply to fitpapahp:

Correct. I would say the two behaviors are different, but end in the same result - ball sent back down left sewer gate immediately after being plunged upward out of the gate.

I think you characterized the differences the same way I would.

TDP acts as if there is another plunger hidden under the treasure chest, pointing downward. The ball shoots upward out of the left gutter and then rapidly reverses as if shot by another "ghost" plunger.

JSP behavior is much more subtle. After the ball is launched out of the left gutter, it sometimes (rarely) seems to tap something hidden under the airplane nose and gently rolls back into the gutter. The JSP issue seems to be related to the geometry of the table ... not necessarily a bug, but it is an unfortunate annoyance to lose a ball that way.

(There seem to be a number of similarly unfortunate "geometry" layout issues with JSP, in my experience. I will make note of them for the developer in the JSP forum. Thankfully, Gameprom has shown they are responsive to such input.)

This issue appears to have been resolved by the latest update. Thanks!

Ditto for me. I have not seen this happen since playing the 1.3 update.