- Mar 17, 2012
- 4,293
- 0
This is the master issues list for Ripley's Believe It or Not! This thread is maintained to aid FarSight in exterminating gameplay bugs, art issues, and sound problems from RBION.
This thread is locked to keep it clean and focused on actual issues, as opposed to opinions about such issues. Report art issues in the Art forum, and all other issues in a new thread in this table's forum. I will add newly-reported issues to this thread at regular intervals. In addition, each bug has a link to the thread it was reported in; discussion of bugs should take place there.
Latest Updates:
29 Nov 2013
Status key:
GAMEPLAY ISSUES:
02-001: Ball floats above hole at end of left habitrail
First reported: 15 Mar 2012
Description: The ball levitates above the hole at the end of the left wireform, above the left inlane.
Devices: Android
Status: Acknowledged
02-002: Second locked ball may become stuck in or near lock
First reported: 01 Mar 2012
Description: The second locked ball may become stuck at various points in or near the lock. A continuous clicking noise may be heard if the two balls are in a position to knock against each other repeatedly.
Devices: All
Status: Fixed
Notes: See also thread RBION right ramp trouble.
02-003: "Bonus" appears on DMD, but bonus is not actually tallied
First reported: 28 Mar 2012
Description: After draining, the end-of-ball bonus starts and displays "Bonus" on the DMD, then proceeds straight to the next ball without actually counting the bonus.
Devices: iOS, 360
Status: Acknowledged
02-004: After entering initials, the UI does not advance
First reported: 11 Apr 2012
Description: After entering initials, the UI used for entering initials does not go away and the game does not advance.
Devices: PS3
Status: Acknowledged
02-005: Making a skill shot does not fulfill related goal
First reported: 04 Apr 2012
Description: Making a skill shot does not mark off the associated goal. Some players report needing hundreds of skill shots before the goal registers.
Devices: All
Status: Acknowledged
02-006: Multiball launches two balls simultaneously
First reported: 22 Apr 2012
Description: The table launches the second and third balls for multiball simultaneously instead of sequentially.
Devices: All
Status: Acknowledged
02-007: Table awards "Perfect Tour" bonus when letters were collected over multiple balls
First reported: 05 May 2012
Description: The "Perfect Tour" bonus is awarded even though a player needed multiple balls to collect the Ripley's letters, when it should only awarded if all 7 letters are collected on one ball.
Devices: All
Status: Acknowledged
02-008: Older devices experience framerate degradation
First reported: 01 Mar 2012
Description: Older devices have difficulty playing RBION at its full framerate.
Devices: Android, iOS
Status: Design constraint. The Whitestar engine used in the real RBION requires more processing power to emulate than other ROMs.
02-009: Starting a new game immediately after finishing previous game may cause camera to remain in attract mode
First reported: 22 Apr 2012
Description: Quickly starting a new game after finishing one may leave the camera in attract mode, panning across the table, instead of on the plunger.
Devices: PS3, Vita, 360
Status: Acknowledged
02-010: Ball phases through right outlane wall
First reported: 15 May 2012
Description: The ball phases through the right outlane wall. Depending on where it ends up, this may lead to secondary odd behavior later.
Devices: Vita, 360
Status: Acknowledged
02-011: Landscape camera 2 view with unlocked camera sometimes does not keep up with ball
First reported: 24 Jun 2012
Description: The camera in landscape view 2 sometimes does not follow a fast-moving ball down the table fast enough before the ball reaches the flippers.
Devices: Android
Status: Acknowledged
02-012: Ripley's letter erroneously awarded after Antarctic Multiball
First reported: 28 Jun 2012
Description: A Ripley's letter is awarded after the Antarctica mode even though the requirements were not met.
Devices: 360
Status: Could not reproduce
02-013: Super Jackpot fails to light for remainder of game if Atlantis and Continent Super Jackpot are stacked on vari-target
First reported: 01 Aug 2012
Description: If both Atlantis and the Continent Super Jackpot are stacked on the vari-target and collected, the regular Super Jackpot becomes unavailable for the remainder of that game.
Devices: PS3, 360
Status: Acknowledged (There is a possibility this is a bug in the real table. The situation does not come up very often.)
02-014: Ball becomes stuck on habitrail from "B" temple lane
First reported: 19 Jul 2012
Description: The ball can become stuck in the depression on the habitrail leading from the "B" temple ramp. Call Attendant feature can retrieve the ball.
Devices: All
Status: Acknowledged
02-015: Table loses track of a ball and becomes unable to continue
First reported: 13 Mar 2012
Description: Under various circumstances, the table can "lose" one of the balls and become unable to continue play. See linked thread for all the different variations of this bug.
Devices: All
Status: Acknowledged as of 06 Sep 2012
Notes: This issue, along with related issues in FunHouse, have been indicated by FarSight to be a very difficult fix.
02-016: Frog Frenzy starts with only one ball
First reported: 05 Aug 2012
Description: Frog Frenzy begins, but only one ball is on the playfield; the others do not launch.
Devices: All
Status: Not a bug. Frog Frenzy is a 4-ball mode if and only if another multiball is running when Frog Frenzy starts.
02-017: Ball becomes stuck behind vari-target
First reported: 07 Sep 2012
Description: The ball can become stuck behind the vari-target. Call Attendant can retrieve the ball if it is the only ball remaining in play. On the 360, the controller vibrates continually for as long as the ball is behind the vari-target.
Devices: iOS, 360
Status: Acknowledged
Notes: See also post at Missing ball, unable to continue - Post # 44.
02-018: Ball becomes stuck on post below upper right flipper
First reported: 04 Apr 2013
Description: The ball can become stuck on a post below the upper right flipper. Player was able to free ball by knocking another ball into it. Suspect minor problem with table geometry rather than clipping issue.
Devices: Android (Nexus 7)
TPA Version: Android 1.12.0
Status: Acknowledged
This thread is locked to keep it clean and focused on actual issues, as opposed to opinions about such issues. Report art issues in the Art forum, and all other issues in a new thread in this table's forum. I will add newly-reported issues to this thread at regular intervals. In addition, each bug has a link to the thread it was reported in; discussion of bugs should take place there.
Latest Updates:
29 Nov 2013
- Updated status of issues # 02-001, 02-003, 02-004, 02-005, 02-006, 02-007, 02-009, 02-010, 02-011, 02-013, 02-014, 02-017, 02-018, 02-502, 02-504, 02-506, 02-507 and 02-601.
- Added insert lighting issue # 02-507.
- Added geometry issue # 02-018.
Status key:
- New - Issues that are newly reported.
- Unknown - Issues from a long time ago that have not been followed up in a while so that no one really knows what happened to them.
- Confirmed / Open - Issues that either I've personally reproduced, that so many people have reported that the existence of the issue is not in doubt, and/or that members have posted a demonstration (like a YouTube clip) of the issue.
- Acknowledged - Issues that have been acknowledged by FarSight, but for which no fix exists yet.
- Fix Pending - Issues that have fixed by FarSight, but the fix is in testing or submission process and is not yet available to players.
- Fixed - Issues that have been resolved by FarSight. Note that not all platforms receive bug fixes at the same time, so an issue that is "Fixed" may still be unresolved on some platforms.
- Could Not Reproduce - Issues that were reported, but the issue has not been successfully reproduced.
- Working as Designed - Issues that are bugs or quirks in the actual table, as well as other issues that result from design or licensing constraints.
GAMEPLAY ISSUES:
02-001: Ball floats above hole at end of left habitrail
First reported: 15 Mar 2012
Description: The ball levitates above the hole at the end of the left wireform, above the left inlane.
Devices: Android
Status: Acknowledged
02-002: Second locked ball may become stuck in or near lock
First reported: 01 Mar 2012
Description: The second locked ball may become stuck at various points in or near the lock. A continuous clicking noise may be heard if the two balls are in a position to knock against each other repeatedly.
Devices: All
Status: Fixed
Notes: See also thread RBION right ramp trouble.
02-003: "Bonus" appears on DMD, but bonus is not actually tallied
First reported: 28 Mar 2012
Description: After draining, the end-of-ball bonus starts and displays "Bonus" on the DMD, then proceeds straight to the next ball without actually counting the bonus.
Devices: iOS, 360
Status: Acknowledged
02-004: After entering initials, the UI does not advance
First reported: 11 Apr 2012
Description: After entering initials, the UI used for entering initials does not go away and the game does not advance.
Devices: PS3
Status: Acknowledged
02-005: Making a skill shot does not fulfill related goal
First reported: 04 Apr 2012
Description: Making a skill shot does not mark off the associated goal. Some players report needing hundreds of skill shots before the goal registers.
Devices: All
Status: Acknowledged
02-006: Multiball launches two balls simultaneously
First reported: 22 Apr 2012
Description: The table launches the second and third balls for multiball simultaneously instead of sequentially.
Devices: All
Status: Acknowledged
02-007: Table awards "Perfect Tour" bonus when letters were collected over multiple balls
First reported: 05 May 2012
Description: The "Perfect Tour" bonus is awarded even though a player needed multiple balls to collect the Ripley's letters, when it should only awarded if all 7 letters are collected on one ball.
Devices: All
Status: Acknowledged
02-008: Older devices experience framerate degradation
First reported: 01 Mar 2012
Description: Older devices have difficulty playing RBION at its full framerate.
Devices: Android, iOS
Status: Design constraint. The Whitestar engine used in the real RBION requires more processing power to emulate than other ROMs.
02-009: Starting a new game immediately after finishing previous game may cause camera to remain in attract mode
First reported: 22 Apr 2012
Description: Quickly starting a new game after finishing one may leave the camera in attract mode, panning across the table, instead of on the plunger.
Devices: PS3, Vita, 360
Status: Acknowledged
02-010: Ball phases through right outlane wall
First reported: 15 May 2012
Description: The ball phases through the right outlane wall. Depending on where it ends up, this may lead to secondary odd behavior later.
Devices: Vita, 360
Status: Acknowledged
02-011: Landscape camera 2 view with unlocked camera sometimes does not keep up with ball
First reported: 24 Jun 2012
Description: The camera in landscape view 2 sometimes does not follow a fast-moving ball down the table fast enough before the ball reaches the flippers.
Devices: Android
Status: Acknowledged
02-012: Ripley's letter erroneously awarded after Antarctic Multiball
First reported: 28 Jun 2012
Description: A Ripley's letter is awarded after the Antarctica mode even though the requirements were not met.
Devices: 360
Status: Could not reproduce
02-013: Super Jackpot fails to light for remainder of game if Atlantis and Continent Super Jackpot are stacked on vari-target
First reported: 01 Aug 2012
Description: If both Atlantis and the Continent Super Jackpot are stacked on the vari-target and collected, the regular Super Jackpot becomes unavailable for the remainder of that game.
Devices: PS3, 360
Status: Acknowledged (There is a possibility this is a bug in the real table. The situation does not come up very often.)
02-014: Ball becomes stuck on habitrail from "B" temple lane
First reported: 19 Jul 2012
Description: The ball can become stuck in the depression on the habitrail leading from the "B" temple ramp. Call Attendant feature can retrieve the ball.
Devices: All
Status: Acknowledged
02-015: Table loses track of a ball and becomes unable to continue
First reported: 13 Mar 2012
Description: Under various circumstances, the table can "lose" one of the balls and become unable to continue play. See linked thread for all the different variations of this bug.
Devices: All
Status: Acknowledged as of 06 Sep 2012
Notes: This issue, along with related issues in FunHouse, have been indicated by FarSight to be a very difficult fix.
02-016: Frog Frenzy starts with only one ball
First reported: 05 Aug 2012
Description: Frog Frenzy begins, but only one ball is on the playfield; the others do not launch.
Devices: All
Status: Not a bug. Frog Frenzy is a 4-ball mode if and only if another multiball is running when Frog Frenzy starts.
02-017: Ball becomes stuck behind vari-target
First reported: 07 Sep 2012
Description: The ball can become stuck behind the vari-target. Call Attendant can retrieve the ball if it is the only ball remaining in play. On the 360, the controller vibrates continually for as long as the ball is behind the vari-target.
Devices: iOS, 360
Status: Acknowledged
Notes: See also post at Missing ball, unable to continue - Post # 44.
02-018: Ball becomes stuck on post below upper right flipper
First reported: 04 Apr 2013
Description: The ball can become stuck on a post below the upper right flipper. Player was able to free ball by knocking another ball into it. Suspect minor problem with table geometry rather than clipping issue.
Devices: Android (Nexus 7)
TPA Version: Android 1.12.0
Status: Acknowledged
Last edited: